In my experience, it's not that the bean config is cached, it's that the form
itself is cached. If your bean is not in request scope, it gets reused.
Tomcat can keep a session alive between application and server restarts and
so your form can survive those. What I've done when I modify my dyna
Message-
From: Hubert Rabago
To: Struts Users Mailing List
Sent: 3/23/04 7:28 AM
Subject: RE: DynaActionForm caching issues?
In my experience, it's not that the bean config is cached, it's that the
form itself is cached. If your bean is not in request scope, it gets
reused. Tomcat can keep
Note: JBoss 3.2.3 includes an integrated Tomcat 4.1.29, which is of course
more likely to be relevant to this problem than JBoss itself...
-Original Message-
From: Norris, David A. ERDC-CERL-IL Contractor
[mailto:[EMAIL PROTECTED]
Sent: Monday, March 22, 2004 4:45 PM
To: [EMAIL
3 matches
Mail list logo