Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 76985 invoked from network); 12 Mar 2007 13:45:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Mar 2007 13:45:03 -0000 Received: (qmail 32674 invoked by uid 500); 12 Mar 2007 13:44:59 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 32462 invoked by uid 500); 12 Mar 2007 13:44:58 -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 32451 invoked by uid 99); 12 Mar 2007 13:44:58 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Mar 2007 06:44:58 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [194.125.111.199] (HELO mx1.irishlifepermanent.ie) (194.125.111.199) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Mar 2007 06:44:44 -0700 Received: from emfbdublin.irishlife.ie ([172.20.4.22]) by mx1.irishlifepermanent.ie (0/0) with ESMTP id l2CDM1pB080999 for ; Mon, 12 Mar 2007 13:36:37 GMT (envelope-from John.Turner@irishlife.ie) X-Server-Uuid: 19812B53-E114-4FFB-9D3D-502B7294446E Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: RE: SOAP over JMS setting the replyTo queue Date: Mon, 12 Mar 2007 13:44:08 -0000 Message-ID: <1AB16968E801F34DBB803746673CAD43C73462@serv3031.europa.internal> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SOAP over JMS setting the replyTo queue Thread-Index: AcdkoCptK1CG4TIpTaWQrFWYt6M7rwACyI2w From: "Turner, John" To: axis-user@ws.apache.org X-OriginalArrivalTime: 12 Mar 2007 13:44:08.0885 (UTC) FILETIME=[826F8E50:01C764AC] X-WSS-ID: 69EB86401Z01249408-01-01 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C764AC.8262EA8D" X-Scanned-By: Mailsecure.net X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C764AC.8262EA8D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I concur. You always have the option of enhancing the JMSSender class. I started to do this but could not figure if I was using the client side configuration correctly. =20 Maybe, on the generated client stub you could do =20 stub._getServiceClient().getServiceContext().setProperty( "transport.jms.ReplyTo", "myQueueJNDIName"); =20 Then within JMSSender.invoke check for this property and if it is set use the specified queue as opposed to the temporary queue.=20 =20 ________________________________ =46rom: stuart.bell@aegon.co.uk [mailto:stuart.bell@aegon.co.uk]=20 Sent: 12 March 2007 12:15 To: axis-user@ws.apache.org Subject: RE: SOAP over JMS setting the replyTo queue =20 Hi John,=20 Thanks for that. That's really disappointing though. Given that I am using the JMS api to transmit a SOAP request, you would think that it would have the full capability of JMS to be able to set your replyTo queue. I am finding this really vexing. We use static reply queues very heavily so it is a key requirement that a SOAP engine such as Axis should support this. I don't mind that Axis uses temp queues by default, but at least give the developer the option to override and use a perm queue instead.=20 Cheers,=20 Stuart=20 =20 "Turner, John" =20 12/03/2007 12:00=20 Please respond to axis-user=20 =20 To: axis-user@ws.apache.org=20 cc: =20 Subject: RE: SOAP over JMS setting the replyTo queue=20 See http://issues.apache.org/jira/browse/AXIS2-2266 =20 =20 Axis2 1.1.1 always creates a temporary queue for the response message (within JMSSender.invoke())=20 =20 =20 =20 ________________________________ =46rom: stuart.bell@aegon.co.uk [mailto:stuart.bell@aegon.co.uk]=20 Sent: 12 March 2007 11:31 To: axis-user@ws.apache.org Subject: SOAP over JMS setting the replyTo queue=20 =20 Hi there,=20 I am attemtping to use the JMS transport mechanism to deliver a SOAP message. I am doing this by generating a proxy class through the WSDL2Java tool as my main aim is to use WSDLs to document and publish our services.=20 This approach works up to the point of putting a message on a queue. This I have done, but to engineer a reply has proven difficult. A typical URI that I would use for my jms "protocol" would be:=20 =20 As you can see I am attempting to set the replyTo queue, which is a standard JMS operation. However, I can't seem to find any reference to this parameter and what the correct semantics are for using it. Can anyone tell me if they have set a replyTo queue in such a URI=3F I find it strange that the Axis API does not have a JMSConstant for the reply to field. Can anyone enlighten me about this=3F=20 Thanks,=20 Stuart=20 Stuart Bell eCommerce Application Architect AEGON UK Tel: 0131 549 3553 Email: stuart.bell@aegon.co.uk http://www.aegonse.co.uk Scottish Equitable plc Edinburgh Park Edinburgh EH12 9SE Registered in Scotland (No. 144517) Authorised and regulated by the Financial Services Authority Member of the AEGON Group AEGON Scottish Equitable and AEGON Trustee Solutions are brand names used by Scottish Equitable plc. =46or contact information, visit http://www.aegonse.co.uk/contact EMAIL DISCLAIMER=20 This message is confidential and intended only for the person it's addressed to. If you have been sent it in error and should not have received it, please email it back to the sender and delete it and any copies of it straight away.=20 We may monitor all electronic communications that go through our networks for security and for checking legal, regulatory and professional standards. If you get in touch with us by email, we may keep a record of your name and email address. We don't accept service by Email of court proceedings, other proceedings or formal notices of any kind unless we've agreed to this specifically beforehand in writing. We take care not to send viruses or other malicious software in our emails but like any net user we cannot guarantee that all the communications we send electronically are free from such things. So, for safety's sake, we would suggest that you have in place and use virus detection software.=20 -- This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorised to be responsible =66or the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do.=20 If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of this message to the intended addressee, you should destroy this message and notify us immediately.=20 Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the intended recipient or other person authorised in writing by us to receive it, howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof. Irish Life Assurance plc (trading as Irish Life) is regulated by the =46inancial Regulator. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D http://www.aegonse.co.uk Scottish Equitable plc Edinburgh Park Edinburgh EH12 9SE Registered in Scotland (No. 144517) Authorised and regulated by the Financial Services Authority Member of the AEGON Group AEGON Scottish Equitable and AEGON Trustee Solutions are brand names used by Scottish Equitable plc. =46or contact information, visit http://www.aegonse.co.uk/contact EMAIL DISCLAIMER=20 This message is confidential and intended only for the person it's addressed to. If you have been sent it in error and should not have received it, please email it back to the sender and delete it and any copies of it straight away.=20 We may monitor all electronic communications that go through our networks for security and for checking legal, regulatory and professional standards. If you get in touch with us by email, we may keep a record of your name and email address. We don't accept service by Email of court proceedings, other proceedings or formal notices of any kind unless we've agreed to this specifically beforehand in writing. We take care not to send viruses or other malicious software in our emails but like any net user we cannot guarantee that all the communications we send electronically are free from such things. So, for safety's sake, we would suggest that you have in place and use virus detection software. -- This is a confidential communication and is intended only for the addressee= = indicated in the message (or duly authorised to be responsible for the = delivery of the message to such person). You are specifically prohibited = =66rom copying this message or delivering the same, or any part thereof, to= = any other person, whomsoever or howsoever, unless you receive written = authorisation from us to do.=20 If you are anyone other than the intended addressee, or person duly = authorised and responsible for the delivery of this message to the intended= = addressee, you should destroy this message and notify us immediately.=20 Please note that we accept no responsibility whatsoever in the event that = this message or any other email message or any part thereof becomes known o= r= is communicated to anyone other than the intended recipient or other perso= n= authorised in writing by us to receive it, howsoever arising and disclaim = all liability for any losses or damage which may be sustained by any person= = as a result thereof. Irish Life Assurance plc (trading as Irish Life) is regulated by the = =46inancial Regulator. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ------_=_NextPart_001_01C764AC.8262EA8D Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable

