I am not good at English. Please associate though it might be incomprehensible. The problem occurs when PushTag is used with Tomcat4.1.x. (There is no problem in Tomcat4.0.6. ) The value of the instance variable "Stack" of PushTag is ValueStack instance when the Push tag is used first. The Push tag doesn't do correct operation since the second times. (Refer to stack of the first time for PushTag. ) The cause is in the Puring mechanism of Tomcat4.1.x. The instance of the custom tag is pooled in Tomcat4.1.x. However, the release() method is not called according to correct timing. The release() method is called in Tomcat4.1.x only at the shutdown of Tomcat. Therefore, the first stack remains through all eternity in stack field of PushTag. The problem will not occur by either of the following methods. -Null is put in stack at the head of doStartTag. -The stack field is removed. The patch corresponding to the problem when the Push tag was used with Tomcat4.1.x was put on JIRA. Is it good in this? http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-354 Moreover, is it correct in this mailing list that the post for so? I am hesitant because I am not good at English.;-) Toshitaka Agata. __________________________________________________ Do You Yahoo!? Yahoo! BB is Broadband by Yahoo! http://bb.yahoo.co.jp/ ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
