From: Scott M S. <Sco...@jb...> - 2002-05-31 19:30:59
|
ClassCastException from serialize, redploy, deserializeThe 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. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message -----=20 From: JD Brennan=20 To: JBoss Users (E-mail)=20 Sent: Friday, May 31, 2002 12:06 PM Subject: [JBoss-user] ClassCastException from serialize, redploy, = deserialize I've narrowed down my ClassCastException to=20 deserializing an Object after redeploying.=20 I serialize an Object to BLOB in MySQL using=20 CMP. Then redeploy and when I deserialize the=20 object I can't cast the Object to one of it's=20 interfaces.=20 Could this be some ClassLoader issue? The=20 interface is loaded by a JBoss class loader=20 and the deserialized object is loaded by=20 another ClassLoader.=20 I think I've got a good handle on the problem,=20 but can't think of a good solution - aside from=20 not using hot deploy...=20 Tx for any thoughts!=20 JD=20 |