SoapProcessingBehavior Class

.NET Framework (current version)

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


Creates a new instance of the SoapProcessingBehavior class.


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

System_CAPS_pubmethodAddBindingParameters(ServiceEndpoint, BindingParameterCollection)

Adds new binding elements to an endpoint.

System_CAPS_pubmethodApplyClientBehavior(ServiceEndpoint, ClientRuntime)

Applies the specified endpoint behavior to the client.

System_CAPS_pubmethodApplyDispatchBehavior(ServiceEndpoint, EndpointDispatcher)

Applies the specified endpoint behavior to the endpoint dispatcher.


Determines whether the specified object is equal to the current object.(Inherited from Object.)


Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)


Serves as the default hash function. (Inherited from Object.)


Gets the Type of the current instance.(Inherited from Object.)


Creates a shallow copy of the current Object.(Inherited from Object.)


Returns a string that represents the current object.(Inherited from Object.)


Validates 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
Available since 4.0

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

Return to top