Hi Patrick,
I don't think CXF JMS transport will recognize the address that you
wrote in the <soap:address>.
Now CXF JMS transport just consumer the address information which define
as <jms:address> which is defined by CXF itself.
You can find some example wsdl here [1].
BTW It looks like your address is coming form soap/jms binding.
Currently CXF do not support it yet.
[1]https://svn.apache.org/repos/asf/incubator/cxf/trunk/testutils/src/main/resources/wsdl/hello_world_doc_lit.wsdl
Willem.
Patrick Mulligan wrote:
This also applies to the binding element as well in terms of generic
applicability, standards, etc. :-)
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: JMS configuration for consumerDate:
Wed, 7 Nov 2007 08:09:39 -0500
Hi, In the JMS configuration docuement (for consumer only in this case), it specified that the configuration can be done either by WSDL or
configuration file. Can this be mixed with a portion in wsdl and configuration? Is the WSDL configuration for JMS consumers standard? That is, is
the syntax of the port element contents standardized or are they specific to a JMS impl? This is a snip from a commercial JMS that I need to connect
to: <wsdl:port binding="tns:ESB_VehicleManagementSOAP_JMS_Binding" name="SOAP_JMS_Port"><soap:address
location="jms:/queue?destination=jms/SoapOutput&connectionFactory=jms/outboundSoapJmsQCF&replyToDestination=jms/SoapInput&targetService=ESB_VehicleManagement_DialogPlus"/></wsdl:port>
Does a cxf jms consumer need to "know" the cxf JMS namespace if definded by wsdl? BTW, we want to have the default tempory queue setup for
request/reply.
Peek-a-boo FREE Tricks & Treats for You! Get 'em!
_________________________________________________________________
Help yourself to FREE treats served up daily at the Messenger Café. Stop by
today.
http://www.cafemessenger.com/info/info_sweetstuff2.html?ocid=TXT_TAGLM_OctWLtagline
