Since a bit earlier than the patch, indeed, caching has been activated
by default and caching disablement has been removed. This was needed at
least by some jelly:define tags, as far as I could tell.
Can you give more details ?
- Do you expect the setters to be called at every new run ?
- Would you have enough if having a method accessible such as
"re-run-setters"?
- Alternatively, would you be happy with overall cache-disablement (at
your own risks) ?
- Finally, did you not find a possibility to have setters receive
expressions which, then, get re-evaluated each time needed ? I would
believe this would be the best practice.
thanks
paul
Le 24 juin 05, à 13:38, Kristofer Eriksson a écrit :
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.
Kind Regards
/Kristofer Eriksson
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
