[
http://jira.codehaus.org/browse/XFIRE-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94944
]
Holger Hoffstätte commented on XFIRE-710:
-----------------------------------------
2 beers (on Ross!) that this won't be fixed in 1.2.7. :-D
> MessageExchange.hasFaultMessage is always true
> ----------------------------------------------
>
> Key: XFIRE-710
> URL: http://jira.codehaus.org/browse/XFIRE-710
> Project: XFire
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.2
> Reporter: Holger Hoffstätte
> Assignee: Dan Diephouse
> Fix For: 1.2.7
>
>
> (reposted from xfire-dev in the hope that it gets more attention here.. :)
> While debugging a surprising problem in Mule/XFireI found that
> MessageExchange.hasFaultMessage() unconditionally returns true, even
> though the faultMessage field is null. Since the getFaultMessage() getter
> is lazy and seems to ignore the hasFault boolean I cannot use that either.
> I'm stumped: why is hasFault true by default, never read or properly set
> together with the faultMessage reference?
> This confusing behaviour causes us quite a bit of trouble since we need to
> distinguish between a MEX with and without fault, yet there seems to be no
> way to do that correctly.
--
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
