- Yes, if you store primitive types rather than application types this problem won't occur - This problem won't occur with remote marshalling of the class data, since object is sent in serialized form to remote nodes. This does point out another problem you are going to run into, however, which is harder to deal with than the one you've hit already ... to get sending your application classes to remote nodes to work, you need to set the class loader that the cache uses to demarshal objects read from the wire; this isn't too hard to do - use cache.registerClassLoader() - but you can't *change* the class loader for a running cache. So you basically need to either use primitive types or restart the cache for that node (not just clear it) when you redeploy your application. - Are you really planning to change the code on one node of the cluster while leaving an older version running on another node? Brave.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990459#3990459 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990459 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
