On Friday 12 November 2010 5:51:38 am Stephane Nicoll wrote: > On Fri, Nov 12, 2010 at 10:43 AM, Willem Jiang <[email protected]>wrote: > > The SoapTransportFactory will try to locat the real TransportFactory by > > checking the address. > > You can find the code from SoapTransportFactory.getDestination() method. > > > > Can you just set the break point on the JettyHTTPTransportFactory? > > Here is more information about this. In SoapTransportFactory#getDestination > > * bi [BindingInfo http://schemas.xmlsoap.org/wsdl/soap/] > * address = http://localhost:7171/MathWebService > * transId= http://schemas.xmlsoap.org/soap/http > > Which leads to a call on > DestinationFactoryManagerImpl#getDestinationFactory with the > "http://cxf.apache.org/transports/http"; namespace. The problem is that > these are my destination factories: ............ > No Jetty in there and the returned factory is > obviously org.apache.cxf.transport.servlet.servlettransportfact...@b20090 > > I don't understand what is happening. I have the http-jetty jar in my > classpath and I also explicitely added the following in my spring config > file: > <import resource="classpath*:/META-INF/cxf/cxf-extension-http-jetty.xml"/> > > Can we use wildcards for this thing? Maybe I am loading another > configuration file that registers the same transportId with another > protocol? The imports of my project on CXF are: > > <import resource="classpath*:META-INF/cxf/cxf-servlet.xml"/>
That right there is the issue. Why are you pulling in META-INF/cxf/cxf- servlet.xml? That's where the servlet destination is specified. Dan > <import resource="classpath*:META-INF/cxf/cxf.xml"/> > <import resource="classpath*:META-INF/cxf/cxf-extension-*.xml"/> > > HTH, > S. -- Daniel Kulp [email protected] http://dankulp.com/blog
