Then you have been lying to us when you said that provider A cannot be changed; you have the source code. ;-)
Trying to make a delegating proxy like this is really quite hard, believe me (and others in this thread). Are you saying that B should use a persistent and distributed event handling system if one is available, otherwise it just delegates to A? And that the consumers couldn't care less which happens? I have my doubts about that last bit, and if they *do* care then they should be able to express this in a filter. > 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]> > Date: Wednesday, April 15, 2015 at 12:59 PM > To: Frank Langel <[email protected]>, OSGi Developer Mail List > <[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
