You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Glen Daniels <gd...@allaire.com> on 2001/01/08 01:05:18 UTC
AXIS ISSUE 5: Orthogonal fault information in a single message
I would like to note, regarding this issue, that the XP working group has
taken dealing with intermittently connected, low-bandwidth, and
resource-constrained devices as part of their requirements. In other words,
XP will be designed to enable running it on WAP phones, pagers, etc.
I think this kind of scenario is a perfect example for why it might be a
good thing to pass back a combined Fault message with as much composable
information as possible for the client, avoiding unnecessary round-trips.
Regardless of how we implement the actual Chainable API (ISSUE 1), I think
it's essential to include mechanisms for easily allowing this sort of thing.
We had discussed, for instance, a mechanism by which Handlers could place
headers destined for the outgoing message in a special place in the Context,
to be picked up by a later handler on the output chain. I'd like to make
sure we formalize this somehow if we go with the one-message model.
I do understand and agree with the thought that at times you won't want to
expose the service's "internal structure" due to security constraints, but I
think that's easily solved with two classes of Fault; one that stops
processing immediately and one that can compose. In any case, composition
can only go so far with SOAP 1.1, as the FaultCode element is either going
to be MustUnderstand or Client, therefore you can't combine the two types of
Fault.
--Glen