If you don't care much for performance, I'd like to add that Castor has the ability to marshal/unmarsal without an XSD as well. You can use their own mapping facility. Here's some more info: http://www.castor.org/xml-framework.html#Run-Time-Descriptors
Kory -----Original Message----- From: obrand [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 2:11 PM To: [EMAIL PROTECTED] Subject: Re: XML to XSD I would recommend using Castor from Exolab to deal with XML and Schemas. JAXB is too complex since it tries to redefine what Schema already defines (constraints, type, ....). Using Castor, you will be able to generate the java framework starting from one file: your schema ! A tool creating Schema from XML is nearly impossible due to the semantic information which does not show in an XML document. For this reason using DTD is useless, and JAXB once again is too complex. I would recommend XML Spy which helps you creating a Schema from an existing XML, then you can tweak it to refine your rules. Once finished, you just take the schema, call sourceGen from the exolab distribution and.... Voila ! Just to add to the polemic, it seems that SUN's future on JAXB is unclear. I have heard from other SUN engineers that the project might be re-architected. Anyway SUN's direction for J2EE 1.4 is to move to Schemas, allowing standard checking from the parser and be able for some vendors to extend some configurations (I am sure that iPlanet is going to like it......). Olivier
