The following steps guide you to generate XML output from Java input:
1. Select the Java Input and Soap Message Output option.
2. Click Edit. The Mapping Editor dialog box appears. Modify the type mapping definition, only if any of the preceding assumptions is not true.
3. Provide the required information and Click OK.
Use the Mapping Editor to enter values (or edit the already present values) for the XML-type, fully qualified class name for the Java object that represents the data type. Sometimes a complex object type may contain another complex object as one of its fields. In this case, you may have to manually define the XML mapping for the nested type(s). If needed, you can also define your custom serializer and deserializer factory that are used to convert the Java object to XML form and back.
Generally, when using a Web Service, the provider can give you enough information about what each of these fields must contain. Additional information about writing custom serialization and deserialization factories can be obtained from Apache Axis (http://ws.apache.org/axis/).
Note: For more information about complex data types, see the BP Server examples topic in Progress OpenEdge business Process Server: Managed Adapters Guideor use the example provided under OEBPS_HOME\BP Server\examples\WebserviceComplexType.zip.
Finally, note that Web Services containing complex type inputs cannot be tested through the Web Services Adapter Configurator. In this case, make sure to properly test your configuration by running the process from Business Process Portal.
Note: The classes for the complex types are not reloadable. If there is any change in the binary, stop the application Server and restart them.
