C. Perera [mailto:[EMAIL PROTECTED]
Sent: Friday, November 14, 2008 11:21 PM
To: Joshi, Shital; axis-user@ws.apache.org
Subject: Re: JMS Transport in Axis2
Hi Shital
Do you mean that next release of Axis2 say (Axis2_1_5
Hi Shital
Going back to my original question, In this latest release will
you have functionality to specify Reply-To property on client side?
Yes, a message context property JMS_REPLY_TO could set the reply
destination, over which a client would wait for the response. I will
Hi Joshi
I am attempting to use the JMS transport in Axis2. We are using*
Tibco* queues. I was able to do one way operation
(_http://www.w3.org/TR/wsdl#_one-way_) over JMS. When I tried to
do request-response operation, I get client already exists JMS
Exception.
, 2008 1:08 PM
To: axis-user@ws.apache.org
Cc: Joshi, Shital
Subject: Re: JMS Transport in Axis2
Hi Joshi
I am attempting to use the JMS transport in
Axis2. We are using Tibco queues. I was able to do one way operation
Hi Shital
I would be happy to work with your team. Do you have a date in mind
for the release which has better JMS Transport?
We are almost code complete.. but would need improved documentation and
samples etc to supplement the new features. I would expect the code to
be checked into svn by
To: axis-user@ws.apache.org
Subject: Re: JMS Transport in Axis2
Hi Shital
I would be happy to work with your team. Do you have a
date in mind for the release which has better JMS Transport?
We are almost code complete
Hi Shital
Do you mean that next release of Axis2 say (Axis2_1_5) will not have
code base for JMS Transport
Yes..
and we'll have include ws-commons library to support JMS Transport?
This will be done for you, most probably automatically with the Axis2
release.. but the specifics are yet to be
