Reshat Sabiq <crts <at> argushealth.com> writes:
> For an array of subrequests, there is a thought of allowing some of them to
> succeed and others to fail, and not throw a fault upon a failure of a
> subrequests right away. This would entail having a statusCode for each
> subrequests. How common is something like that?
I've seen examples of this. Given that we have regular faults, and we don't
completely stop processing after an exception pertaining to an individual
subrequest, i'm trying to indicate the status of an individual subrequest using
a soap:Fault as well. However, when representing that fault w/ XFireFault, it is
not serialized as a soap:Fault, e.g. shown below. It is instead serialized like
a regular java object. I logged a bug for this.
One thought i have is to represent this as a String field, and serialize it
manually into soap:Fault, so that client can peruse individual status codes
similarly to complete failures indicated by soap:Fault. Is there a better way to
make soap:Fault more declarative?
P.S. This is what i was hoping for as a field of a subrequest:
<soap:Fault>
<soap:Code>
<soap:Value>soap:Sender</soap:Value>
<soap:SubCode>
<soap:Value
xmlns:error="urn:some.urn">error:SomeError</soap:Value>
</soap:SubCode>
</soap:Code>
<soap:Reason>
<soap:Text>Some Error</soap:Text>
</soap:Reason>
<soap:Detail>
<error:detail code="1001"
xmlns:error="urn:some.urn">someField</error:detail>
</soap:Detail>
</soap:Fault>
P.P.S. This is one field's serialization by xfire as of now:
<faultCode xmlns="http://fault.xfire.codehaus.org";>
<localPart
xmlns="http://namespace.xml.javax";>Sender</localPart>
<namespaceURI
xmlns="http://namespace.xml.javax";>http://www.w3.org/2003/05/soap-envelope</namespaceURI>
<prefix xmlns="http://namespace.xml.javax"/>
</faultCode>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
