You should define a subset of schema I think. The smallest one that is usefull to your users. If it contains only structures supported by castor, then why not. But if you then want to generate code for it the subset gets a little smaller.
btw, it looks like your doing something people would very much like to see contributed to castor. > -----Original Message----- > From: Greg McCreath [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 07, 2002 4:02 PM > To: [EMAIL PROTECTED] > Subject: [castor-dev] Load of Schema into Schema Model > > > > Hi all, > > I have a requirement to build schemas behind tree/message structures > that the user is inputting. Effectively I need to create a schema to > validate a structure, but the user doesn't really know they > are building > a schema. > > Two Castor questions: > > Is it possible to load a schema into a Castor in-memory 'Schema model' > so we may manipulate it with our UIs? > > Is it possible to get a in-memory schema model .... or preferable any > object model and render an on-disk schema from it? > > Many thanks > > Greg. > > ----------------------------------------------------------- > 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
