Hi Glen, I can't give a precise reply but I can tell you that the ClassDescriptor is shared between the xml side and the jdo side so it contains all fields that are relevant on both sides.
Arnaud > -----Original Message----- > From: Glen Edwards [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 26, 2002 2:33 PM > To: [EMAIL PROTECTED] > Subject: [castor-dev] org.exolab.castor.mapping.ClassDescriptor interface > methods > > Hi > I was wondering if there were reasons that a couple of methods were not > available in the ClassDescriptor interface: depends and identities. > Currently there is no way to know if an object is a dependent object > unless > I use the implementation :(. There may be a good reason for this, so I > would > be curious to know. Identity is available, but identities are not. This > means that if I have a composite > key I can only get the first part of the composite in the current > implementation. Another option here would be for identity to return the > String as contained in the mapping file and I parse it. Again I am > currently > having to use the implementation here :( As both of these are > defined in the xml I assume (rightly or wrongly) that exposing these would > not cause issues. > > Glen Edwards > Elm Square Interactive/Exit41 > Three Dundee Park > Andover, MA 01810 > 978-933-7464 > [EMAIL PROTECTED] > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
