Thanks Ralph
I've checked it out with a very simple test tag. I don't encounter problems using a 1.2 TLD with tag pooling. I suspect the Struts 1.0.2 tags are 1.1. (Am I right in assuming this is what was meant by conformant tags?)
Also, as Remy suggests, disabling tag pooling in 4.1.7 and clearing out the work directory cleared up the issue.
cheers
Rory
-----Original Message-----
From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 09, 2002 11:47 AM
To: Tomcat Users List
Subject: AW: Custom Tag caching bug in 4.1.6, 4.1.7
There has been a little discussion about OSCache
some days ago, that might match your problem.
(See atached mails)
-----Ursprüngliche Nachricht-----
Von: Douglas, Rory [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 9. Juli 2002 17:20
An: Tomcat Users List (E-mail)
Betreff: Custom Tag caching bug in 4.1.6, 4.1.7
In other words, it seems as if an attribute value might be incorrectly
cached between the two custom tags. Does anyone else have similar
experiences, perhaps with non-Struts custom tags?
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
