[
https://issues.apache.org/jira/browse/CXF-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897362#action_12897362
]
Daniel Kulp commented on CXF-2384:
----------------------------------
You'll probably need to provide a full test case. If you see the test that was
added for this:
http://svn.apache.org/viewvc/cxf/trunk/systests/jaxws/src/test/java/org/apache/cxf/systest/dispatch/DispatchClientServerTest.java?view=markup
(line 128) you can see it specifically asserts that it's not a
SOAPFaultException.
> SOAPFaultExcption thrown instead of a WebServiceException
> ---------------------------------------------------------
>
> Key: CXF-2384
> URL: https://issues.apache.org/jira/browse/CXF-2384
> 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, Service.Mode.MESSAGE);
> SOAPMessage response = dispatch.invoke(request);
> Looking in the API
> (http://java.sun.com/javase/6/docs/api/javax/xml/ws/Dispatch.html#invoke(T)),
> 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.
