Hi Martin,
You shouldn't inject the org.apache.cxf.jaxws.JaxWsProxyFactoryBean to
cxf se, you should use cxf proxies described in [1]. Basically cxf
proxies is the ClientProxyFactoryBean but specified transport as JBI, we
hide the transport details for the end user.
And you can take a look the CxfSeClientProxyTest[2] which is exactly
same scenario as you want.
Btw, the cxf http-jetty transport shouldn't be used inside cxf se, I
think it was introduced by your injected JaxWsProxyFactoryBean
[1]http://servicemix.apache.org/servicemix-cxf-se.html
[2]http://svn.apache.org/repos/asf/servicemix/smx3/branches/servicemix-3.2/deployables/serviceengines/servicemix-cxf-se/src/test/java/org/apache/servicemix/cxfse/CxfSeClientProxyTest.java
Freeman
Martin Feeney wrote:
Hi All,
I am trying to call an External Web Service from servicemix. I am
injecting the org.apache.cxf.jaxws.JaxWsProxyFactoryBean as the client
factory and method create in to my CXF SE service unit and on a call I
get an error org.apache.cxf.interceptor.Fault: Could not find conduit
initiator for transport http://schemas.xmlsoap.org/soap/http. I would
prefer to use the proxy client object as apposed to using the CXF BC
and the JBI CLient API. The appropriate dependencies are included
especially cxf-rt-transports-http-jetty-2.1.3.jar. Has anyone achieved
this before and can you enlighten me?
Thanks
