[jira] Resolved: (CXF-3191) SOAP binding is not propagating checked exceptions through interfaces generated from IDL

["Fred Dushin (JIRA)" <ji...@apache.org>]

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

Fred Dushin resolved CXF-3191.
------------------------------

    Resolution: Not A Problem

It turns out that my test case is in error.

If you want to propagate an exception back to the client, you need to use the form of exception constructor that supports the embedded message type as a parameter.  If you fail to include this parameter, the exception will not make it back to the client.

Next time, I should read the spec.  But that does seem like odd behavior (shameless defense of my own ignorance).

> SOAP binding is not propagating checked exceptions through interfaces generated from IDL
> ----------------------------------------------------------------------------------------
>
>                 Key: CXF-3191
>                 URL: https://issues.apache.org/jira/browse/CXF-3191
>             Project: CXF
>          Issue Type: Bug
>          Components: Soap Binding
>    Affects Versions: 2.2.12
>            Reporter: Fred Dushin
>         Attachments: CXF-3191.tar.gz
>
>
> I have generated WSDL and Java sources from IDL.
> The IDL contains the definition of an interface with an operation that contains a checked exception (which is also defined in IDL).
> The servant throws this exception in its implementation.
> However, the exception is not getting propagated back to the client; instead, the client is receiving a javax.xml.ws.soap.SOAPFaultException.
> I have confirmed separately that the causing exception is not getting marshaled back to the client.
> Stand-alone test case (maven) to be submitted shortly.
> I will add any subsequent analysis to this ticket.

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