The main functionality of this tutorial application is to replace a default text by a user input. Within E2E UI, the SOAP service with its messages represents the data model. The data model itself consists of the <<SOAPPortType>> operations input and output parameters. For best practice reasons, we use document/literal "wrapped" style messages (c.f. WS-I profile for reasons). This means, that each SOAP operation has at maximum one input and output parameter. The names of the parameter types are derived from the operation name: the input parameter has the same name as the operation, the output parameter is named by using the operation name having 'Response' added at the end.
Due to the fact that the SOAP operation parameter classes are not only used for the SOAP operation but at the same time are also used for the mapping of the data to the user interface elements, these classes are wrapped up in a Messages repository under the Data root element of the Containment tree.
Figure: HelloWorld UI Message Data Model
As seen in the above figure, there are two classes, each with an attribute called myText of the BaseType String. The class changeHelloWorldText is the operations input parameter, the class changeHelloWorldTextResponse the output parameter.
Amend the default E2E SOAP Service and change it to a E2E SOAP Document operation implementing the above changeHelloWorldText and changeHelloWorldTextResponse classes as input and output parameters. Due to the nature of the implementation used for E2E UIs, SOAP operations must get the stereotype <<SOAPDocumentOperation>>. Finally, name the operation changeHelloWorldText.
Figure: HelloWorld UI Service
For detailed information on how to create E2E SOAP Services please refer to the E2E Education lessons.
Overview
Content Tools