Hi Eran; IMHO Stateless does not talk only about across multiple invocations, just like EJB it simply say user should not be looking at the states on the Handler anytime.
In our initial discussion, need to avoid the syncronizing handlers was one of the reason to make things stateless. Stateless Handlers are the simple answer to avoid complexities like this. Srinath On 3/21/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > > Srinath Perera wrote: > > One of the basic assumptions of Axis2 handler architecture is that > > handlers are stateless .. so there should not be attributes in the > > class (expect for HandlerMedatadata). Just notice > > AddressingOutHandler has a attribute that leads to this unpleasant > > surprise > > > Hmm, I think I have done a mistake. But it has nothing to do with the > assumption of handlers being stateless, IMO. > > I have not kept this attribute across multiple invocations of the same > handler. Its *within* one invocation of that handler. > > Anyway, if this leads to synchronization issues, let me keep this in the > message context. > > -- Chinthaka > -- ============================ Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani
