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.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
|
Title: ClassCastException from serialize, redploy, deserialize