You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by st...@aegon.co.uk on 2007/03/12 12:31:01 UTC
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=
"jms:/queue?destination=STUART.IN&connectionFactory=myQCF&initialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory&timeout=5000&targetService=Product_Version_V002JMS_SOAP_Service&initialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory&jndiProviderURL=file:/h://bindings&replyDestination=STUART.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? I find it
strange that the Axis API does not have a JMSConstant for the reply to
field. Can anyone enlighten me about this?
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.
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 copies 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.
RE: SOAP over JMS setting the replyTo queue
Posted by "Turner, John" <Jo...@irishlife.ie>.
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.
Maybe, on the generated client stub you could do
stub._getServiceClient().getServiceContext().setProperty(
"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 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.
Cheers,
Stuart
"Turner, John" <Jo...@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
<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="jms:/queue?destination=STUART.IN&connectionFactory=myQCF&a
mp;initialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory&
timeout=5000&targetService=Product_Version_V002JMS_SOAP_Service&
initialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory&jnd
iProviderURL=file:/h://bindings&replyDestination=STUART.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? I find
it strange that the Axis API does not have a JMSConstant for the reply
to field. Can anyone enlighten me about this?
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.
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
copies 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 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.
========================================================================
======
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
copies 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 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.
==============================================================================
RE: SOAP over JMS setting the replyTo queue
Posted by st...@aegon.co.uk.
Hi John,
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.
Cheers,
Stuart
"Turner, John" <Jo...@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=
"jms:/queue?destination=STUART.IN&connectionFactory=myQCF&initialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory&timeout=5000&targetService=Product_Version_V002JMS_SOAP_Service&initialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory&jndiProviderURL=file:/h://bindings&replyDestination=STUART.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? I find it
strange that the Axis API does not have a JMSConstant for the reply to
field. Can anyone enlighten me about this?
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.
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
copies 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 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.
==============================================================================
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 copies 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.
RE: SOAP over JMS setting the replyTo queue
Posted by "Turner, John" <Jo...@irishlife.ie>.
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="jms:/queue?destination=STUART.IN&connectionFactory=myQCF&a
mp;initialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory&
timeout=5000&targetService=Product_Version_V002JMS_SOAP_Service&
initialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory&jnd
iProviderURL=file:/h://bindings&replyDestination=STUART.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? I find
it strange that the Axis API does not have a JMSConstant for the reply
to field. Can anyone enlighten me about this?
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.
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
copies 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 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.
==============================================================================