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

Importing web service interface as model

Latest revision as of 05:10, 28 August 2024

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

This page was edited 22 days ago on 08/28/2024. What links here

Revision as of 07:27, 26 June 2023 (view source) Stephanie Namugambe (talk \| contribs) No edit summary Tag: Visual edit ← Older edit		Latest revision as of 05:10, 28 August 2024 (view source) Stephanie Namugambe (talk \| contribs) m ((username removed) (log details removed))
(5 intermediate revisions by 2 users not shown)
Line 1:		Line 1:
			<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 [[Import xml and JSon with MDriven\|Import XML and JSon with MDriven]].