[
https://issues.apache.org/jira/browse/AXIS2-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha C. Perera resolved AXIS2-2266.
--------------------------------------
Resolution: Fixed
Fixed in trunk. Could be applied to the 1.2 branch to get into the next RC as
soon as someone confirms this is fixed as expected.
Allows a client to specify response destination as:
serviceClient.getServiceContext().setProperty(JMSConstants.REPLY_PARAM,
outgoing.client.QuoteQueue");
If a response destination has not been specified by the client, a temporary
queue would be created as before for the response
On the server side, the services.xml could specify a new parameter as:
<parameter name="transport.jms.ReplyDestination"
locked="true">dynamicQueues/outgoing.QuoteQueue</parameter>
This could specify the the JMS destination for any messages that does not have
a replyTo destination set
> Permanent JMS Response Queue
> ----------------------------
>
> Key: AXIS2-2266
> URL: https://issues.apache.org/jira/browse/AXIS2-2266
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: transports
> Affects Versions: 1.1.1
> Environment: Windows XP
> Reporter: John Turner
> Assigned To: Asankha C. Perera
>
> When using the JMS transport a service client stub specifies a temporary JMS
> queue as the ReplyTo destination. A useful feature would be to be able to
> configure a permanent ReplyTo queue for the generated client stub and the
> service endpoint. In a request/response communication the association would
> be made through the message id or correlation id.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
