Programming Guide for Java › Task Execution Web Service › SOAP Messages

SOAP Messages

The Task Execution Web Service expects messages from the client to have the following characteristics:

• Message exchanges between the client and the web service are in the form of a SOAP Request-Response message exchange pattern (MEP).
• The ultimateReceiver for all requests is the web service.
• The web service throws a fault for any MustUnderstand SOAP header block. Also, NotUnderstood header blocks are generated for headers that cause this fault.
• A binding on a web service-enabled operation is a SOAP binding in the document binding style.

SOAP Limitations

SOAP requests use the pipe ("|") as a delimiter to separate values in multi-valued attributes. For example, for an address attribute you can have several values separated by a piper, such as 110 First Avenue | Boston | MA.

Do not use the pipe character as a delimiter for single-valued attributes. For example, a specification such as Name: John | Jones can cause the request to fail.