Which is really just a set of MBeans to create JMS client objects in JBoss jndi.
Although it should really just be a case of configuring the JMSProvider
to point at Oracle's jndi.
Looking at attempting to do the same thing described above, that is use Oracle AQ as a JMS Provider for MDBs using JBoss 4.2 and Oracle 10.2.0.1.0. Started implementing the "Oracle AQ Patch". Treaded thru various configuration issues which I believe are resolved, but I am now receiving a JMSException("JMS Session is null.") from the AQjmsConnectionConsumer run() method upon startup. Before continuing down this path; I figure I would throw out a couple of questions:
- Is the "Oracle AQ Patch" compatible with Jboss 4.2 and Oracle 10.2.0.1.0?
- A previous reply mentions "configuring the JMSProvider", has anybody gotten this to work? If so, you wouldn't happen to have a cheat sheet or a bit more direction.
- Also, the "Oracle AQ Patch" doesn't support XA, found an oracle aq resource adapater implementation (e.g. https://oracleaq.dev.java.net/), has anybody used this resource adapater with JBoss?
Guess what I'm looking for is a nudge in the right direction!!! More than willing to put in the effort, just would like to start out knowing I'm not going down a dead-end plus that it is the best solution.