[
https://issues.apache.org/jira/browse/CXF-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971727#action_12971727
]
Fred Dushin commented on CXF-3191:
----------------------------------
Interesting.
If I manually modify the generated ThrowMe class to return a non-null
ThrowMeType (see item 5 in previous comment), the proper exception type is
returned through the API.
On the wire, I see:
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>foo</faultstring><detail><ns2:ThrowMe
xmlns:ns2="http://cxf.apache.org/test";
/></detail></soap:Fault></soap:Body></soap:Envelope>
> 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.
