Error "SOAP Binding does not support Document-style Operations with Messages containing Multiple Parts" is seen after migrating a product from a previous version to ActiveMatrix 3.3.0.

Error "SOAP Binding does not support Document-style Operations with Messages containing Multiple Parts" is seen after migrating a product from a previous version to ActiveMatrix 3.3.0.

book

Article ID: KB0075813

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix Service Grid -
TIBCO ActiveMatrix Service Bus -
Not Applicable -

Description

Description:
After migrating a legacy project from a previous version to TIBCO ActiveMatrix ("AMX") 3.3.0, the following error is seen in Service and Reference:

SOAP Binding does not support Document-style Operations with Messages containing Multiple Parts, if ALL the parts are mapped to Header (for instance, Operation: 'processMessage', Message: 'processMessageRequest').   /CRIFRetail/Composites/CRIFRetail.composite   /CRIFRetail/Composites   _XQSCj2M1EeOJhrL9WFCaZw   EMF Validation Problems
SOAP Binding does not support Document-style Operations with Messages containing Multiple Parts, if ALL the parts are mapped to Header (for instance, Operation: 'urn:crif-messagegateway:2006-08-23/ProcessMessage', Message: 'ProcessMessageSoapIn').   /CRIFRetail/Composites/CRIFRetail.composite   /CRIFRetail/Composites   _XQSCnmM1EeOJhrL9WFCaZw   EMF Validation Problems

Symptoms:
The same project runs without issue in a previous version of AMX.

Cause:

We are doing a stricter service validation (mainly regarding WSI-BP) in AMX 3.3.0. One of the constraints involved is "Not Supported Multipart Types validation". For some use cases, there may be a false alarm thus the constraint needs to be re-evaluated in future release.

Issue/Introduction

Error "SOAP Binding does not support Document-style Operations with Messages containing Multiple Parts" is seen after migrating a product from a previous version to ActiveMatrix 3.3.0.

Resolution

If this problem is reported when migrating an existing project (which worked fine in a previous AMX version) to AMX 3.3.0, it is usually a false positive. The workaround is to disable the constraint as shown in the attached image (Filename: disable.png) and clean the workspace. If the problem is seen in a new project, you may disable the constraint but make sure to verify that everything works at run time as there might be a true WSI-BP violation.

Attachments

Error "SOAP Binding does not support Document-style Operations with Messages containing Multiple Parts" is seen after migrating a product from a previous version to ActiveMatrix 3.3.0. get_app