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

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

On Sat, 26 Jul 2003 13:55:14 -0700, Brian Goetz <br...@qu...> wrote:

>> Why do we need any of this magical stuff in WebMacro?
>>
>> > So - magic everywhere, or nowhere?
>>
>> Come on Marc, who's side are you on here?  :)  Magic *nowhere*
>>
>
> This seems like a conversation worth having.  I think that while you
> and Marc agree on the idea of ditching (or at least demoting) CT, your
> motivations are different.
>
> Lets talk about this magic thing.  I have always thought that the
> magic "architect selects tools { X, Y, Z } and makes them available
> transparently in all contexts" to be a powerful feature.  Velocity has
> a similar mechanism for loading global macros (which we should have
> too.)

Yes it is, but it should be optional - i.e. replace the LazyVariableFactory 
with your own mechanism for this - app specific class interfaces perhaps... 
i.e.

public interface MyAppContextAwareObject
{
    void init( o.w.Context ctx, MyApplication myapp);
}

> You seem to think its bad, and not in the user's best interest.
> Explain.

As above, and other posts. Crank up the flexilibility, and clean up the 
model at the same time.

:)

-- 
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