Mapped JSON Convention
1. An element with no characters or child elements is represented by:
{ "element" : "" }
2. No namespaces declarations are ever written.
Note: | The Badgerfish convention does allow namespaces. If a client sends a request that contains XML namespaces, you need to bridge to the Badgerfish convention. To do this, in the virtual service's Set Headers action, set the parameter Set Headers to Header and specify the Name as Content-Type and the Value as application/json/badgerfish. Doing this will override the existing Content-Type that will be sent to the native provider. |
3. An element with multiple child elements of the same name is represented by an array.
Simple case:
<price>10.00</price>
{ "acme.price" : { "10.00" }
Array case:
<root><child>test</child><child>test</child></root>
{ "root" : { "child" : [ "test", "test" ] } }
4. The XML attributes for a message are prefixed with @ when a message is serialized (same as Badgerfish).
