Its a great question. In essence they are initialized in the order they are defined within muse.xml. As such make sure your producer is higher up. No threads are used (that could introduce some very strange behaviour) just a single startup thread. (NOTE that isn't strictly speaking gauranteed under osgi as there are about 4-5 threads that may start a bundle depending on the container, so if you're bundling other code it may have its activator started sooner than predicted)
-----Original Message----- From: Jan Torben Heuer [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 09, 2008 12:21 PM To: [email protected] Subject: Re: Lookup other capabilites On Tuesday 08 July 2008 14:23:04 [EMAIL PROTECTED] wrote: Hallo, > Hi Jan, > The initializeCompleted always only works on a singel resource. I > assume as you couldn't get the reference from the external soap > request that the producer is in a different resource. To lookup other > resources use Yes, it is (it is a different ContextPath, though I assume it is a different resource). > > getResource().getResourceManager().getResource(new EndpointReference( > new > >URI(museIsoLayer.getRouter().getEnvironment().getDefaultURI()+resourceN >ame) >)); > > where resourceName is the <context-path>adapter</context-path>. What if the resource hasn't been initialized, yet? Should I simply block until then? Do the axis or mini-servlet engines start resources simultanously or will it result in a deadlock? (Hope I didn't mix something up) Jan -- Jan Torben Heuer Institute for Geoinformatics [EMAIL PROTECTED] Robert-Koch-Strasse 26-28 +49 251 83-31960 48151 Münster, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
