axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eran Chinthaka <chinth...@opensource.lk>
Subject Re: [Axis2] Some problems in the client side with multiple threading.
Date Wed, 22 Mar 2006 12:29:37 GMT
Nothing to worry I fixed it, as soon as I saw Jaliya's mail.

I was fighting for the wording. Never mind, I had enough wars for the 
day ;-) .

-- Chinthaka


Srinath Perera wrote:
> 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 <chinthaka@opensource.lk> 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
>
>   


Mime
View raw message