[
https://issues.apache.org/jira/browse/CXF-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588740#action_12588740
]
Daniel Kulp commented on CXF-1525:
----------------------------------
I believe this is already fixed on 2.0.6 snapshot as that line no longer even
exists in the DispatchInDatabindingInterceptor. Any chance you can give the
2.0.6 snapshots a try to make sure?
> NullPointer Exception when SOAP FAULT FaultString is NULL
> ---------------------------------------------------------
>
> Key: CXF-1525
> URL: https://issues.apache.org/jira/browse/CXF-1525
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 2.0.4, 2.0.5
> Environment: JBoss 4.2.2, cxf used as a client
> Reporter: Alex F
> Priority: Critical
>
> When a WS returns a SOAP FAULT with an empty FaultString in it a NPE is
> thrown.
> suspicious code:
> DispatchInDatabindingInterceptor handleMessage:
> if (message instanceof SoapMessage) {
> ....
>
> Fault fault = new Fault(new
> org.apache.cxf.common.i18n.Message(soapFault.getFaultString(),
>
> LOG));
> ...
> }
> => soapFault.getFaultString() is NULL this leads in the end to and NPE when
> the field code in the message gets adressed. As a consequence of this the
> original Exception from the WebService is getting ignored.
> yours,
> alex
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
