>as I understand, please correct me, the XSLT transformation is for >converting my non-database aware XML schema in an database aware schema >(Torque-schema.xml). So all the works lies on writting the >right XSL. The >rest is "mechanical work".
Correct. [..] > >Is not there any way *automathically* convert the XSD or DTD >in the DDL or database without caring about the mappings, maybe because the >tool assumes already some mapping constraints. I wonder why it is not already done, >�maybe because is not possible?. It is unlikely there would be a "generic" soultion out there. XML Schema's are so flexible, you can define virtually any hierarchy of data with them; it is very unlikely that there will be a ready-to-use tool that will convert any XSDSchema into DDL. However, you could write your own XSLT to convert YOUR schemas, because you can make create your own constraints in the mapping. >In the other hand, as an evidence that it is possible, WSAD >from IBM, is >able to create the database scripts from an XSD. How do they >do it? I imagine they do it by imposing severe constraints on the XSD - or, rather, making great assumptions about how you want to map the elements to tables... >I would be using it but my WSAD just crashed the VM in all my attempts. > >NOTE: My XSDs are actually a set of XSDs, where each one >imports other XSDs, >so is quite complex structure. In that case, it *might* be necessary to write a program to read-and-create-a-torque-schema from your XSD schema - I've got a feeling that XSLT will "see" the XSD as one file, in which case XSLT will be OK, but I could be wrong. > >Opinions welcome please, since I am stuck from a while ago >with this matter, > >Adolfo. > > > > >> -----Mensaje original----- >> De: Charles Anthony [SMTP:[EMAIL PROTECTED] >> Enviado el: mi�rcoles 20 de agosto de 2003 13:00 >> Para: 'OJB Users List' >> Asunto: RE: creating DB from an XSD or XML >> >> Hi, >> >> An XSDSchema is already in XML. >> >> Torque allows you to define an database schema in XML; OJB >uses Torque to >> generate it's database tables. >> >> So, it follows that (Depending upon then complexity of the >XSD schema) you >> should be able to write a XSLT transformation to create the >Torque schema. >> It woulbe something like >> >> Schema -> XSLT (Stylesheet) -> Torque-schema.xml -> Torque -> DDL >> >> For more info on the Torque see >http://db.apache.org/torque/generator/ >> (Note torque is also a persistency layer. OJB only uses the generator >> portion of Torque) >> >> Cheers, >> >> Charles >> >> >-----Original Message----- >> >From: "Rodr�guez Migu�lez, Adolfo" [mailto:[EMAIL PROTECTED] >> >Sent: 20 August 2003 11:04 >> >To: [EMAIL PROTECTED] >> >Subject: creating DB from an XSD or XML >> > >> > >> >From time ago I am loooking fo a way to do the following. >> > >> >Assuming that I have some kind of DTD or XSD for XMLs. I >would like to >> >create, a database, or DDL, to reproduce the DTD or XSD >> >estructure in my >> >database schema. Could be this done with an automathic >> >procedure. In other >> >words, is currently possible to create a database schema >> >reproducing the >> >structure of an XSD or DTD? Such a DTD or XSD would not be >> >database aware at >> >all. >> > >> >I am developing a web application focused for a kind of >business which >> >already has very well defined XML schemas and I would like to >> >create the >> >database following the same estructure, if possible, as an >authomatic >> >procedure, maybe with OJB, or OJB plus something.... It would >> >easy me to >> >receive XMLs from an external web service an automathically >> >store them in >> >DB, or the opposite make a valid XML conforming the DTD or >XSD from my >> >database assuming that both have same strutucture. >> > >> >TIA, >> > >> >Adolfo >> > >> >>--------------------------------------------------------------------- >> >To unsubscribe, e-mail: [EMAIL PROTECTED] >> >For additional commands, e-mail: [EMAIL PROTECTED] >> > >> >> >> This email and any attachments are strictly confidential and >are intended >> solely for the addressee. If you are not the intended >recipient you must >> not disclose, forward, copy or take any action in reliance >on this message >> or its attachments. If you have received this email in error >please notify >> the sender as soon as possible and delete it from your >computer systems. >> Any views or opinions presented are solely those of the >author and do not >> necessarily reflect those of HPD Software Limited or its affiliates. >> >> At present the integrity of email across the internet cannot be >> guaranteed >> and messages sent via this medium are potentially at risk. >All liability >> is excluded to the extent permitted by law for any claims >arising as a re- >> sult of the use of this medium to transmit information by or to >> HPD Software Limited or its affiliates. >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > This email and any attachments are strictly confidential and are intended solely for the addressee. If you are not the intended recipient you must not disclose, forward, copy or take any action in reliance on this message or its attachments. If you have received this email in error please notify the sender as soon as possible and delete it from your computer systems. Any views or opinions presented are solely those of the author and do not necessarily reflect those of HPD Software Limited or its affiliates. At present the integrity of email across the internet cannot be guaranteed and messages sent via this medium are potentially at risk. All liability is excluded to the extent permitted by law for any claims arising as a re- sult of the use of this medium to transmit information by or to HPD Software Limited or its affiliates. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
