Things are hairier as I thought, way hairier!
I did it as you suggested but it turns out it's still trying to add to
a component-tag's bean that's null. It seems that findAncestorWithClass
creates new tags spontaneously but not necessarily configuring them
enough (in this case, having a null bea
that's one above your target level, then call invokeBody.
-Original Message-
From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 28, 2004 2:39 AM
To: Jakarta Commons Developers List
Subject: Re: [jelly] should caching be configurable ?
Le 28 sept. 04, à 02:02, Ha
Le 28 sept. 04, à 02:02, Hans Gilde a écrit :
Here's the memory "leak" that was fixed by nulling out the component.
It's not so much of a leak as a "holding on to references that should
be available to the GC":
I might want to build several instances of a JFrame from the same
Jelly script. But,
Here's the memory "leak" that was fixed by nulling out the component. It's
not so much of a leak as a "holding on to references that should be
available to the GC":
I might want to build several instances of a JFrame from the same Jelly
script. But, I may not. I may simply keep that Script around
