Hi Patrick,
you cannot use the snippet you used to connect to the service you are
trying directly. You will need to have <jms:address .../> configured
with the appropriate info. from the location jms: address. This
translation you can do it in configuration or modify the WSDL it's upto
you. Another thing I noticed is the location starts with "jms:/" and
this won't tell CXF to use JMS transport at client side we need the
location name starting from "jms://" so you will need to modify WSDL
anyway.
Regards,
Ulhas Bhole
Patrick Mulligan wrote:
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!
http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
