Kewl.. nice to see this be of use. As far as I can remember, I think the torque4.0 namespace was just a "make it short" decision. The longer form's OK by me.
Out of curiosity, does this mean all schema.xml files will have to be modified with the xsd headers? Not a bad thing, just wondering if you had figured out how to support both ddt and xsd. FWIW, I briefly experimented with writing some code that would read the first few lines of the schema, then decide which parser to use. I was thinking of minimizing the disruption in using the new code. However, I don't think this is important now since so much is being changed in 4.0. > -----Original Message----- > From: Thomas Fischer [mailto:[email protected]] > Sent: Friday, September 10, 2010 1:49 AM > To: Apache Torque Developers List > Subject: database.dtd replaced by database.xsd in torque 4 > > > I added Greg's suggestion for a schema xsd to the torque 4.0 templates, > and > support in the generator to check xml sources against a schema. > A few things were changed as compared to Greg's initial proposal > - I changed the namespace from http://db.apache.org/torque4.0 to > http://db.apache.org/torque/4.0/templates/database. The reason was to > have > a similar namespace as the contol.xml's ( > http://db.apache.org/torque/4.0/generator/configuration). This is open to > discussion, please object if you do not like it. > - I added a non-strict version which does not check for allowed > characters, > so people can choose which schema they want. > - removed attribute heavyIndexing, value "null" for attribute idMethod > and > value 'none' of the onUpdate and onDelete attributes as described in > TORQUE-127, TORQUE-130 and TORQUE-131 in jira. > > Any reviews, comments, objections etc are welcome. > > Thomas > > P.S the schema is not yet available on the web site, but is resolved > internally by an entityResolver. I'd rather not publish the schema on the > web site in case we need to change anything. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] DukeCE Privacy Statement: Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
