This documentation is archived and is not being maintained.

SoapProcessingBehavior Class

Defines the client endpoint behavior used to marshal messages between different binding types and message versions.


Namespace:  System.ServiceModel.Routing
Assembly:  System.ServiceModel.Routing (in System.ServiceModel.Routing.dll)

public class SoapProcessingBehavior : IEndpointBehavior

The SoapProcessingBehavior type exposes the following members.

Public methodSoapProcessingBehaviorCreates a new instance of the SoapProcessingBehavior class.

Public propertyProcessMessagesGets or sets a value that indicates whether messages should be processed.

Public methodAddBindingParametersAdds new binding elements to an endpoint.
Public methodApplyClientBehaviorApplies the specified endpoint behavior to the client.
Public methodApplyDispatchBehaviorApplies the specified endpoint behavior to the endpoint dispatcher.
Public methodEquals(Object)Determines whether the specified Object is equal to the current Object. (Inherited from Object.)
Protected methodFinalizeAllows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection. (Inherited from Object.)
Public methodGetHashCodeServes as a hash function for a particular type. (Inherited from Object.)
Public methodGetTypeGets the Type of the current instance. (Inherited from Object.)
Protected methodMemberwiseCloneCreates a shallow copy of the current Object. (Inherited from Object.)
Public methodToStringReturns a string that represents the current object. (Inherited from Object.)
Public methodValidateValidates the service endpoint.

SOAP processing is the process where messages are converted between message versions.

Processing messages from one MessageVersion to another is accomplished by constructing a new WCF message that contains the body part and relevant headers from the incoming WCF message. Headers that are specific to addressing, or that are understood at the router level, are not used during construction of the new WCF message because these headers are either of a different version (in the case of addressing headers) or have been processed as part of the communication between the client and the router.

Whether a header is placed in the outbound message is determined by whether or not it was marked as understood as it passed through the incoming channel layer. Headers that are not understood (such as custom headers) are not removed and so pass through the routing service.

.NET Framework

Supported in: 4

.NET Framework Client Profile

Supported in: 4

Windows 7, Windows Vista SP1 or later, Windows XP SP3, 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.

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.