When overridden in a derived class, allows a SOAP extension to receive a SoapMessage to process at each SoapMessageStage.
Assembly: System.Web.Services (in System.Web.Services.dll)
Public MustOverride Sub ProcessMessage ( _ message As SoapMessage _ )
public abstract void ProcessMessage( SoapMessage message )
public: virtual void ProcessMessage( SoapMessage^ message ) abstract
abstract ProcessMessage : message:SoapMessage -> unit
Parameters
- message
- Type: System.Web.Services.Protocols.SoapMessage
The SoapMessage to process.
ProcessMessage is called at all SoapMessageStage stages for SOAP extensions applied to both XML Web services created using ASP.NET and their clients. At each SoapMessageStage, an instance of a class deriving from SoapMessage is passed to ProcessMessage. If the SOAP extension is running on the XML Web service client, then a SoapClientMessage object is passed into ProcessMessage; otherwise a SoapServerMessage object is passed in.
The following example is the ProcessMessage portion of a SOAP extension that logs SOAP requests and SOAP responses. By logging the SoapMessage at the AfterSerialize SoapMessageStage, the SOAP extension accesses the Stream to be sent over the wire. If the SOAP extension is applied to an XML Web service method created using ASP.NET, then the Stream contains the SOAP response from the XML Web service method. If the SOAP extension is applied to an XML Web service client, the Stream contains the SOAP request to an XML Web service method.
Classic SoapExtension.ProcessMessage Example#1
.NET Framework
Supported in: 4, 3.5, 3.0, 2.0, 1.1, 1.0.NET Framework Client Profile
Supported in: 4, 3.5 SP1Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.