For the precedence issue, we could identify if a class followed the 'JavaBean' standard when we initially construct a CachedType for it. Since the CachedType objects are cached, there would only be a slight performance impact the first time an unrecognized class is attached. So, the precedence rules would be: first check if object is advisable, then check if it is a collection, then check if it follows standard javabean symantics, and finally use the serializable handler. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094291#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...