Has anybody ever thought of persisting DynaBeans (from common-beanutils)
using Castor?
Obviously something would need to be known about these classes ahead of time
in order to have a mapping for them but this may still be interesting.
the obvious points of impact seem to me to be:
a) castor would need to look up mappings based on getDynaClass().getName()
instead of getClass().getName().
b) Access to bean properties would need to verified as compatible everywhere
Anyone find this interesting or is it a _really_ bad idea?
Tim
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
