Peter,
I am sorry I wasn't able to take this further yet.
The idea was to introduce something like a reset() method on tags to
ensure that nullity... but if you think we need to disable caching then
we'll have to need a form of method like "doesNeedCaching" which would
then cache in any cases. I know for example such things for Swing or
Define tags (but not per-class).
I still think Cache.reset() is better and Kristofer accept it as an
alternative. Would you ?
thanks
paul
Le 20 juil. 05, à 13:49, peter royal a écrit :
The second time mytag is called, attr2 will still have the value
"boo",
and not null or default value. My question is if this is the desired
behavior, if not, can this be fixed somehow.
I have confirmed this behavior and it is a regression in the way the
memory leak patch is implemented. Trying to figure out how to fix it
now :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
