I think you do not need to replace EventAdmin to implement distribution
and persistence.
You could simply create a listener that receives all events and does the
dsitribution / persistence. Jus make sure you mark events created by
your own impl to avoid recursion.
Christian
Am 15.04.2015 um 13:05 schrieb Frank Langel:
Yep, thought so. Idea was to have two EventAdmin implementations
* Provider A is the fellix event admin impl
* Provider B is a custom implementation providing additional
functionality/capabilities
Provider B is registering a service of type EventHandler if that event
handler service has some specific properties, else A is used. In my
case, B provides persistent and distributed messaging implementation.
Does that make sense?
Thanks
Frank
From: Marcel Offermans <[email protected]
<mailto:[email protected]>>
Date: Wednesday, April 15, 2015 at 12:59 PM
To: Frank Langel <[email protected]
<mailto:[email protected]>>, OSGi Developer Mail List
<[email protected] <mailto:[email protected]>>
Subject: Re: [osgi-dev] service tracker precedence
Greetings, Marcel
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
