On Jun 24, 2005, at 1:38 PM, Kristofer Eriksson wrote:
Secondly, to add to the above topic, I see the change in cache
behavior
(since the patch?!?). When calling a Tag a second time attributes not
specified will have values previously set, as mentioned by Brett.
First call: <mylib:mytag attr1="foo" attr2="boo" />
Second call: <mylib:mytag attr1="foo" />
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 :)
-pete
--
peter royal -> [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
