O2DBIWiki/WorkingXMI: Difference between revisions
imported>JomunaChoudhuri No edit summary |
m (4 revisions) |
||
(One intermediate revision by one other user not shown) | |||
Line 28: | Line 28: | ||
<!-- ##[[MailTo(software AT cebitec DOT uni DASH bielefeld DOT de)]] --> | <!-- ##[[MailTo(software AT cebitec DOT uni DASH bielefeld DOT de)]] --> | ||
<!-- ##For bug reports, please use our bug reporting system [http://bugs. | <!-- ##For bug reports, please use our bug reporting system [http://bugs.cebitec.uni-bielefeld.de BugZilla]. --> | ||
Author: [http://www.cebitec.uni-bielefeld.de/~blinke] | Author: [http://www.cebitec.uni-bielefeld.de/~blinke] |
Latest revision as of 07:13, 26 October 2011
O2DBI - Working with O2DBI - Converting XMI files
-> Back to Overview page <-
Building a class scheme from scratch using the O2DBI Designer may be suitable for small class schemes. Large and distributed projects often use UML based design software, e.g. the freely available ArgoUML or the commercial Poseidon or Rational Rose. These application are capable of reading and writing "XMI" files (XML metadata exchange).
XMI files contain a definition of classes, their attributes, relationships, associations etc. They may be used to define a class scheme for O2DBI:
Conversion
The XML format used by O2DBI differs from the format definition of XMI. The O2DBI tarballs provides an XSLT based conversion script.
Example:
xsltproc /path/to/O2DBI/share/xml/xmi_to_o2dbi.xslt your_classes.xmi > your_classes.xml
Common problems with XMI content
XMI allows various ways to express certain structures. Depending on the XMI generating application the conversion may or may not work. The XMI script was written to support the XMI files generated by ArgoUML. You should check the classes in the Designer after conversion. Inheritance and attributes should be ok in most cases, but associations may have wrong names or no names at all.
-> Back to Overview page <-
Author: [1]