[
http://jira.codehaus.org/browse/XFIRE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105904
]
Jean-Louis Pinheiro commented on XFIRE-1081:
--------------------------------------------
Thank you for the answer, but I don't understand what you mean.
If I don't add fault handlers in my Xfire configuration, my soap response
doesn't have security headers, but contains a full exception
description in a <detail> element (it is here an exception of type
SofFwkBusinessRuleException).
My client app would then be able to know what was the initial exception (but
fails because it doesn't find the security headers).
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Erreur pour de faux</faultstring>
<detail>
<SofFwkException xmlns="http://interfaces.demo.metiers.soffwk.sofinco.com";
xmlns:ns1="http://exceptions.soffwk.sofinco.com";
xmlns:ns2="http://www.w3.org/2001/XMLSchema-instance";
ns2:type="ns1:SofFwkBusinessRuleException">
<code xmlns="http://exceptions.soffwk.sofinco.com";>00</code><exception
ns2:nil="true" xmlns="http://exceptions.soffwk.sofinco.com"; />
<message xmlns="http://exceptions.soffwk.sofinco.com";>Erreur pour de
faux</message></SofFwkException>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
If I put your patched DOMOutHandler as a fault handler in my xfire
configuration, the soap response contains the requested security
headers, but doesn't contain the detail element anymore.
My client app will not be able to know what was the initial exception.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soap:Header>
<wsse:Security soap:mustUnderstand="1"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>
... <!-- Security headers-->
</wsse:Security>
</soap:Header>
<soap:Body wsu:Id="id-23069842"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Erreur pour de faux</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
I am sorry, but could you detail your answer more precisely, I don't know how
and where I can do what you said ...
> 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
