[jira] Resolved: (CXF-2384) SOAPFaultExcption thrown instead of a WebServiceException

["Daniel Kulp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-2384.
------------------------------

    Resolution: Fixed


Re-marking this as resolved as the tests pass.

HOWEVER, this may also be a "won't fix" as I think I know the issue.  CXF delays connecting until a buffer (defaults to 4K fills) or the message finishes writing so that we can flip to non-chunked mode for small messages.   If the connection is made during the writing of larger requests, we may get the exceptions wrapped in a variety of different exceptions (like JAXB exceptions or Stax exceptions and such) and thus may be difficult or impossible to detect.  The workaround is to configure in a larger buffer size.   See ChunkingThreshold info at:
https://cwiki.apache.org/confluence/display/CXF20DOC/Client+HTTP+Transport+(including+SSL+support)

> 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.