Issue R48 - first part resolution

Resolution to R48 - first half as agreed on TC call
Jan 24.

In 10.3.1

From

[existing static analysis requirement SA00050] When
<toParts> is present in an <invoke>, it is not required to
have a <toPart> for every part in the WSDL message definition, nor
is the order in which parts are specified relevant. Parts not explicitly
represented by <toPart> elements would result in uninitialized parts
in the target anonymous WSDL variable used by the <invoke> or <reply>
activity. Such processes with missing <toPart> elements MUST be rejected
during static analysis.

To: [updated static analysis requirement SA00050]
When <toParts> is present, it is required to have a <toPart>
for every part in the WSDL message definition; the order in which parts
are specified is irrelevant. Parts not explicitly represented by <toPart>
elements would result in uninitialized parts in the target anonymous WSDL
variable used by the <invoke> or <reply> activity. Such processes
with missing <toPart> elements MUST be rejected during static analysis.

Also change static analysis table entry

Regards, Diane

IBM  Emerging Internet Software Standards



(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709