Dub,
Your ClassCast exceptions indicate that you have a class that
is loaded by your webapp's classloader (and therefore changes
on each redeploy) but that is set statically on some classes
that are in the system classpath (which doesn't change with
each redeploy).
I recently found a bug in the version of Jasper (Tomcat's JSP engine)
that is also used by Jetty6. I've fixed it for Jetty and told
the Tomcat team about it. This may apply to you if you
are using JSPs and are using JDK1.5, so you may want to give
a recent SNAPSHOT of the plugin a whirl. Instructions on
that can be found from http://jetty.mortbay.org/jetty6/index.html
cheers
Jan
gdub wrote:
Stephen Duncan wrote:
Also look at the second question in this FAQ:
http://tomcat.apache.org/faq/deployment.html
It explains why reloading an app causes this problem to show up more
quickly.
The description sounds like it would apply to any container that uses
multiple classloaders, not just Tomcat, so it's likely true for Jetty
as well.
That would explain it. I wonder why the
difficulty with releasing unreferenced
class loaders.
-dub
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
