Re: Axis2: soap/jms question

[Asankha C. Perera]

Hi Shantanu I pulled the code from the trunk yesterday and now jms binding is working fine on jboss. Thanks for the fix. Cool! Sorry for the delay in responding to this, as I was actually fixing the below mentioned issue lately 1. Is there a way to specify the temporary queue jndi name for blocking calls using the jms transport? Yes, now there is. See https://issues.apache.org/jira/browse/AXIS2-2266 and the fix is available on the trunk 2. For non-blocking two way operations how can we specify that the response should be published to a separate queue? I did not try this, but if I set the wsa:replyTo from the client, with a jms specific url that specifies the response queue jndi name, will the service pick this up from the wsa:replyTo and publish the response to this queue using the specified url? Yes, See https://issues.apache.org/jira/browse/AXIS2-2266 I would be grateful if you could independently verify this fix using the latest code from trunk, so that I could merge it into the 1.2 branch ASAP to get into the next release asankha --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]