Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 35509 invoked from network); 9 Dec 2002 07:58:36 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 9 Dec 2002 07:58:36 -0000 Received: (qmail 7365 invoked by uid 97); 9 Dec 2002 07:59:49 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 7349 invoked by uid 97); 9 Dec 2002 07:59:48 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 7336 invoked by uid 98); 9 Dec 2002 07:59:48 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <01d701c29f58$c4323b80$9865fea9@spiritsoft.com> From: "James Strachan" To: "Jakarta Commons Developers List" References: Subject: Re: [jelly] Subclassing JellyContext Date: Mon, 9 Dec 2002 07:58:29 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > What I meant to say was that a variable _value_ should be visible only in a certain > scope. So there is a stack of values per variable. You could create a number of different contexts each of which can contain different values of a given variable name. e.g. ${foo} ${foo} ${foo} which would output "3 2 1". i.e. that the above implements a stack of variable values of the 'foo' variable. James ------- http://radio.weblogs.com/0112098/ ----- Original Message ----- From: To: Sent: Monday, December 09, 2002 6:48 AM Subject: RE: [jelly] Subclassing JellyContext > Variables should automatically be available to their child > contexts so I > don't think you need to create your own JellyContext for that. What I meant to say was that a variable _value_ should be visible only in a certain scope. So there is a stack of values per variable. > Also the push/pop features can be used by just creating and > using child > context - its rather like using a local block in Java. Ok, I will look into this - this should help. > There's also the > tag which creates a child variable scope, > essentially making any > variables set inside the tag > > One question; where will you be using these typesafe getters > and setters you > want? Will it be inside a Jelly Tag implementation? Unfortunately no. The application has to put about 10 values in the context before the Jelly Tags can do their work. Right now I am doing it via a "ContextHelper" class. Thanks for the help, Mike. -- To unsubscribe, e-mail: For additional commands, e-mail: __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: For additional commands, e-mail: