(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.