I concur.  You always have the = option of enhancing the JMSSender class.  I started to do this but could not =66igure if I was using the client side configuration = correctly.

 

Maybe, on the generated client stub you could do

 

      &n= bsp; stub._getServiceClient().getServiceContext().setProperty(=

      &n= bsp;     "transport.jms.ReplyTo", = "myQueueJNDIName");

 

Then within JMSSender.invoke check for this property and if it is set use the specified queue as opposed to the temporary queue.

 

From:= stuart.bell@aegon.co.uk [mailto:stuart.bell@aegon.co.uk]
Sent: 12 March 2007 12:15
To: axis-user@ws.apache.org
Subject: RE: SOAP over JMS = setting the replyTo queue

 


Hi John,


Thanks =66or that.  That's really disappointing though.  Given that I am= = using the JMS api to transmit a SOAP request, you would think that it would have = the =66ull capability of JMS to be able to set your replyTo queue.  I am = =66inding this really vexing.  We use static reply queues very heavily so it is a key requirement that a SOAP engine such as Axis should support this.  I don't mind that Axis uses temp queues by default, but at least give the developer the option to override and use a perm queue instead.=

Cheers,


Stuart


 

"Turner, John" <John.Turner@irishlife.ie>

12/03/2007 12:00
Please respond to axis-user

        =
        To:        axis-user@ws.apache.org
        cc:        
 = =        Subject:        RE: SOAP over JMS setting the replyTo = queue




See http://issues.apache.org/jira/= browse/AXIS2-2266
 
Axis2 1.1.1 always creates a temporary queue for the = response message (within JMSSender.invoke())
 
 

 


From: stuart.bell@aegon.co.uk [mailto:stuart.bell@aegon.co.uk]
Sent: 12 March 2007 11:31
To: axis-user@ws.apache.org
Subject: SOAP over JMS setting the replyTo queue =
 

Hi there,

I am attemtping to use the JMS transport mechanism to deliver a SOAP = message.  I am doing this by generating a proxy class through the WSDL2Java tool as my = main aim is to use WSDLs to document and publish our services.

This approach works up to the point of putting a message on a queue. =  This I have done, but to engineer a reply has proven difficult.  A typical = URI that I would use for my jms "protocol" would be: =

