Hi Arun,
If you're using JBI packaging (SU and SA) as you are doing, you don't need that bean. The JBI deployer will take care of correctly setting up and registering your endpoints for you. It's only needed when you use plain Spring files or bundles containing Spring files to deploy your JBI endpoints. The Spring file will only create the endpoint instances and this bean will make sure that they get registered with the JBI runtime. Regards, Gert Vanthienen On Fri, Apr 4, 2014 at 5:34 PM, arun kumar <[email protected]> wrote: > Hello Gert, > > Thanks, I will try with the second option. > > Just one question though: > > <bean class="org.apache.servicemix.common.osgi.EndpointExporter" /> > > I am using JBI packaged service assembly, Is EndpointExporter the right > class to register the JBI endpoints ?. > I get a null pointer exception in this class when deploying the service ie > on this line inside deploy() api. > "this.assemblyName = bundleContext.getBundle().getSymbolicName();". > Basically the bundleContext is null, I will put an Activator class to set > the bundleContext and test this perhaps. > > Thanks, > Arun > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/JBI-cluster-not-working-with-ActiveMQPool-tp5719698p5719885.html > Sent from the ServiceMix - User mailing list archive at Nabble.com.
