3.1.4.92 IsParameterReferencedByMethodInstance

The IsParameterReferencedByMethodInstance operation checks whether the specified Parameter contains any TypeDescriptor that is the ReturnTypeDescriptor of any MethodInstance contained by the Method containing the Parameter.

The following is the WSDL port type specification of the IsParameterReferencedByMethodInstance WSDL operation.

 <wsdl:operation name="IsParameterReferencedByMethodInstance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
   <wsdl:input wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/IsParameterReferencedByMethodInstance" message="tns:BusinessDataCatalogSharedService_IsParameterReferencedByMethodInstance_InputMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:output wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/IsParameterReferencedByMethodInstanceResponse" message="tns:BusinessDataCatalogSharedService_IsParameterReferencedByMethodInstance_OutputMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/IsParameterReferencedByMethodInstanceArgumentExceptionFault" name="ArgumentExceptionFault" message="tns:BusinessDataCatalogSharedService_IsParameterReferencedByMethodInstance_ArgumentExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/IsParameterReferencedByMethodInstanceArgumentNullExceptionFault" name="ArgumentNullExceptionFault" message="tns:BusinessDataCatalogSharedService_IsParameterReferencedByMethodInstance_ArgumentNullExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/IsParameterReferencedByMethodInstanceArgumentOutOfRangeExceptionFault" name="ArgumentOutOfRangeExceptionFault" message="tns:BusinessDataCatalogSharedService_IsParameterReferencedByMethodInstance_ArgumentOutOfRangeExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/IsParameterReferencedByMethodInstanceBdcExceptionStateFault" name="BdcExceptionStateFault" message="tns:BusinessDataCatalogSharedService_IsParameterReferencedByMethodInstance_BdcExceptionStateFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/IsParameterReferencedByMethodInstanceInvalidOperationExceptionFault" name="InvalidOperationExceptionFault" message="tns:BusinessDataCatalogSharedService_IsParameterReferencedByMethodInstance_InvalidOperationExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/IsParameterReferencedByMethodInstanceMetadataExceptionStateFault" name="MetadataExceptionStateFault" message="tns:BusinessDataCatalogSharedService_IsParameterReferencedByMethodInstance_MetadataExceptionStateFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
 </wsdl:operation>

The protocol client sends a BusinessDataCatalogSharedService_IsParameterReferencedByMethodInstance_InputMessage request message, and the protocol server MUST respond with a BusinessDataCatalogSharedService_IsParameterReferencedByMethodInstance_OutputMessage response message, unless any one of the conditions in the following table is met.

If any one of the conditions in the following table is met, the protocol server MUST instead respond  with a SOAP fault containing the corresponding error complex type, serialized as specified in section 2.2.4. If more than one error condition is encountered, the protocol server MUST respond with exactly one error complex type, determined in an implementation-specific manner.