[ http://jira.codehaus.org/browse/XFIRE-804?page=all ]
Tomasz Sztelak closed XFIRE-804.
--------------------------------
Resolution: Won't Fix
FaultInfoException works as described in docs, but its decide what exception to
use based on executed method, so it won't work if you thrown exception from
other handler. But you can easily create your own FaulHandler which will do
this, as described in first part of
http://xfire.codehaus.org/Fault+and+Exception+Handling ( or just take a look at
CustomFaultHandler source code) .
> using FaultInfoException as described in the User Guide doesn't work
> --------------------------------------------------------------------
>
> Key: XFIRE-804
> URL: http://jira.codehaus.org/browse/XFIRE-804
> Project: XFire
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.2
> Reporter: Matthew
> Assigned To: Tomasz Sztelak
>
> I created the Exception class inheriting from FaultInfoException. I threw
> that exception in a handler and traced through the code and it never tried to
> check if my exception was of the type FaultInfoException and the resulting
> fault message did not have any detail element.
> It would also be nice if this FaultInfoException allowed setting other
> elements of the fault message like code and subcode.
--
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
