If a BPEL process has multiple WSDL messages declared in its WSDL file and one or more messages have their parts defined to be of some type, whereas other messages have their parts defined to be of some element, runtime behavior can become unpredictable. This is because these WSDLs are considered to have mixed type messages. For example, assume there are multiple copy actions within an assign activity. These copy actions attempt to populate an output variable that has multiple parts:

• Part 1 is declared as an xsd:string type.

• Part 2 is declared as an xsd:int type.

• Part 3 is declared as an element of a custom-designed complex type.

This behavior is not supported.