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.
-Dave
> Replying to my own message:
>
> I just downloaded and tried it under Tomcat 3.1 which showed the same
> problem. So at least this isn't a new bug. :-)
>
> I also tried Tomcat 4.0-m4 which works perfectly in for my test case.
>
> > I have a simple test case (which this was generated under) which I can
> > post to the list if anyone is interested.
> >
> > Is this a known bug? I haven't tried the same thing under Tomcat 3.1
> > yet, as I was under the impression that Tomcat 3.2beta was superior to
> > Tomcat 3.1.
>
