commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert McIntosh <rob...@bull-enterprises.com>
Subject Re: [jelly] Scope revisited
Date Thu, 13 Mar 2003 23:43:57 GMT
I don't have a use case for events either, but I thought I would throw 
it out there for discussion. I agree that the Scope interface be very 
simple and the context should have a default scope, which can be 
overridden by the user.

~Robert

bob mcwhirter wrote:

>>2. Have/keep the scope listeners and events?
>>    
>>
>
>I personally see Scope as a way to keep me from having to keep writing
>subclasses of JellyContext when I want the context to be backed by my
>own data structure.
>
>Talking with Strachan I think we're pondering 
>
>    context.setDefaultScope( myScope );
>
>In that vein, making Scope very simple be best for my particular
>use-case.
>
>public interface Scope
>{
>    void setVariable(String name, Object value);
>    Object getVariable(String name);
>}
>
>If the JellyContext wants to check for ListenableScope and fire events,
>that's cool, but it'd also be overblown for all of my use-cases.
>
>	-bob
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>  
>


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


Mime
View raw message