Ozzie,
Please submit a patch and i'd be very happy to check it in. we ported
some of the JMS stuff from Axis1 and this may have been a mistake
while porting and shows my lack of JMS knowledge :)
thanks,
dims
On 5/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Ideally,
This is what we want:
String replyDestination =
extractReplyDestination(properties);
Destination reply = null;
if( replyDestination != null ) {
reply =
m_session.createQueue(replyDestination);
} else {
reply = createTemporaryDestination();
}
The replyDestination would be provided in the endpoint as a property.
I am testing this approach now.
Any reason why this wasn't added?
Thanks,
Ozzie
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 2:38 PM
To: axis-user@ws.apache.org
Subject: RE: Controlling the reply destination of the SOAP client for
IN-OUT sync pattern
When communicating with the ESB, you are not allowed to create temporary
destinations because this could violate security requirements. There has to
be a better way to not only use the generated stub but also the built-in JMS
Sender without modification.
Thanks,
Ozzie
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 1:04 PM
To: axis-user@ws.apache.org
Subject: Controlling the reply destination of the SOAP client for IN-OUT
sync pattern
I have a question about the JMS usage in Axis2. I see the following snippet
in the SendSession inner class:
byte[] call(JMSEndpoint endpoint, byte[] message, long timeout,
HashMap properties)
throws Exception {
Destination reply = createTemporaryDestination();
MessageConsumer subscriber = createConsumer(reply);
BytesMessage jmsMessage = m_session.createBytesMessage();
According to this, I don't have control over the destination of the reply
for Sync connections. Is this true? If that is the case, I cannot properly
communicate with an EnterpriseServiceBus using the IN-OUT pattern. Am I
missing something here? Is there no way to have the Sync connection receive
on a destination that is provided in the endpoint?
"jms:/TestRequestQueue?replyDestination=TestResponseQueue&connectionFactory=ConnectionFactory"
I should be able to direct the client to listen on the "replyDestination"
parameter.
Thanks,
Ozgur (Ozzie) Gurkan
Wellpoint Member 2 - SAF Team
Cell: 404-641-3381
Pager: [EMAIL PROTECTED]
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete the
original. Any other use of the email by you is prohibited.
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