<soap:address location=3D"jms:/queue=3Fdestination=3DSTUART.IN&amp;= connectionFactory=3DmyQCF&amp;initialContextFactory=3Dcom.sun.jndi.fsco= ntext.RefFSContextFactory&amp;timeout=3D5000&amp;targetService=3DPr= oduct_Version_V002JMS_SOAP_Service&amp;initialContextFactory=3Dcom.sun.= jndi.fscontext.RefFSContextFactory&amp;jndiProviderURL=3Dfile:/h://bind= ings&amp;replyDestination=3DSTUART.REPLY"/> =

As you can see I am attempting to set the replyTo queue, which is a standard JMS operation.  However, I can't seem to find any reference to this parameter and what the correct semantics are for using it.  Can anyone tell me if they have set a replyTo queue in such a URI=3F  I find it = strange that the Axis API does not have a JMSConstant for the reply to field. =  Can anyone enlighten me about this=3F

Thanks,


Stuart

Stuart Bell
eCommerce Application Architect
AEGON UK
Tel: 0131 549 3553
Email: stuart.bell@aegon.co.uk







http://www.aegonse.co.uk

Scottish Equitable plc
Edinburgh= = Park
Edinburgh
EH12 9SE

Registered in Scotland (No. 144517)
Authorised and regulated by the Financial Services Authority
Member of the AEGON Group
AEGON Scottish Equitable and AEGON Trustee Solutions are brand names used by Scottish Equitable plc.

=46or contact information, visit = http://www.aegonse.co.uk/contact


EMAIL DISCLAIMER

This message is confidential and intended only for the person it's addressed to. If you have been sent it in error and should not have received it, = please email it back to the sender and delete it and any copies of it straight = away.

We may monitor all electronic communications that go through our networks = =66or security and for checking legal, regulatory and professional standards. If = you get in touch with us by email, we may keep a record of your name and email address.

We don't accept service by Email of court proceedings, other proceedings or= = =66ormal notices of any kind unless we've agreed to this specifically beforehand in writing.

We take care not to send viruses or other malicious software in our emails = but like any net user we cannot guarantee that all the communications we send electronically are free from such things. So, for safety's sake, we would suggest that you have in place and use virus detection = software.

--
This is a confidential communication and is intended only for the addressee indicated in the message (or duly authorise= d= to be responsible for the delivery of the message to such person). You are specifically prohibited from copying this message or delivering the same, or any part thereof, to any other person, whomsoever or howsoever, unless you receive written authorisation from us to do.

If you are anyone other than the intended addressee, or person duly authorised and responsible for the delivery of = this message to the intended addressee, you should destroy this message and = notify us immediately.

Please note that we accept no responsibility whatsoever in the event that this message or any other email message or any part thereof becomes known or is communicated to anyone other than the = intended recipient or other person authorised in writing by us to receive it, = howsoever arising and disclaim all liability for any losses or damage which may be sustained by any person as a result thereof.

Irish Life Assurance plc (trading as Irish = Life) is regulated by the Financial Regulator.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D





http://www.aegonse.co.uk

Scottish Equitable plc
Edinburgh Park
Edinburgh
EH12 9SE

Registered in Scotland (No. = 144517)
Authorised and regulated by the Financial Services = Authority
Member of the AEGON Group
AEGON Scottish Equitable and AEGON Trustee Solutions are brand names used by Scottish Equitable plc.

For contact information, visit http://www.aegonse.co.uk/contact


EMAIL DISCLAIMER

This message is confidential and intended only for the person it's addressed to. If you have been sent it in error and should not = have received it, please email it back to the sender and delete it and any copie= s= of it straight away.

We may monitor all electronic communications that go = through our networks for security and for checking legal, regulatory and = professional standards. If you get in touch with us by email, we may keep a record of = your name and email address.

We don't accept service by Email of court proceedings, = other proceedings or formal notices of any kind unless we've agreed to this specifically beforehand in writing.

We take care not to send viruses or other malicious = software in our emails but like any net user we cannot guarantee that all the communications we send electronically are free from such things. So, for safety's sake, we would suggest that you have in place and use virus = detection software.

--
This is a confidential communication and is intended only for the addressee=
 =
indicated in the message (or duly authorised to be responsible for the =
delivery of the message to such person). You are specifically prohibited =
=66rom copying this message or delivering the same, or any part thereof, to=
 =
any other person, whomsoever or howsoever, unless you receive written =
authorisation from us to do.=20

If you are anyone other than the intended addressee, or person duly =
authorised and responsible for the delivery of this message to the intended=
 =
addressee, you should destroy this message and notify us immediately.=20

Please note that we accept no responsibility whatsoever in the event that =
this message or any other email message or any part thereof becomes known o=
r=
 is communicated to anyone other than the intended recipient or other perso=
n=
 authorised in writing by us to receive it, howsoever arising and disclaim =
all liability for any losses or damage which may be sustained by any person=
 =
as a result thereof.

Irish Life Assurance plc (trading as Irish Life) is regulated by the =
=46inancial Regulator.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D

------_=_NextPart_001_01C764AC.8262EA8D--