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 PROTECTED] > Subject: DynaActionForm caching issues? > > > Hello, > > This message is in response to Geeta Ramani's post on March 4 > entitled "DynaActionForm IllegalArgumentException." > > In short, I have a DynaActionForm defined in > struts-config.xml. It's been around for a while, but I find > that each time I make a change to it (for instance, adding a > new property), I run into the same IllegalArgumentException > (at the same file and line number) that Geeta described. I > can work around the issue by undeploying my application, > stopping my application server entirely (JBoss 3.2.3 on > Linux), and then restarting and redeploying. > > Is it possible that there are some caching issues, where > Struts saves its configured DynaActionForms somewhere in the > application server's memory and then doesn't realize it has > to refresh that information when struts-config.xml changes? > > Interestingly, the Struts and all Commons jar files are kept > inside my application's war file, and are not stored in > JBoss's shared library directory. I would think this would > ensure a complete Struts reload upon each deployment, but it > seems that is not the case. > > I'm using Struts 1.1 final and the Commons jars included in > that distribution. I have JBoss 3.2.3 running on Linux with > Sun's j2sdk 1.4.2_04. > > Thanks in advance for any suggestions, > -- > David Norris > [EMAIL PROTECTED] >
