> On May 26, 2016, at 10:26 AM, nicolasduminil > <[email protected]> wrote: > > Hello, > > I confirm the exception is raised by > com.sun.xml.internal.ws.client.ClientTransportException. When you're saying > that I'm not using CXF, do you mean on the client side or the service is not > CXF ?
The client side. The “com.sun.xml.internal.ws.client” package is the JAX-WS implementation built into the JDK/JRE. > For the service, as I said, it was developed using Spring WS. As per > the client, it is a JAX-WS proxy generated by the maven plugin for CXF, like > this: > …………. > > There is no any CXF jar. CXF generates (by default) clients that are completely compatible with the JAX-WS standard and thus work with the implementation in the JDK (like you are using) or our own implementation. To use CXF, you would need to add the cxf-rt-frontend-jaxws and it’s dependencies onto the classpath. > As per turning on the logging on the service, how should I dod it in an > embedded Tomcat running in Spring Boot ? I tried to use TCP/IP Monitor. I'm > getting the traffiv when using the SoapUI proxy but when I use the one > generated by wsdl2java nothing appears in the TCP/IP Monotor console and the > HTTP 401 is returned. > > Could you please help further ? Since you are not using CXF at runtime, I’m not sure what to suggest. You should be able to get the client to use the TCP proxy via the normal system properties. Example: -Dhttp.proxyHost=localhost -Dhttp.proxyPort=8080 or similar so that the data would go through the tcp monitor. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
