To be notified of endpoints, a better way might be to register a
service in OSGi implementing:
org.apache.servicemix.nmr.api.event.EndpointListener
Or track all services in the registry implementing:
org.apache.servicemix.nmr.api.Endpoint
And the answer to your second question is no. In both case, you'll
have at the end an service register which implements
org.apache.servicemix.jbi.deployer.ServiceAssembly
But the best way is the one I indicated above, tracking endpoints at
the NMR level is easier. Because it's the lower level, you're sure
that you won't miss anything.
On Fri, Jul 3, 2009 at 14:57,
TheWinch<[email protected]> wrote:
>
> Thank you! These explanations + a bit of source browsing make the picture
> very clear. From what I understand, if I register an OSGi listener to track
> down EndpointWrapper registrations, then I will be able to get an idea of
> every service that has been deployed. I have 2 more questions:
>
> 1. In which jar is EndpointExporter provided ?
> 2. What of "regular" 3.2.3 SUs ? I mean, if I deploy a SMX3.2.3 installer,
> will an EndpointWrapper and a DeployedAssembly be registered in OSGi as well
> ?
>
> From my experiments with the OBR and the console, I would rather answer
> "yes" to my second question, but asking directly to the source does not hurt
> :-).
> --
> View this message in context:
> http://www.nabble.com/-SMX4--Registry-%2B-Dynamic-endpoint-activation-by-OSGi---tp24320145p24322751.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
