Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 11545 invoked from network); 26 May 2006 18:38:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 May 2006 18:38:53 -0000 Received: (qmail 96612 invoked by uid 500); 26 May 2006 18:38:42 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 96601 invoked by uid 500); 26 May 2006 18:38:42 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 96590 invoked by uid 99); 26 May 2006 18:38:42 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 May 2006 11:38:42 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=HTML_MESSAGE,NO_REAL_NAME,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of ozgur.y.gurkan@accenture.com designates 170.252.248.71 as permitted sender) Received: from [170.252.248.71] (HELO amrmr1002.accenture.com) (170.252.248.71) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 May 2006 11:38:39 -0700 Received: from AMRXV1002.dir.svc.accenture.com (amrxv1002.dir.svc.accenture.com [10.10.160.62]) by amrmr1002.accenture.com (8.13.6/8.13.6) with ESMTP id k4QIc2BX007293 for ; Fri, 26 May 2006 13:38:18 -0500 (CDT) Received: from AMRXR1002.dir.svc.accenture.com ([170.252.31.72]) by AMRXV1002.dir.svc.accenture.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 May 2006 13:38:15 -0500 Received: from AMRXM1107.dir.svc.accenture.com ([10.10.160.35]) by AMRXR1002.dir.svc.accenture.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 26 May 2006 13:38:15 -0500 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C680F3.8C5753D3" Subject: RE: Controlling the reply destination of the SOAP client for IN-OUT sync pattern Date: Fri, 26 May 2006 13:37:52 -0500 Message-ID: Importance: normal Priority: normal In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Controlling the reply destination of the SOAP client for IN-OUT sync pattern Thread-Index: AcaA5nMcjhXa6FeASMS7BpEiUcxYkwADOxHQ From: To: X-OriginalArrivalTime: 26 May 2006 18:38:15.0050 (UTC) FILETIME=[8C9326A0:01C680F3] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C680F3.8C5753D3 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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.=20 =20 Thanks, Ozzie ________________________________ From: ozgur.y.gurkan@accenture.com [mailto:ozgur.y.gurkan@accenture.com] 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 =20 I have a question about the JMS usage in Axis2. I see the following snippet in the SendSession inner class: =20 byte[] call(JMSEndpoint endpoint, byte[] message, long timeout, HashMap properties) throws Exception { Destination reply =3D createTemporaryDestination(); MessageConsumer subscriber =3D createConsumer(reply); BytesMessage jmsMessage =3D m_session.createBytesMessage(); =20 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? =20 "jms:/TestRequestQueue?replyDestination=3DTestResponseQueue&connectionFac= t ory=3DConnectionFactory" =20 I should be able to direct the client to listen on the "replyDestination" parameter. =20 Thanks, Ozgur (Ozzie) Gurkan Wellpoint Member 2 - SAF Team Cell: 404-641-3381 Pager: ozzie@emailtreo.com =20 =20 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. ------_=_NextPart_001_01C680F3.8C5753D3 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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: ozgur.y.gurkan@accenture.com [mailto:ozgur.y.gurkan@accenture.com]
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 =3D = createTemporaryDestination();

         =        MessageConsumer subscriber =3D = createConsumer(reply);

         =        BytesMessage jmsMessage =3D = 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=3DTestRe= sponseQueue&connectionFactory=3DConnectionFactory”

 

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: ozzie@emailtreo.co= m

 

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.

------_=_NextPart_001_01C680F3.8C5753D3--