Below is a snippet of a thread from the tomcat-user list describing my problem: > -----Original Message----- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > > David Rees wrote: > > > I also just tried this on Tomcat 3.2, same problem. > > > > Again, here's the problem: > > > > I have a form which posts to a jsp, which then instantiates a > bean with the > > data from the form, which then forwards the request to a > servlet which does > > a getAttribute to obtain then the bean data. It then forwards > on again to > > another jsp. > > > > The problem occurs during development: Updating the servlet causes a > > ClassCastException. Shutting down and restarting Tomcat makes the > > ClassCastException go away. > > > > This happens on Tomcat 3.1 and 3.2. It does not happen on the > Tomcat 4.0 m4 > > build. > > > > Should I post this issue to the -dev list? It seems like a > Tomcat bug to > > me. > > > > You can if you want ... but there are fundamental architectural > problems to the > way that class reloading was done in 3.1 and 3.2. It would be a > pretty major > change to fix it. > > Tomcat 4.0 uses a different strategy (pretty much based on what > Apache JServ) > did that seems to deal with class reloading in a much more robust > manner (and > with lower overhead). I've done a bit more experimenting with this problem and now I've got two cases which can produce the ClassCastException, one in a servlet, and also one in a jsp. If you like, I'll post the simple test cases for each, but from Craig's message he implies that this is a known bug in the Tomcat 3.x series. It would be nice to get this fixed, it would save me from stopping/restarting Tomcat after updating certain servlets/jsps. Thanks, Dave
