Integration Server 10.11 | Web Services Developer’s Guide | SOAP Message Exchange Patterns | Considerations When Changing a Provider’s Compatibility Mode | Impacts of Changing a Provider’s Compatibility Mode to True
 
Impacts of Changing a Provider’s Compatibility Mode to True
For provider web service descriptors, when you change the Pre-8.2 compatibility mode property from false to true, for operations that have no defined output, the MEP (either In-Only MEP or Robust In-Only MEP) becomes In-Out MEP.
*For a service first provider web service descriptor, when you change the Pre-8.2 compatibility mode property to true, Integration Server regenerates the WSDL and includes a <wsdl:output> element for the operation. As a result, the operation uses In-Out MEP. Integration Server issues a warning message letting you know the MEP has changed.
If handlers are assigned to the web service descriptor, because the MEP is now In-Out MEP, Integration Server starts executing the response and fault handler services.
*For a WSDL first provider web service descriptor, when you change the Pre-8.2 compatibility mode property to true, at run time, Integration Server will use In-Out MEP even when the WSDL for an operation does not include a <wsdl:output> element. Integration Server issues a warning message letting you know the MEP has changed.
If handlers are assigned to the web service descriptor, because the MEP is now In-Out MEP, Integration Server starts executing the response and fault handler services.
Note:
The Pre-8.2 compatibility mode property and the ability to run in pre-8.2 compatibility mode are deprecated as of Integration Server 10.4 due to the deprecation of the web services implementation introduced in Integration Server version 7.1.