Marcel Offermans wrote: > > Are you aware of the enterprise expert group within OSGi that is > currently looking at issues like this (I'm not sure if this exact > scenario is being discussed but distributed/clustered solutions in > general are)? > Ah, no didn't know that - thanks for the info!
>> Ok, looking at the code again, I think we could change the Activator >> code a little bit and factor out the object creation in the start() >> method to separate >> method (like createEventAdminImpl(...)) - so I could easily provide my >> own activator which extends the existing one. > > Still, in that case you're basically creating your own event admin > implementation bundle. You can reuse some of the code, but have to > repackage that outside of Felix (or add a second event admin > implementation to Felix, but then it would have to be useful outside > your own use case). > > Another idea might be to just have an event listener that listens to > events that need to be sent to other nodes in the cluster. That can be > done without changing the event admin itself. I doubt that you will want > to send *all* events to all nodes, because a lot of events are framework > related and simply having them sent to other nodes in a cluster would > not make sense (for example, sending a "framework started" or > "startlevel changed" event to another node would only confuse it). Yes, true - sending events to other nodes could be done by a general event listener. Unfortunately we have some extra requirements which require us to add additional information to the event on the receiving side before the event is distributed on that node. I'm not sure what the reason was that I have to do this inside the event admin anymore - I'm now thinking about the whole stuff for some days and lost track a little bit :) But I'll rethink the whole stuff once more :) Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
