You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Samisa Abeysinghe <sa...@gmail.com> on 2007/06/01 04:03:52 UTC

Re: Axis2 Architecture problems.

Sanjiva Weerawarana 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.
Absolutely +1 for the flag. I too was trying to find a use case for but 
could not find any.

Samisa...

-- 
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org