Hi again My query is really on whether the interface itself is too restrictive. Yes I know I can cast to another type, we are using this for JDO and XML at my site, but coding to an interface is always preferable to coding to an implementation. Glen
-----Original Message----- From: Diez Roggisch [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 26, 2002 9:01 AM To: [EMAIL PROTECTED] Subject: Re: [castor-dev] org.exolab.castor.mapping.ClassDescriptor interface methods Hi, just this night I fiddled around with that stuff - Arnaud is perfectly right. So if you want to access those special fields (leaving the secure pathways...) you should be able to cast to JDOClassDescriptor. Diez [EMAIL PROTECTED] schrieb am 26.03.02: > 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 ________________________________________________________________ Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13 ----------------------------------------------------------- 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
