> On May 26, 2016, at 12:07 PM, nicolasduminil
> wrote:
>
> Apache CXF 2.4.5
I would start with upgrading to Apache CXF 3.1.6. That version is ANCIENT and
certainly not supported anymore.
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.ta
Okay, adding cxf-rt-transports-http as a dependency solves the previous
exception. Now I'm sure I'm using CXF instead of the default JAX-WS comming
with Java 8. And the result has changed: I'm receiving:
org.apache.cxf.transport.http.HTTPException: HTTP response '401:
Unauthorized' when communicat
Hello,
Many thanks again for this precious information. I added the mentioned
dependency (cxf-rt-frontend-jaxws) to my pom and here is the new
stack-trace:
javax.xml.ws.soap.SOAPFaultException: Could not find conduit initiator for
transport http://schemas.xmlsoap.org/soap/http
at
org.apa
> On May 26, 2016, at 10:26 AM, nicolasduminil
> 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. T
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 ? For the service, as I said, it was developed using Spring WS. As per
the client, it is a JAX-WS
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 s
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.
A
Hi Jens,
You could try using the CXF @Policy annotation on the SEI itself. I added a
test that shows how this can be done:
https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=systests/ws-security/src/test/java/org/apache/cxf/systest/ws/fault/FaultTest.java;h=471f07ce0d6a53d7c869240e19ee494
Hi
Quick question, can a JAX-WS server return 406 ? is it a CXF JAX-WS
server ?
Cheers, Sergey
On 25/05/16 15:44, nicolasduminil wrote:
Greetings,
I have a JAX-WS web service deployed on an app server and I try to call it
via a JAX-WS client generated by the maven cxf-codegen-plugin. But it
