The problem is probably the same one we saw when binding and then
rebinding ejb home proxies into JNDI using java.rmi.MarshalledObjects.
The issue is that there was some caching being done at the vm layer based
on identity of the class loader. Try your testcase with the new 3.0.0 release
which changed how class loaders computed equality and hashCode
and if there is still a problem open a bug.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
----- Original Message -----
From: JD Brennan
To: JBoss Users (E-mail)
Sent: Friday, May 31, 2002 12:06 PM
Subject: [JBoss-user] ClassCastException from serialize, redploy, deserialize

I've narrowed down my ClassCastException to
deserializing an Object after redeploying.

I serialize an Object to BLOB in MySQL using
CMP.  Then redeploy and when I deserialize the
object I can't cast the Object to one of it's

Could this be some ClassLoader issue?  The
interface is loaded by a JBoss class loader
and the deserialized object is loaded by
another ClassLoader.

I think I've got a good handle on the problem,
but can't think of a good solution - aside from
not using hot deploy...

Tx for any thoughts!