For one, if the error is coming from com.sun.xml.internal.ws.client, you aren’t using CXF. You are using the jaxws impl built into the JDK. I’d start off by making sure the appropriate CXF jars are found and being picked up.
Next would be to turn on logging and check the soap message being sent to see if it more or less matches what soap-ui is sending. Dan > On May 26, 2016, at 9:38 AM, nicolasduminil > <[email protected]> wrote: > > Hi, > > What do you mean ? Of course it can since it does. And by "a JAX-WS server" > you mean "a JAX-WS service" right ? > > But I probably need to provide more details concerning the web service's > technology. AFAIK, it was developed with Spring-WS and runs in a Tomcat > server, embedded in Spring Boot. > > Anyway, the client generated with SoapUI works and I expect the same from a > client generated with CXF wsdl2java. What does SoapUI do more that any > standard JAX-WS proxy ? > > Makes sense ? > > Kind regards, > > Nicolas > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/com-sun-xml-internal-ws-client-ClientTransportException-The-server-sent-the-status-code-HTTP-406-Note-tp5768944p5768959.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
