Proxied classes need to be identified and receive special processing

Proxy classes (usually via CGLIB proxies) need to be identified as proxies and treated in such a way that the proxy enhancements do not interfere with marshalling/unmarshalling. Two different issues have arisen with proxies:

http://www.mail-archive.com/user@castor.codehaus.org/msg02345.html
http://www.mail-archive.com/user@castor.codehaus.org/msg02489.html

First and foremost, Castor needs to identify when an object/class is a proxy instead of the real thing. According to the CGLIB mailing list:

http://sourceforge.net/mailarchive/message.php?msg_id=9827333

this can be done by finding if a class is an implementation of the net.sf.cglib.proxy.Factory interface (this may need to be user adjustable for other proxying libraries – if there are any).

Once the proxy has been identified, this issue may need to be split into three sub-issues:

1. Looking up ClassDescriptors based on a proxy class (get the proxy's superclass to look up?)
2. Introspecting proxy classes (don't introspect the proxy, introspect the original?)
3. Mapping proxy classes (not sure about this one... maybe the previous two will solve this one)