Per this message in the February 2007 thread entitled "HTTP dependency/decoupling issue", Jetty is supposed to be an optional dependency for the client side:
http://mail-archives.apache.org/mod_mbox/incubator-cxf-dev/200702.mbox/[EMAIL PROTECTED] Specifically, it says: Of course, there may still be a client-side runtime dependency on Jetty if the client is configured to launch a decoupled response endpoint. When I try to start my client and invoke a SOAP-over-HTTP operation without the Jetty dependency on my class path, I see the following exception: ,---- | javax.xml.ws.WebServiceException: org.apache.cxf.interceptor.Fault: No conduit initiator was found for the namepsace http://schemas.xmlsoap.org/soap/http. | [...] | Caused by: org.apache.cxf.interceptor.Fault: No conduit initiator was found for the namepsace http://schemas.xmlsoap.org/soap/http. | at org.apache.cxf.endpoint.AbstractConduitSelector.getSelectedConduit(AbstractConduitSelector.java:89) | at org.apache.cxf.endpoint.UpfrontConduitSelector.prepare(UpfrontConduitSelector.java:62) | at org.apache.cxf.endpoint.ClientImpl.prepareConduitSelector(ClientImpl.java:369) | at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:212) | at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) | at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:125) | ... 7 more | Caused by: org.apache.cxf.BusException: No conduit initiator was found for the namepsace http://schemas.xmlsoap.org/soap/http. | at org.apache.cxf.transport.ConduitInitiatorManagerImpl.getConduitInitiator(ConduitInitiatorManagerImpl.java:96) | at org.apache.cxf.endpoint.AbstractConduitSelector.getSelectedConduit(AbstractConduitSelector.java:71) | ... 12 more `---- What do I have to do to configure my client to not "launch a decoupled response endpoint", if that is indeed what's causing this failure? That is, my goal is to not rely on Jetty if it's possible not to. -- Steven E. Harris
