[
https://issues.apache.org/jira/browse/CXF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Dail updated CXF-2511:
----------------------------
Attachment: Soap11FaultOutInterceptor.patch
One branch handled this correctly if the 'detail' element was null. The other
else condition was attempting to create the stackTrace element but was not
including the actual stacktrace. The result was that the stacktrace element was
present but with no content.
Element stackTrace =
detail.getOwnerDocument().createElementNS(
Soap11.SOAP_NAMESPACE, Fault.STACKTRACE);
detail.appendChild(stackTrace);
The fix was to add the line:
stackTrace.setTextContent(sb.toString());
Patch is attached that fixes this issue.
> The Soap11FaultOutInterceptor does not include the stacktrace even if
> FAULT_STACKTRACE_ENABLED is set
> -----------------------------------------------------------------------------------------------------
>
> Key: CXF-2511
> URL: https://issues.apache.org/jira/browse/CXF-2511
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 2.2.3, 2.2.4
> Environment: Windows, Java 6
> Reporter: Chris Dail
> Priority: Minor
> Attachments: Soap11FaultOutInterceptor.patch
>
>
> The stacktrace is not included in the SoapFault that is passed back to the
> client even if the FAULT_STACKTRACE_ENABLED is set to true. In a sample
> service I have the following property configured.
> <jaxws:properties>
> <entry key="faultStackTraceEnabled" value="true"/>
> </jaxws:properties>
> I debugged the issue and found the property was indeed set when it reached
> the Soap11FaultOutInterceptor. I did get to the root of the problem and will
> submit a patch for the fix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
