Per Daniel:

I've been thinking about this too because we could run into issues if there are static objects that all come from the main class loader that each controller is manipulating. The issue is, each use case will configure the actors differently. There is a static reference to the actor service in the event manager code. I think this may be problematic? Do you think so?

And also:

The LazyInitData inner class for the ControlLoopEventManager has a hard coded config name “event-manager” that can’t be overwritten by a subclass of the ControlLoopEventManager. For us, each use case has its own event manager and those event managers are configured differently per use case (i.e. configuring the SDN-R actor request/response topic). It would be nice if the subclass could determine what the event-manager config file name should be for the super class LazyInitData instance. Currently my work around for this is for our use case event managers to have their own LazyInitData class that define the config file name that initializes its own EventManagerServices.

Solution:

The ControlLoopEventManager should allow the rules/controller to specify the EventManagerServices object to use.