[
http://jira.codehaus.org/browse/XFIRE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105934
]
Jean-Louis Pinheiro commented on XFIRE-1081:
--------------------------------------------
That's what I did, and I found that it was the CustomFaultHander that creates
the detail element from the thrown exception.
This handler is executed after the DOMOutHandler and should be executed before.
As a workaround, I created my own CustomFaultHander with the following
constructor :
public CustomFaultHandler() {
super();
setPhase(Phase.POST_INVOKE);
before(DOMOutHandler.class.getName());
}
and I added it to the faultHandlers list.
> The changes done by the FaultSoapSerializerHandler cannot be seen in the
> CurrentMessage.
> ----------------------------------------------------------------------------------------
>
> Key: XFIRE-1081
> URL: http://jira.codehaus.org/browse/XFIRE-1081
> Project: XFire
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.6
> Reporter: Martin Andres Marquez
> Assignee: Dan Diephouse
> Attachments: XFIRE-1081.diff
>
>
> The DOMOutHandler puts the FaultSoapSerializerHandler after it when it should
> be placed before in order to see the changes when it comes to the encryption
> part with wss4j for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
