Input / output assumptions and design
Assuming that
- A
ValuesInput[] document is input that is the same as Values[] output. - The
columnValue document in the Document ValuesInput[] document has a string variable called additionalString (which would be pointless if there is no variable inside / under the document)
So, in general, it would be like this:

Of course, you can generate the code after designing the input / output by right-clicking with the mouse and generate the code β To implement this service.

But instead of using the generated code, I'm trying to give an example with IDataMap, which you can find in webMethods Javadoc com.softwareag.util.IDataMap . Which is very convenient to use.
IDataMap
IDataMap combines the functionality of IData , IDataCursor , IDataUtil , and IDataFactory . IDataMap implements the java.util.Map Java Collections Framework interface, providing a familiar and simple interface. IDataMap extends the map interface by adding getAs<Type> methods that convert the return value to a specific type.
And this happens as follows:
public static final void mapDocument(IData pipeline) throws ServiceException {
And the result

source share