Return-Path: 
 <commons-dev-return-16941-qmlist-jakarta-archive-commons-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@apache.org
Received: (qmail 44593 invoked from network); 2 Oct 2002 19:52:11 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 2 Oct 2002 19:52:11 -0000
Received: (qmail 21192 invoked by uid 97); 2 Oct 2002 19:52:56 -0000
Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org
Received: (qmail 21155 invoked by uid 97); 2 Oct 2002 19:52:55 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 21143 invoked by uid 98); 2 Oct 2002 19:52:54 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
Message-ID: 
 <8F015E4D786CD411912200D0B746EB9103589287@pobox.offix.musicmatch.com>
From: Jason Horman <jhorman@musicmatch.com>
To: "'commons-dev@jakarta.apache.org'" <commons-dev@jakarta.apache.org>
Subject: [jelly] variable scope
Date: Wed, 2 Oct 2002 12:52:52 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C26A4D.4B09BA70"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

------_=_NextPart_001_01C26A4D.4B09BA70
Content-Type: text/plain;
	charset="iso-8859-1"

I am creating objects via "usebean" that are quite large, 300-400mbs. What
are my options currently for removing these objects from memory once I am
done with them?
 
Right now I am doing this:
 
<useBean var="largeObject" class="blah"/>
 
<bsh:script>
    jellyContext.removeVariable("largeObject");
</bsh:script>

I noticed that some jelly variables, like "set", have a scope attribute but
it seems to be used to differenciate between container scopes. I think that
a new "scope" or "block" tag with its own context scope could be useful.
Something similar to language { } blocks.
 
<jelly>
 
    <scope>
        <set var="var1" />
        <useBean var="var2" />
    </scope>
 
    <!-- var1 and var2 no longer exist -->
 
</jelly>
 
It seems pretty easy to implement, the scope tag just has to pass along a
new context object to its children.
 
-jason
 
This email message and any attachments are for the sole use of the intended
recipient(s) and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited. If you
are not the intended recipient or his/her representative, please contact the
sender by reply email and destroy all copies of the original message.

------_=_NextPart_001_01C26A4D.4B09BA70--