What is the recommended approach for an application deployed as an EAR in JBoss 5.1 to access JMS destinations on WebLogic 9.2?
The current implementation, which worked just fine on 4.2.3, does not even start without errors on JBoss 5.1. The application deployed to 4.2.3 used a Spring JmsTemplate to connect to WebLogic. WebLogic's client libraries were put into $jboss_home/server/$name/lib. This worked just fine.
With JBoss 5.1 I have tried the method that had worked on 4.2.3 but I could not even start the server (even before deploying my EAR). I have also tried to bundle the libraries in the EAR's lib directory (weblogic.jar, wlclient.jar, wljmsclient.jar together and separately), but I seem to be getting other seemingly unrelated errors
- class loader errors that result in ClassNotFoundExceptions for JBoss AS classes ( org.jboss.web.deployers.WARStructure, org.jboss.resource.metadata.mcf.ManagedConnectionFactoryDeploymentGroup, org.jboss.resource.metadata.mcf.NoTxConnectionFactoryDeploymentMetaData)
- a data source not being loadable with a javax.management.InstanceNotFoundException
- security-related warnings on missing signer certificates for JBoss AS jars (jboss-classloader.jar, jboss-deployers-vfs.jar) - client libraries seem to be loading different security policies
As I don't seem to have a solution that can bundle the WebLogic client jars (neither in the application server's lib directory, nor in the EAR), I assumed there should be a better way. I have considered some options and found some pointers, but could not figure out the way to proceed for my current setup (WebLogic 9.2 and JBoss 5.1):
- remove some classes from the WebLogic client libraries that exhibit 'bad behavior' (some pointers, but no solution)
- load client libraries differently by adapting JBoss class loading or deployers
- JCA (WL 8.1 with JBoss 5.1)
- messaging bridge (Configure WebLogic 9.2 Messaging Bridge)
I cannot change the WebLogic Version, but if someone has a positive experience with JBoss 6, I will try that (current version M4 - so I am a bit reluctant). Alternatively, I could also imagine adaptations to JBoss Messaging or deploying HornetQ.
Thank you,
Kariem