JBoss development, A new message was posted in the thread "Problems with proxy classes and a proposed resolution": http://community.jboss.org/message/532341#532341 Author : Andrew Dinn Profile : http://community.jboss.org/people/adinn Message: -------------------------------------------------------------- Thanks for the feedback, David.     That's precisely what my prototype implementation does (your comments in JASSIST-42 were all the recipe I needed). It seemed to work ok so once I fixed writeClassDescriptor to return a class with the correct name. This allowed the writer and reader to use normal object serialization to write/read the proxy instance itself.       Well, yes that's maybe so but I would not like to have to write and maintain code to do that. Your subclassed OOS/OIS solution achieves the same result with just a few calls to methods of OOS/OIS. That''s a big plus for your solution. My reasons for retaining the writeReplace version were i) retaining compatibility and ii) providing an option for code which has to use an OOS/OIS created by some other package rather than create its own subclass of OOS.This discussion is a way of polling to see how important these criteria are.   regards,     Andrew Dinn -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/532341#532341