Hi Jim,
Did you consider using XSL transformation?
This may be much more flexible
Claude
> -----Original Message-----
> From: James Carter [mailto:[EMAIL PROTECTED]]
> Sent: 12 November 2002 19:44
> To: [EMAIL PROTECTED]
> Subject: [castor-dev] Castor APIs for XML*Schema data structure?
>
>
>
> A weird question perhaps, but here goes...
>
> I'm considering using Castor as the "backbone" of an "XML generation"
> process which is Schema driven. Specifically, I want to use a
> Castor-based program to read in a flat file of data (record structure
> TBD) and generate an XML output file. Certainly, the existing
> SourceGenerator module does exactly what I need for the "front end" of
> this process, that is, creating the XML file. But the other side
> involves 2 things: creating a Java "driver" program that parses the
> flat file and calls all the generated setter() methods (and then
> marshalls to XML) -and- defining the record structure of the flat file
> itself. Now, in this case, the flat file is coming from a legacy
> COBOL app, so in essence, that last part amount to creating a COBOL
> "record copy" (for those not familiar with COBOL, essentially a data
> structure definition in COBOL-ese).
>
> So, first off - is there anything in Castor to do this kind of thing?
> (I've not seen anything yet but might have missed it)
>
> Secondly, does this make sense, or is there perhaps a better way of
> doing this?
>
> And, if this does make sense, what APIs are there in Castor to access
> regarding the "metadata" in the XSD file? Seems like one ought to be
> able create a "driver program generator" pretty simply given the
> contents of the XSD structure. (And then create the language specific
> data structure code on the other end).
>
> Thanks for any ideas/advice,
> Jim Carter
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
__________________________________________________________________________
· This email and any files transmitted with it are CONFIDENTIAL and intended
solely for the use of the individual or entity to which they are addressed.
· Any unauthorized copying, disclosure, or distribution of the material within
this email is strictly forbidden.
· Any views or opinions presented within this e-mail are solely those of the
author and do not necessarily represent those of Odyssey Asset Management
Systems SA unless otherwise specifically stated.
· An electronic message is not binding on its sender. Any message referring to
a binding engagement must be confirmed in writing and duly signed.
· If you have received this email in error, please notify the sender immediately
and delete the original.
