axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjiva Weerawarana <>
Subject Re: Axis2 Architecture problems.
Date Sun, 03 Jun 2007 03:13:26 GMT
OK so if there's no disagreement can we go ahead with this? This means the 
set of handlers is determined at deployment time, unless the flag is set 
and the user wants dynamic control over it.


Deepal Jayasinghe wrote:
>> Deepal Jayasinghe wrote:
>>> The main reason behind handler chain clone was to support dynamic
>>> modification of the chain, that is some one can change the current
>>> handler chain while he is processing the message. So we clone the
>>> template handler chain and store that in the message context.
>> This particular feature I've always felt is YAGNI. AFAIK we don't have
>> a single use-case for this right now .. so why don't we introduce a
>> flag "cloneHandlerChain" which is false by default and we document it
>> and tell people to set a parameter (globally or in services.xml) to
>> set it if they want the thing cloned.
> Yes when we discuss this at the  One of the ApacheCon , I also did not
> agree initially but since Glen had strong arguments I had to agree . But
> I still did not find any useful use case so I am +1 on removing that.
> Thanks
> Deepal
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation;
Founder, Chairman & CEO; WSO2, Inc.;
Director; Open Source Initiative;
Member; Apache Software Foundation;
Visiting Lecturer; University of Moratuwa;

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message