#14 SOAP ignores the result's root value

[Matthias Dieter Wallnöfer]

Claudio's comment:

In general, the guidelines we decided to follow when converting a Jolie interface in a WSDL one,
was to always map a message with a type whose native node is void.

The choice was driven by the fact that it is necessary to adhere as much as possible to WSDL specs
where Messages are different from types.
In this scenario, the root element must always be empty in order to avoid TypeMismatch.

Thus interfaces like the following ones should be deprecated

interface MyInterface {
RequestResponse:
test( string )( int )
}

an interface like this one is not a good candidate to be converted into a Web Service.
This is why, in general I use these interfaces only when I am sure they won't never become
a Web Service, otherwise I always introduce the message type
(that, it is always the best practice to follow.... mmmmm we miss a lot of documentation about this)

Fabrizio's comment:

Yes, only wsdl has that limitation, while soap does not.

I suggest introducing a parameter for soap and our wsdl tools that tells Jolie to which subnode our root native values should be mapped to, along with a sane default.

For the docs about these behaviours, how about the Jolie docs website?