-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi David,
Good idea, I always consider handlers as an optional component in the execution chain, which one can opt to keep out. And at the same time one might try to run Axis2 engine without a single handler. IMO, must understand thing is an absolute requirement and a core component in to a SOAP processing engine. So that is why I like to keep that piece of logic inside the AxisEngine class itself. You might want to improve the existing logic to properly work on the roles but I prefer leaving them as it is. I hope none of your intentions are to allow someone to let the engine to be executed without must understand checking. - -- Chinthaka David Illsley wrote: > 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 > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFtYGmjON2uBzUhh8RAo2RAJ99u3W2o0lIYqrXyzttrYFRjDFwtQCgmQVv 1mw2IH8+OjvOmvDCUdd4kho= =YN6L -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
