Hi, I've read the 'integrate-cxf-with-servicemix.html' doc and looked at the unit tests and still can't configure my ServiceMix 3.3.1 cxf-bc to use JMS; it's using the HTTP conduit instead. My cxf-bc 'xbean' configuration is only a few lines long:
<beans xmlns:cxfbc="http://servicemix.apache.org/cxfbc/1.0"; xmlns:service="http://beans.demo"; xmlns:jms="http://cxf.apache.org/transports/jms"; > <cxfbc:provider wsdl="classpath:CreditCheck.wsdl" service="service:CreditProcessor" endpoint="CreditCheckJMS" /> </beans> Note that I don't specify a 'locationURI' as I'm not sure what it should be given I'm using JMS and not HTTP. I'm also not specifying any kind of bus configuration. My (partial) WSDL is below: <wsdl:binding name="CreditCheckBinding"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http"; style="document" /> (I tried using the following transport setting to no effect: transport="http://cxf.apache.org/transports/jms"; ) As a child of my <wsdl:port> element (not shown here), I have a bunch of <jms:address> configuration data. If I don't specify 'locationURI' in the xbean, I get an NPE from CxfBcProvider when it attempts to get an address from the EndpointInfo. If I do specify a 'locationURI', I get an HTTP connection error as my URI doesn't exist. These errors occur when I attempt to send data to the cxf-bc and not when I deploy it to the container; it deploys just fine. In every case, I see that an HTTP conduit is being used, not a JMS conduit as I would expect. How do I configure my CXF-BC to use JMS? Is it done in the xbean or the WSDL? Thanks, Garry -- View this message in context: http://www.nabble.com/Can%27t-get-CXF-BC-to-use-JMS-transport-tp16569577p16569577.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
