On Fri, Nov 12, 2010 at 10:43 AM, Willem Jiang <[email protected]>wrote:
> > On 11/12/10 5:21 PM, Stephane Nicoll wrote: > >> Hi Dan, >> >> Thanks for the tip. There is indeed a difference between CXF 2.2.11 and >> CXF >> 2.3.0 with the exact same configuration (I just flip the cxf version in my >> pom and rerun my simple unit test with embedded Jetty). >> >> The destinationFactory is not the same (see >> org.apache.cxf.endpoint.AbstractEndpointFactory): >> >> * CXF 2.2.11: >> org.apache.cxf.transport.http_jetty.JettyHTTPTransportFactory >> * CXF 2.3: org.apache.cxf.binding.soap.SoapTransportFactory >> > > 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? Nice. Will do. In the meantime, I have found that overriding the JettyHTTPTransportFactory bean configuration with the one from CXF 2.2.11 fixes my issue ! I have reported the problem now I have found a way to workaround it: https://issues.apache.org/jira/browse/CXF-3119 <https://issues.apache.org/jira/browse/CXF-3119>Thanks! S.
