I've done this with JBossMQ as proof of concept for a project we are working. I was not able to use the wsdl2Java tools to generate the stubs. Instead I wrote my own - actually is was fairly easy. My JMS listener is a standalone program as well.
There is a book by Wrox - Axis Next Generation in Java SOAP - (ISBN 1-861007-15-9) which has an example of a JMSTransport implementation. Watch out because the example has one huge bug, the reply queue is not a temporary queue. Because of this RPC replies can be returned to the wrong client if one of the clients waiting for a reply dies before he gets his response. Simply set up temporary queues for all replies and this problem will be solved. -----Original Message----- From: Brain, Jim [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 11, 2003 11:31 AM To: AXIS Mailing List (E-mail) Subject: Questions about Axis over JMS Details are a bit light on this, from what I can google. For anyone who has does AXIS/JMS, a few questions: * Some of the examples I see on IBM's web site assume you are using the low level JAX-RPC API and can code the changes to switch from HTTP to JMS in the client code. I have generated my client stubs from WSDL with wsdl2java, so I want to be able to use those same stubs (with some config parm to switch from HTTP to JMS), or worst case, regen the stubs for JMS, but no transport specific coding done by me. Is this possible? * On the server side, I get the impression the JMS listener is a standalone program. Has anyone managed to get the listener to work as a Message Driven Bean in J2EE 1.3 or whatever? * Anyone doing similar stuff with Websphere and MQSeries (which is what we are using?) Jim Jim Brain, [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> "Researching tomorrow's decisions today." (319) 369-2070 (work) Systems Architect, ITS, AEGON Financial Partners
