Importing web service interface as model
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
It can be very helpful to import | It can be very 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]] | ||
MDriven Designer can't import an XSD och WDSL directly. | MDriven Designer can't import an XSD och WDSL directly. | ||
| Line 7: | Line 7: | ||
[[File:Sparx XSD import.png|none|thumb|648x648px|Importing XSD with Sparx]] | [[File:Sparx XSD import.png|none|thumb|648x648px|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 | 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'''. | 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]] | [[File:Sparx export as XMI.png|none|thumb|972x972px]] | ||
Revision as of 06:38, 31 January 2023
It can be very 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 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 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
This page was edited more than 1 years ago on 01/11/2024. What links here