Hi David ; What do you mean by adding a handler which run at last. I think that is something we can not do b'coz after Dispatching phase its up to the sys admin to decide the phases he want to use , according to your suggestion we need to have a reserved phase in user phase to put that particular handler, if that is the case Im against the idea of removing the code from AxisEngine and putting that as a handler. This will break the flexibility of the handler chain.
Thanks Deepal > Hi all, > I'm looking at using the axis2 engine as part of a larger system which > will have a set of roles which we want respected and perhaps a set of > headers whcih should be ignored for mustUnderstand checking because > anothe rpart of the system will deal with them. > > Currently the mustUnderstand checking is simply a method in > AxisEngine. I'd quite like to pull this out into a handler which runs > last. This would have the advantage that it would be simple for other > people to use in a similar way (perhaps this would be useful for > synapse?) and reduces the complexity of AxisEngine. > > Any thoughts? Objections? > > Cheers, > David > -- Thanks, Deepal ................................................................ "The highest tower is built one brick at a time" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
