axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glyn Normington" <>
Subject Processing of faults raised after the pivot handler
Date Wed, 16 Jan 2002 10:16:19 GMT
One of the issues described in the draft architecture guide [1] is that if
a fault occurs after the pivot Handler, should the backwards scan notify
Handlers which were invoked prior to the pivot Handler?

The current implementation does notify such Handlers. However, this is not
consistent with the processing of faults raised in a 'downstream' system
and stored in the message context by the pivot Handler. These faults are
passed through any response Handlers, but do not cause onFault to be driven
in the local engine.
We need to understand what's going on here. If you take a sequence of
Handlers and then introduce a distribution boundary (i.e. network hop) into
the sequence, what effect should that have on the semantics of the sequence
in terms of its effects on message contexts? The diagram in the issues
section of [1] shows a client-side Handler sequence invoking a server-side
Handler sequence. We need to consider how the semantics of this combined
sequence compares with the sequence formed by omitting the
transport-related Handlers.


View raw message