You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Asbell, Jonathan" <Jo...@McGraw-Hill.com> on 2002/11/21 22:16:34 UTC

RE: JMS sample - (CLARIFICATION)

Can I get a clarification on JMS and AXIS (or any webservice for that
matter).  If you wrap a webservice call in a jms call, all that really does
is spin off a thread.  However, the http call initiated inside the thread
itself is still synchronous.  That is, the webservice call can timeout
within the jms thread waiting for its response.  Am I correct?


-----Original Message-----
From: Kevin Wang [mailto:kwang@farelogix.com]
Sent: Thursday, November 21, 2002 3:47 PM
To: axis-user@xml.apache.org
Subject: RE: JMS sample



Hi Jaime,

Can I archieve this using AXIS API:
VM1 --(request)--> VM2 --(forward request)--> VM3 --(response)--> VM1?
(do we need change the code to allow user set replyTo to a nontemporary
wellknown destination?)


or I have to use this way:
VM1 <--(request/response)--> VM2 <--(request/response)--> VM3?

Thanks,
Kevin


RE: JMS sample - (CLARIFICATION)

Posted by Jaime Meritt <jm...@sonicsoftware.com>.
Jon,

There is no HTTP call involved when using the Axis transport.  The JMS
message contains the SOAP request.  The AxisServer (or any other server
with JMS support) that is listening on the other end gets the request,
invokes a service and sends the response back over JMS.  Since there is
no HTTP involved, the request is not bound to an HTTP timeout of any
kind.  Does that clarify issues or further muddle them?

Thanks,
Jaime 

-----Original Message-----
From: Asbell, Jonathan [mailto:Jonathan_Asbell@McGraw-Hill.com] 
Sent: Thursday, November 21, 2002 4:17 PM
To: 'axis-user@xml.apache.org'
Subject: RE: JMS sample - (CLARIFICATION)

Can I get a clarification on JMS and AXIS (or any webservice for that
matter).  If you wrap a webservice call in a jms call, all that really
does
is spin off a thread.  However, the http call initiated inside the
thread
itself is still synchronous.  That is, the webservice call can timeout
within the jms thread waiting for its response.  Am I correct?


-----Original Message-----
From: Kevin Wang [mailto:kwang@farelogix.com]
Sent: Thursday, November 21, 2002 3:47 PM
To: axis-user@xml.apache.org
Subject: RE: JMS sample



Hi Jaime,

Can I archieve this using AXIS API:
VM1 --(request)--> VM2 --(forward request)--> VM3 --(response)--> VM1?
(do we need change the code to allow user set replyTo to a nontemporary
wellknown destination?)


or I have to use this way:
VM1 <--(request/response)--> VM2 <--(request/response)--> VM3?

Thanks,
Kevin