[
https://issues.apache.org/jira/browse/CXF-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209839#comment-14209839
]
Alessio Soldano edited comment on CXF-4242 at 11/13/14 2:36 PM:
----------------------------------------------------------------
Talked to Rebecca, looks like the issue is actually still here. I'm providing a
fix soon as mentioned in the description as I don't see any issue/drawback with
it at the moment.
was (Author: asoldano):
Talked to Rebecca, looks like the issue is actually aready here. I'm providing
a fix soon as mentioned in the description as I don't see any issue/drawback
with it at the moment.
> Add exception name to faultstring/detail/stackTrace
> ---------------------------------------------------
>
> Key: CXF-4242
> URL: https://issues.apache.org/jira/browse/CXF-4242
> Project: CXF
> Issue Type: Improvement
> Components: Soap Binding
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: 3.0.2
>
>
> When using faultStackTraceEnabled = true and exceptionMessageCauseEnabled =
> true, it's have the soap message enriched with the exception that caused a
> fault to be generated. The stackTrace element, though, does not include the
> (class) name of the exception that's been thrown.
> I tried a naive fix (i.e. adding
> sb.append(throwable.getClass().getCanonicalName() + " : " +
> throwable.getMessage() + "\n"); into the
> AbstractSoapInterceptor::prepareStackTrace(..) method), but it seems the
> whole fix for CXF-3445 should be revisited (including client side).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
