Hello, I have developed a little example for using JMS with Axis2. My environment is Tomcat 5.5 with Axis 1.3, ActiveMQ 5 and Eclipse 3.3. By using the contract-first-approach I have created service and client code from the wsdl and get it working after some problems with configuration :-)
But I still have some questions according message delivery... Image following scenario: 1. Client makes a request while the server is down. The message is pending on an activemq destination. 2. The client receives a timeout because the server is still down and gets online later. The client is terminated. I know, there is a callback mechanism, but there are many other reasons that the client can terminate... 3. The server will be started and listens to the queue of activemq, gets the request message and returns a response to another queue. That´s what works very well. I have now the problem that the client and the callbackhandler are down. How can I achive that I get the message back to the client? Can I start the callbackhandler again independly from the service client? I hope, there is another solution than writing an jmsConsumer which receives the message and I have to parse it on my own... By using http and Axis2 this part must be done by Sandesha2 (ws-rm), right? The client gets online, has stored the sequence id and can ask the server for all messages!? Or I am completly wrong? It´s my first post at Axis user forum. I hope, my question and my writing is clear enough. More information to this topic are available at http://wso2.org/forum/thread/3111 Thanks for your help, Jens -- View this message in context: http://www.nabble.com/further-questions-to-Axis2-and-JMS-tp15241641p15241641.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
