Versions Compared

Old Version 8

changes.mady.by.user Tijmen Daatselaar

Saved on

compared with

New Version Current

changes.mady.by.user Tijmen Daatselaar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info
iconfalse
titleWhat is it for?
Excerpt
The Domain schema editor can be used to define the structure of REST requests and responses, or to add a mapping from your application domain.

The domain schema is a contract of communication. The purpose of the domain schema is to define what items are needed in a message and to specify its elements. For example the representation of a person. In this case the persons first name (1), always followed by his last name and his job(s). The right column represents the application domain, where the left column represents the domain schema of the message.

...

Note

You can make translations between message and your application domain. For example, it is possible to store a single-valued attribute in the message in a multi-valued attribute in your application domain. You have to be aware that you can only make a translation into a more general data type. For example the other way is not possible. When sending a message, it is not possible to place a multivalued attribute of your application domain in a single valued attribute of the domain schema.

Hide root element

Image RemovedImage Added

To define an unnamed array the 'Hide root element' checkbox corresponding to the domain schema root element must be ticked.

Example of a JSON message that consists of an unnamed array:

Code Block
[
	{ 
		"JohnId",: 23 }1,
	{	"Name": "RickBob", 30 }
		"Age": 35,
		{"Gender": "Paul", 27 male"
	}
]

When making use of unnamed arrays, only one child (relation or attribute) can follow the root element.

...

For more information on how to set the infinite-loop-limit for Runtime, check the properties documentation page.