jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Zänglein" <m.zaengl...@gmx.de>
Subject Re: Changes in Taglib handling from Tomcat 4.0.5 to 4.1.24 ?
Date Sun, 27 Jun 2004 14:05:17 GMT
No, I m afraid.

I used several browsers with caching disabled and the result always remained the same.

besides, the error also occurs when visiting a completely different link within the application
and afterwards returning to the list page.



-----Ursprüngliche Nachricht-----
Von: Michael McGrady <mike@michaelmcgrady.com>
An: Tag Libraries Developers List <taglibs-dev@jakarta.apache.org>; taglibs-dev@jakarta.apache.org
Datum: Sonntag, 27. Juni 2004 15:53
Betreff: Re: Changes in Taglib handling from Tomcat 4.0.5 to 4.1.24 ?

Sounds to me like caching on the client side.

At 06:19 AM 6/27/2004, Markus Zänglein wrote:
>I developed some own taglibs for an web application running on Tomcat 
>4.0.5, obeying the spec
>Now I've upgraded to Tomcat 4.1.24 and I recognized some problems with 
>certain tags.
>It seems, that Tomcat caches some data from one request to another.
>My so called "listItem-tag", which is to iterate a collection and print 
>out some properties of the list elements, does show list items that have 
>been deleted during the request before.
>so one can think, that the deletion has not worked correctly. Instead, 
>looking into the database makes clear, that the entry has been deleted 
>After logging off and on again, the list is displayed correctly by Tomcat.
>Anyone an idea, why this may happen ?

To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org

View raw message