toshi - are you stating that handlers should not add headers to the SOAP request message to be processed downstream? or that they should not add MU headers?
How does your proposal reconcile with section 11.2.2, 'Explicit Service Context' of the JAX-RPC spec? in a few notes posted, you state that only handlers can manipulate headers. My read of 11.2.2 indicates that the business logic can access headers and i don't see and exclusion for MU headers. maybe you can point out an error in my interpretation. /Chris On Tue, 19 Aug 2003, Toshiyuki Kimura wrote: > Hi Srinath and All, > > If you assume that the handlers are parts of an ultimate receiver > of JAX-RPC implementation, I think that the following scenario is an > unrecommended usecase. > > Because of; > - A1 has no way programmatically to know whether there're components > (i.e. A2, A3 ...) behind A1, or not. > - MU headers should be processed before starting any business logics. > ( If the MU header, which is added by A1, is refused by A2, > A2#handleRequest() may need to rollback. Who and how ??? ) > > So, I proposed an extension of API as an IF for handling MU headers. > <http://marc.theaimsgroup.com/?l=axis-dev&m=106120252307587&w=2> > >
