Debugging class loader problems is not fun. Keep in mind that if the same class is loaded by two different class loaders, the two instances of the class are not considered the same by Java even though they are literally the same class. This is easier to do than it may seem on the surface.
So in this case if the object was created through one class loader and the cast occurs in the context of a different class loader, you will get the cast exception. Mike On 5/2/05, Johan Maasing <[EMAIL PROTECTED]> wrote: > I do not have any good ideas but I recognize the situation (non-tapestry > app). In our case the web application was unloaded, replaced with a new > version and then re-deployed. Since weblogic was running the whole time > the JVM was never interrupted. This caused problems with our property > classes. They were static singletons so they were not unloaded when the > web application was unloaded. However, the new version of the > application changed the property classes. This meant that that the > classloader considered the old live instances not the same class as the > new versions. So, I guess that a question would be if your problems > occurs on a newly started server or only when you have restarted an > application? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
