Impacts of Changing a Provider’s Compatibility Mode to False
When you change a provider web service descriptor’s Pre-8.2 compatibility mode property from true to false, In-Out MEP operations with no defined output change to In-Only MEP or Robust In-Only MEP.
For a service first provider web service descriptor, when you change the
Pre-8.2 compatibility mode property to
false,
Integration Server regenerates the WSDL. Because the service has no output,
Integration Server does
not include a
<wsdl:output> element for the operation. As a result, the operation changes to In-Only MEP. When the operation executes, it will no longer return a SOAP response.
Integration Server issues a warning message letting you know the MEP has changed. Also, if there are handlers assigned to the web service descriptor, because the operation now uses In-Only MEP, Integration Server will not execute the response or fault handler services.
For a WSDL first provider web service descriptor, when you change the
Pre-8.2 compatibility mode property to
false,
Integration Server begins to use the MEP that matches the operation’s WSDL. That is, if the operation:
Has no
<wsdl:output> and
<wsdl:fault> element, the operation will start using In-Only MEP. When the operation executes, it will no longer return a SOAP response.
Has no
<wsdl:output> element but does have a
<wsdl:fault> element, the operation will start using Robust In-Only MEP. When the operation executes, it will no longer return a SOAP response if the operation executes successfully, but will return a SOAP fault if an exception occurs.
Integration Server issues a warning message letting you know the MEP has changed. Also, if there are handlers assigned to the web service descriptor:
If the operation now uses In-Only MEP,
Integration Server will
not execute the response or fault handler services.
If the operation now uses Robust In-Only MEP,
Integration Server will only execute the response handler service if an exception occurs.