Event Model

At the code level, different systems often still call each other directly or indirectly. To reduce code coupling, you can use Hasor's event mechanism for deeper decoupling.

Hasor events have three execution models:

• Synchronous with a dedicated thread.
• Synchronous with a shared thread.
• Asynchronous.

Model	Main flow	Listener execution
Synchronous, dedicated thread	Fire event → wait → continue after listeners finish	Runs on an event thread; completion releases the waiting caller
Synchronous, shared thread	Fire event → run listeners → continue	Runs on the calling thread
Asynchronous	Fire event → continue immediately	Runs independently on an event thread

Whether the event model is synchronous or asynchronous, events in Hasor share the following characteristics:

• Event listeners execute in registration order.
• Event listeners use the same interface.
• Event registration uses the same approach.

Registering Event Listeners

Implement a listener

import net.hasor.core.EventListener;
public class MyListener implements EventListener<Object> {
    public void onEvent(String event, Object eventData) throws InterruptedException {
        Thread.sleep(500);
        System.out.println("Receive Message:" + JSON.toJSONString(eventData));
    }
}

Obtain the EventContext interface

ApiBinder apiBinder = ... 
EventContext ec = apiBinder.getEventContext();

or

AppContext appContext = ...;
EventContext eventContext = appContext.getInstance(EventContext.class);

or

EventContext eventContext = appContext.getEventContext();

or

public class MyBean {
    @Inject
    private EventContext eventContext;
}

Then register the event in the container through EventContext.

Register an event listener

EventContext eventContext = ...
eventContext.addListener("EventName",new MyListener());

Firing Events

Example

eventContext.fireSyncEvent("EventName",...);