OK, I've tried to update the Castor generated APIs using Castor 8.11. Heres the status: - I've updated the build file to make the regeneration work - I've updated the xsd files to make them compliant with the latest XMLSchema spec (they may still be optimised by factoring some attributes and element). After this step, I can rebuild without error the 3 APIs. Note however that I had to change some of the constraints in the markup to make it compliant with the new XMLSchema. When I try to build Jetspeed with this new API, I get a lot of errors because : - the package o.a.j.x.api.registrymarkup has not been updated because there are no xsd in the CVS to update it (it should have been completely replaced by jetspeedconfig) - the psml.xsd describes a markup that is not currently used and thus the newly generated API fails. All these problems arise from the partial merge with Kevin proposal 3 implementation when we fixed the CVS head in october. If some other people want to play with the xsd and Castor files, I've committed the updated xsd and build files but not the castor jars. If you want to test this, just grab the latest castor release, regen the source API and see the disaster. On wednesday, I'll try to rollback the psml markup to its pre-proposal 3, regenerate the PSML API and see if I can make it work. If there's no progress by wednesday, I'll give up and actively work at switching the persistence system. But for now, I'm too tired... -- Raphaël Luta - [EMAIL PROTECTED] Vivendi Universal Networks - Services Manager / Paris -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/[email protected]/> List Help?: [EMAIL PROTECTED]
