Hi Chamikara, Grrr, whose bright idea was mustUnderstand!
It seems to me that what you're asking is that we tell handler writers not to call setProcessed(true) if they want their handlers to work with Sandehsa2. That seems pretty ugly and doesn't fit in with the way the mustUnderstand checking works now... and at a guess, calling setMustunderstand(false) will be MUCH slower than setProcessed(true) Surely it's a general Sandesha2 responsibility to somehow store (and restore) the results of previous handlers which have run or, alternatively re-run the handler? Can't you store away the setProcessed information in the same way you must be storing To, ReplyTo etc etc? David On 23/01/07, Chamikara Jayalath <[EMAIL PROTECTED]> wrote:
Hi All, Currently whenever the AddressingInHandler processes a SOAP Header Block it sets the setProcessed() method to avoid mustUnderstand failures. In Sandesha2 we have a requirement to serialize and deserialize SOAP envelopes before the actual mustUnderstand check. Since the setProcessed() method simply sets an internal boolean variable this information get lost in this process. A solution might be to do 'setMustUnderstand(false)' as well. Is there any reason not to do this ? Thanks, Chamikara
-- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
