cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Commented: (CXF-2384) SOAPFaultExcption thrown instead of a WebServiceException
Date Thu, 12 Aug 2010 16:12:20 GMT


Daniel Kulp commented on CXF-2384:

If I comment out the line that starts the server, the test also passes.  

I've also added a test in the same class that tests the case where it's using a correct port,
but a path to where a service isn't running. (aka: gets a 404 return code back)    That is
also passing with a WebServiceException wrappering an IOException.

Thus, everything looks like it's  working correctly from my point of view.   To do much of
anything else, we'll really need a  complete test case.

> SOAPFaultExcption thrown instead of a WebServiceException
> ---------------------------------------------------------
>                 Key: CXF-2384
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.2.2
>         Environment: jdk1.6, ubuntu 9.10
>            Reporter: Niek Palm
>            Assignee: Daniel Kulp
>             Fix For: 2.2.7
> When the connection of the webservice is lost we get a SoapFaultException instead of
of a WebServiceException. We use the dispachter in the following way:
> 	Service service = Service.create(SERVICE_NAME);
> 	service.addPort(PORT_NAME, SOAPBinding.SOAP11HTTP_BINDING, url.toString());
> 	Dispatch<SOAPMessage> dispatch = service.createDispatch(PORT_NAME, SOAPMessage.class,
> 	SOAPMessage response = dispatch.invoke(request);
> Looking in the API  (,
there is specified that any communication problem will cause in a WebServiceException. To
our point of view this is a bug in cxf.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message