Pulse 3.x Event Manager

I’ve started the migration of a Java application using Pulse 2.x to Pulse 3.x and I found the following breaking change:

In 2.x, there used to be a way to tell the engine to forward its events to a SEEventHandler. The way to do that was: pulseEngine.getEventManager().forwardEvents(myHandler);.
In 3.x, there is a PulseEngine.getActiveEvents() method that appears to do the same but in an “on-demand” way. Is there the only way we have in 3.x to receive the events from the engine? Is still a way to receive them in an asynchronous way?


Privacy Notice