So I'm looking at your test, and it looks like one should expect this behavior (the test should always fail). Have you tried this test on a pre-leak-fix version of Jelly? I'm going to do so tomorrow.
This isn't the same caching problem reported by other users. That problem is caused not by repeated invocation of the same script, but by something that is causing the same TagScript to be sued for two XML tags. This makes the second instance use the variables from the first instance. -----Original Message----- From: peter royal [mailto:[EMAIL PROTECTED] Sent: Friday, July 22, 2005 8:19 AM To: Jakarta Commons Developers List Subject: Re: [jelly] 1.0-final problem wrt tag caching On Jul 22, 2005, at 1:34 AM, peter royal wrote: > I'll do what you did and spend some time tomorrow looking at the > failures to see if we can have nirvana (no memory leak + exact > behavior semantics from when we had the leak). > k, i was able to get all the tests in core to pass, including the new one I added about the tag caching. i'm offline so i can't test all the taglibs since i don't have everything needed in my maven repo, but i'm pretty sure they'll be okay too. i'll verify when i'm back online prior to committing. -pete -- peter royal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
