Rules for parameter values

Previous Next

When defining a web service, if a parameter is based on a domain, its values are automatically converted by USoft to match the domain and domain restrictions. Domain constraints are not executed and some of the domain restrictions do not apply: Display type, Display length, Decimals displayed, Generate Unique Values, Default value, Perc. Full.

Other rules for input and output parameters depend on whether the method is an RPC-oriented method or a document-oriented method.

For document-oriented methods, the domain of a parameter, if any, must have IO Format set to: XML, and the datatype must be a string datatype. Parameter values for a document-oriented method must have as first element the parameter name.

For document-oriented, it is LOGICAL and HIGHLY RECOMMENDED to define one input parameter and one output parameter (XML document).

For RPC-oriented methods, the format of the parameters depends on the IO Format of the specified domain:

If the IO Format is : XML, XML documents must be received and returned. You have to take care that the first XML element in this XML document is the parameter name. This allows complex parameters to be defined as attributes, or attributes and elements (for example soap:Array).

Parameters that are defined based on a domain without IO Format or with an IO Format other than : XML, do not contain the parameter name in the XML document. USoft automatically handles the parameter names.

In both cases, USoft automatically handles the method name:

For input parameters, a method name that occurs within the received SOAP message is interpreted.

For output parameters, method names are added to a returning SOAP message.