Patrick Moore wrote: > Hi Keith --- > > Is this information going to be able to be read from the schema file? If the > answer is no then I will work on a patch that lets the information to be in > the schema file. The reason is that I would like to have all the information > in the schema file so that the data definition is self contained. If I > decide to move to a different source generator this would enable a > conversion to that new source generator's appinfo format using XSLT. If I > have a series of .properties files I get no such flexiblity. > > If I came up with such a patch would it be rejected out of hand? I can see advantages to both approaches, the encapsulation favoured by Patrick certainly has some appeal (and would suit my immediate requiremnets well) but there is also the argument that you may want to bind the same schema to mutiple languages etc, so having the info external to the schema may be better modularisation. If Patrick got the go-ahead I'd certainly be interested in helping/using the result. The two approaches don't need to be exclusive neccessarily (they could use the same underlying APIs but take info from different sources) My 2c... > > > >-----Original Message----- > >From: Keith Visco [mailto:[EMAIL PROTECTED]] > >Sent: Monday, February 18, 2002 2:37 PM > >To: [EMAIL PROTECTED] > >Subject: Re: [castor-dev] defining superclass, and interfaces in xml > >schema file. > > > > > > > >Hi Patrick, > > > >Please see: http://bugzilla.exolab.org/show_bug.cgi?id=882 > > > >Arnaud has been working on the binding file for Castor which will give > >you the features you need...such as specifying class names, specifying > >interfaces and a superclass, etc. > > > >A single super class can already be specified using > >castorbuilder.properties. This super class can contain the "implements > >interface(s)" that you need. However this superclass is used for all > >generated classes (except descriptors). > > > >A work around to allow finer grained control is to split your schema > >into multiple schema for the purpose of source generation and use > >multiple castorbuilder.properties files for specifying different super > >classes. This is only for the purpose of source generation and > >your main > >schema would remain in-tact. It's just a work-around until the binding > >file has been commited into the CVS. > > > >Thanks, > > > >--Keith > > > > ----------------------------------------------------------- > 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
