[
http://jira.codehaus.org/browse/XFIRE-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomasz Sztelak closed XFIRE-904.
--------------------------------
Assignee: Tomasz Sztelak (was: Dan Diephouse)
Resolution: Duplicate
Duplicate of XFIRE-890
> Using DOMOutHandler in faulthandler result in soapfaults without a detail
> (and child) element when exception is thrown
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: XFIRE-904
> URL: http://jira.codehaus.org/browse/XFIRE-904
> Project: XFire
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.2, 1.2.3, 1.2.4
> Environment: Windows XP / JBoss AS 4.05GA / Java 5
> Reporter: Ernst-Jan van der Laan
> Assigned To: Tomasz Sztelak
>
> The soapfault detail element is missing when a DOMOutHandler is specified in
> the the service.xml as faulthandler and a exception is thrown from a web
> service. This bug occurs on both XFire 1.2.2 and XFire 1.2.4.
> sevices.xml:
> ...
> <faultHandlers>
> <handler handlerClass="org.codehaus.xfire.util.dom.DOMOutHandler" />
> <handler handlerClass="org.codehaus.xfire.util.LoggingHandler" />
> </faultHandlers>
> I am using a JSR181 annotated class a web service. If I remove the
> faulthandler the detail element, with the exception details in it, re-appears.
> As work arround I created a SendPhaseDOMOutHandler and my own LoggingHandler,
> which run in Phase.SEND instead of Phase.USER.
--
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
