Firstly, thanks for all the prompt answers I've been getting on this
newsgroup.
I have been trying to understand how the ClassDescriptor is used in
Castor XML and JDO. Its use in Castor XML is pretty straight forward.
In JDO, I'm a bit confused.
I hunted around the source and I found a class
org.exolabs.castor.mapping.loader.MappingLoader which is extended by
*.jdo.engine.JDOMappingLoader. JDOMappingLoader seems to create class
descriptors with help from MappingLoader. So it seems that JDO does use
a class descriptor.
However, JDOMappingLoader seems to call MappingLoader to load a class
descriptor (loadClassDescriptor), but this function always returns null
(the class load of the descriptor name is commented out), so the way I
read the code is that MappingLoader.createDescriptor is *always* called
to create the ClassDescriptor using the ClassMapping and reflection.
The upshot is that my custom ClassDescriptor will be ignored. Is this
correct?
What are the implications of modifying the JDOMappingLoader to check for
a custom ClassDescriptor (instead of always creating it) and then
wrapping it with a JDOClassDescriptor.
thanks again for any help.
--
__o
_-\<,_ Brian
(_)/ (_) [EMAIL PROTECTED] x503
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
