Updating from 2.2.0 to 2.5.0: Migrationpath and Compatibility issues
Oliver Meyer <[email protected]> Thu, 21 Jun 2012 11:08:23 +0200
| Newsgroups | gmane.text.xml.xmlbeans.user |
|---|---|
| Message-ID | <[email protected]> |
Hi, in a project in which we are using xmlbeans 2.2.0 and used it to generate classes for multiple different schema files, we now need to update the xmlbeans lib (we just created a schema, for which 2.2.0 can no longer generate correct classes). Is there a document describing (in-)compatibilities between these versions and what to do to update? We are using xmlbeans mainly to read in xml files. Rarely we create files with it. I like to now specifically: 1. Do I have to regenerate all schema specific libs from the .xsd files? 2. Are there known incompatibilities in behaviour? 3. Are xmlbeans 2.2.0 and 2.5.0 declared to be compatible? What kind of compatibility is meant here? I did not find any information concerning this migration use case on the apache page. If some one could point me to it, I would be more than happy to read. The only thing I could find, was the pointer to the common error of not adding the qname library to the class path. But, I was looking for a positive list of what to do, so that an update will work in the first place. I guess (but I like that to be confirmed) that update from 2.x to 2.x+y should work without regenerating, without compile time issues, and (if I do not depend on a buggy behaviour in 2.x) without changes in the application code, unless I like to use a new feature. Any pointers? Cheers, Oliver -- [email protected] +49 (0)2408 9492 - 793 DSA - Daten- und Systemtechnik GmbH PascalstraÃe 28, 52076 Aachen, Germany http://www.dsa.de Sitz und Registergericht/Domicile and Court of Registry: Aachen HRB-Nr./Commercial Register No.: 11960 GeschÀftsfÃŒhrung/Board of Management: Dr. Eckhard Schulz, Dr. Volker Gehring, Dr. Ansgar Schleicher