Importing web service interface as model
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
Using Sparx, edit and clean up the imported model. Usually you will want to remove all "elements", keeping on the classes | Using Sparx, edit and clean up the imported model. Usually you will want to remove all "elements", keeping on the classes | ||
When ready, export the model using XML UML 2.4.1 and XMI 2.4.2. | When ready, export the model using XML with '''UML 2.4.1''' and '''XMI 2.4.2'''. | ||
[[File:Sparx export as XMI.png|none|thumb|972x972px]] | [[File:Sparx export as XMI.png|none|thumb|972x972px]] | ||
'''Note! MDriven ONLY supports XMI 2.4.2''' | '''Note! MDriven ONLY supports XMI 2.4.2''' | ||
Revision as of 16:25, 25 November 2018
It can be very helpful to import an web service or REST interface definition as a model. Then you can use the classes like this Import xml and JSon with MDriven
MDriven Designer can't import an XSD och WDSL directly.
Sparx on the other hand can import schemas and export to XMI, which in turn can be imported by MDriven Designer.
Using Sparx, edit and clean up the imported model. Usually you will want to remove all "elements", keeping on the classes
When ready, export the model using XML with UML 2.4.1 and XMI 2.4.2.
Note! MDriven ONLY supports XMI 2.4.2
This page was edited more than 1 years ago on 01/11/2024. What links here