Re: Re: [Webmacro-devel] ContextTool replacement and thread-safety

[Marc P. <ma...@an...>]

On Sat, 26 Jul 2003 21:10:00 +0100, Marc Palmer <ma...@an...> wrote:

>> As far as the latter, you are so far from convincing me (and I think
>> everyone else) that we need to inspect and potentially call methods on
>> everything that gets put() into the context that you should probably
>> consider that concept vetoed.
>
> I know - my point is that this should be EITHER/OR. I firmly believe, if 
> everyone thinks that Context should now do the instanceof ContextAware 
> thing - alternative overriden put() is a better solution - that Context 
> should not do a check for ContextTool(s) and init them - the abstracted 
> factory logic should do this.

Sorry - that should read:

I know - my point is that this should be EITHER/OR. I firmly believe, if 
everyone thinks that Context should NOT do the instanceof ContextAware 
thing in put() - alternative overriden put() is a better solution - that 
Context should not do a check for ContextTool(s) and init them - the 
abstracted factory logic should do this.

...but that is the last I will say on this. We're arguing about 2 lines of 
code, the net effect of which will be identical, it just affects the 
modularity of the LazyVariableProvider.

Adios, I'm off to bed. I can't wait for my recurring ContextTool 
nightmare... oh no, that's the waking hours!

-- 
Marc Palmer
Contract Java Consultant/Developer
			
                        w a n g j a m m e r s

                 java and web software design
              experts with an ethical outlook

                   http://www.wangjammers.org