Thanks...I'm wondering if explicitly adding a cxf-rt-transports-http-jetty dependency can help, that issue does not exist with the servlet transport being involved... Please, send me the test project if you can and I will look into it
Cheers, Sergey On Mon, May 30, 2011 at 1:47 PM, Bruno Dusausoy <[email protected]> wrote: > On 05/30/2011 12:50 PM, Sergey Beryozkin wrote: > [...] >> >> That is interesting, though a bit unexpected as I can see the >> identical code in 2.3.4 and 2.4.0, as far as the defaulting of the >> trandportId is concerned. >> Can you give me a favor and clarify a couple of things... >> Were you getting the same "No DestinationFactory was found for the >> namespace http://schemas.xmlsoap.org/wsdl/soap/http"; with 2.3.4 ? >> Do you have Spring libs on the runtime classpath ? >> Is http-jetty dependency included given that you use an absolute HTTP >> address ? >> >> Just trying to figure out only some users do get this exception with 2.3.x >> > > Yes, it's the same stack trace, excepting the line number for > JaxRsServerFactoryBean (line 145 for 2.3.3 vs line 160 for 2.3.4). > Same exception whether or not I put your workaround. > > Yes, I have Spring 3.0.5.RELEASE in my runtime classpath. > The only thing I've changed is the version of CXF in my POM, no dependencies > added or removed. > > Hope this helps. > > Regards, Bruno. > > PS : I'll try to do a simple maven project to highlight the problem. > > -- > Pensez environnement : limitez l'impression de ce mail. > Please don't print this e-mail unless you really need to. >
