Documentation:Rest Services In MDriven: Difference between revisions

Rest Services In MDriven

Latest revision as of 07:55, 17 June 2024

REST Services are services executed by connecting to a URL that defines operation and parameters and returns an answer – not seldom as JSON objects.

You must set the tagged value RestAllowed on the ViewModels you want to allow Rest access to.

Calling Existing REST Services

MDriven supports a couple of EAL operators to manage REST services. All operators reside on the selfVM variable which is available only in the ViewModel context.

selfVM.RestGet(targeturl,user,pwd,optionalnestingwithheaders)

Read: OCLOperators RestGet

selfVM.RestPost(targeturl,user,pwd,optionalnestingwithheadersAndUploadValues)

Read: OCLOperators RestPost

selfVM.RestDownload(targeturl,user,pwd,optionalnestingwithheaders)

Read: OCLOperators RestDownload

Note! optionalnestingwithheaders is the name of the blue ViewModel class in the example below (as an OCL String).

Example

The action GetExporttest retrieves data by converting another ViewModel to XML - it stores it in the variable vText.

The next action invokes RestPost to send that data to a URL address; it also says it should look at the nesting named 'Xml'. In this nesting, we have the STRINGCONTENT (see also OCLOperators RestPost) which gets its content from the vText variable. We also add the header Authorization with a bearer token to get access from the receiving service.

This page was edited 9 days ago on 06/17/2024. What links here

@@ Line 1: / Line 1: @@
-'''REST services''' are services that are executed by connecting to an URL that defines operation and parameters then it returns an answer – not seldom as JSon objects.
+<message>Write the content here to display this box</message>
+'''REST Services''' are services executed by connecting to a URL that defines operation and parameters and returns an answer – not seldom as JSON objects.
-====== Calling existing REST services ======
+You must set the tagged value '''RestAllowed''' on the ViewModels you want to allow Rest access to.
-MDriven supports a couple of EAL operators to manage REST services. All operators reside on the selfVM variable – available only in the ViewModel context.
+=== '''Calling Existing REST Services''' ===
+MDriven supports a couple of EAL operators to manage REST services. All operators reside on the [[selfVM]] variable which is available only in the ViewModel context.
   ''selfVM.RestGet(targeturl,user,pwd,optionalnestingwithheaders)''
+Read: [[OCLOperators RestGet]]
   ''selfVM.RestPost(targeturl,user,pwd,optionalnestingwithheadersAndUploadValues)''
+Read: [[OCLOperators RestPost]]
   ''selfVM.RestDownload(targeturl,user,pwd,optionalnestingwithheaders)''
-There is a also a new helper operator on selfVM:
+Read: [[OCLOperators RestDownload]]
- selfVM.JSonToObjects( «<Type>» ,  JSonDataInStringFormat)
-The selfVM.JSonToObjects creates objects of class Type and matches attributes and association from the json data – and it can create object trees (unclosed graphs) by following names on associations. These few additions enables us to consume Rest services that others expose.
-And when it comes to '''exposing ourselves to others''' – Turnkey has two new MVC verbs:
+'''Note!''' ''optionalnestingwithheaders'' is the '''name''' of the blue ViewModel class in the example below (as an OCL String).
- MDrivenRest/Get?command=vmname&id=rootobjref
- MDrivenRest/Post?command=vmname&id=rootobjref
+==== Example ====
-What they do is that they look for ViewModel named as the command-parameter, if one is found the [http://wiki.mdriven.net/index.php/Part_9_MDriven_Turnkey,_cloud_tools_and_access_groups accessgroups] are checked to see if access is allowed. If it is, additional parameters sent in the url are matched against ViewModel variables – and given corresponding values. Then any actions present in the root level of the ViewModel are executed. And then the Get verb packs the viewmodel content as json in the response.
+[[File:2018-05-29 10h31 45.png|none|thumb|689x689px]]
+The action '''GetExporttest''' retrieves data by converting another ViewModel to XML - it stores it in the variable <code>vText</code>.
-The Post verb looks in the request values after names that match the ViewModel root – if match is found the corresponding value is applied. Then changes – if any – are committed to db. The last thing for post is that it packs the complete ViewModel as json in the response. If there is an error – a string “error: <message>”  is returned.
+The next action invokes RestPost to send that data to a URL address; it also says it should look at the nesting named 'Xml'. In this nesting, we have the STRINGCONTENT (see also [[OCLOperators RestPost]]) which gets its content from the vText variable. We also add the header Authorization with a bearer token to get access from the receiving service.
-You must set RestAllowed on ViewModels you want to allow Rest access to.
+'''See also''': [[Documentation:Exposing Ourselves as a REST Service|Exposing Ourselves as a REST Service]]
+[[Category:Rest]]
+[[Category:Advanced]]
+{{Edited|July|12|2024}}