# Pulse 3.x Event Manager

**URL:** https://discourse.kitware.com/t/pulse-3-x-event-manager/533
**Category:** Pulse Physiology Engine
**Created:** [September 10, 2020, 1:38pm UTC](https://discourse.kitware.com/t/pulse-3-x-event-manager/533 "2020-09-10T13:38:43Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![esteban.aliverti](https://discourse.kitware.com/user_avatar/discourse.kitware.com/esteban.aliverti/32/165_2.png) [@esteban.aliverti](https://discourse.kitware.com/u/esteban.aliverti)
#### Post date: [September 10, 2020, 1:38pm UTC](https://discourse.kitware.com/t/pulse-3-x-event-manager/533/1 "2020-09-10T13:38:43Z")

</div>

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?

Regards,