Documentation:Importing web service interface as model: Difference between revisions

Importing web service interface as model

Latest revision as of 05:55, 27 January 2025

This page was created by Lars.olofsson@mdriven.net on 2018-11-25. Last edited by Stephanie@mdriven.net on 2025-01-27.

It can be helpful to import a 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 them to XMI, which in turn can be imported by MDriven Designer.

Importing XSD with Sparx

Using Sparx, edit and clean up the imported model. Usually, you will want to remove all "elements," keeping on the classes.

When it is ready, export the model using XML with UML 2.4.1 and XMI 2.4.2.

Note! MDriven ONLY supports XMI 2.4.2

@@ Line 1: / Line 1: @@
+{{Edited|July|12|2025}}
 <message>Write the content here to display this box</message>
-It can be helpful to import a web service or REST interface definition as a model. Then you can use the classes like this [[Import xml and JSon with MDriven|Import XML and JSon with MDriven]].
+It can be helpful to import a web service or REST interface definition as a model. Then you can use the classes like this [[Documentation:Import xml and JSon with MDriven|Import XML and JSon with MDriven]].
 MDriven Designer can't import an XSD och WDSL directly.
@@ Line 11: / Line 12: @@
 When it is 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]]
 '''Note! MDriven ONLY supports XMI 2.4.2'''
+[[File:Sparx export as XMI.png|none|thumb|917x917px]]
 [[Category:Advanced]]
 [[Category:MDriven Designer]]