-
1. Re: How to use external or third party jar in the classpath of a bundle.
ffang Aug 14, 2010 2:45 PM (in response to divakar)Hi,
You need install third party jar containing weblogic.jndi.WLInitialContextFactory as a bundle, and then in your JMS consumer bundle you should import weblogic.jndi package.
Btw, you should put this question on FUSE ESB forum.
Freeman
-
2. Re: How to use external or third party jar in the classpath of a bundle.
divakar Aug 16, 2010 8:31 AM (in response to ffang)Thanks, Yes I should have dropped this in the ESB forum, I did it accidentally,
You answer helped me,
I installed the jar file as bundle using the following command,
osgi:install -s wrap:file:///C:/xxx/xxx.jar
-
I am facing another issue now weblogic jms consumer,
karaf@root> Exception in thread "SpringOsgiExtenderThread-66" org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.apache.servicemix.jms.endpoints.JmsConsumerEnd
point#0' defined in URL bundleentry://212.fwk27263487/META-INF/spring/xbean.xml: Cannot resolve reference to bean 'connectionFactory' while setting bean property 'connectionFactory'; nested exceptio
n is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'connectionFactory' defined in URL bundleentry://212.fwk27263487/META-INF/spring/xbean.xml: Invocation of
init method failed; nested exception is javax.naming.CommunicationException [Root exception is java.net.ConnectException: xxx.xxx.com/xx.xx.xx
xx:xxxx Bootstrap to xxx.xxx.com/xx.xx.xx
xx:xxxx failed. It is likely that the remote side declared peer gone on this JVM