[
https://issues.apache.org/jira/browse/CXF-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995611#comment-12995611
]
aaron pieper commented on CXF-3342:
-----------------------------------
Yes, oops, I just caught this bug myself! Sorry, I'm still kind of testing the
patch myself; I may have posted it prematurely.
> NullPointerException in Soap12FaultOutInterceptor when an exception is thrown
> from a SOAP 1.2 endpoint
> ------------------------------------------------------------------------------------------------------
>
> Key: CXF-3342
> URL: https://issues.apache.org/jira/browse/CXF-3342
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 2.2.11, 2.3.2
> Reporter: aaron pieper
> Attachments: exception.txt, patch.txt
>
>
> I'm implementing a web service using CXF. After upgrading the CXF endpoint
> from SOAP 1.1 to SOAP 1.2, error handling no longer works properly. Instead
> of receiving SOAP faults from the web service, I receive an empty document,
> which breaks my client software. A stack trace is logged on the web server.
> The stack trace includes the following:
> java.lang.NullPointerException
> at
> org.apache.cxf.staxutils.W3CDOMStreamWriter.writeNamespace(W3CDOMStreamWriter.java:209)
> at org.apache.cxf.staxutils.StaxUtils.getUniquePrefix(StaxUtils.java:1287)
> at
> org.apache.cxf.binding.soap.interceptor.Soap12FaultOutInterceptor$Soap12FaultOutInterceptorInternal.handleMessage(Soap12FaultOutInterceptor.java:77)
> at
> org.apache.cxf.binding.soap.interceptor.Soap12FaultOutInterceptor$Soap12FaultOutInterceptorInternal.handleMessage(Soap12FaultOutInterceptor.java:55)
>
> It looks like Soap11FaultOutInterceptor has some code to handle a special
> case where writer.getPrefix() returns null, and that this code wasn't copied
> over to Soap12FaultOutInterceptor.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
