Exploring the Pipeline Class Using Web Services Enhancements SP2
page 2 of 3
by Jayaram Krishnaswamy
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 17499/ 47

Pipeline Class: Properties and Methods

PipeLine Class Properties

The next tree diagram shows the properties of the Pipeline class expanded to show all the properties. Code snippets from the web service described in the next section will clarify some of the properties.

Examining the Properties with an Example

Create a web service project, herein called TPipeLine, remove the default Service1.asmx file and add a new web service file called, TPProps.asmx. Now apply web service extensions 2.0, by right clicking the highlighted project and clicking on WSE2.0 Settings... as shown.

This brings up the WSE2.0 settings dialogue as shown wherein you enable the two checkboxes, if you want to enable the second checkbox, you must have enabled the first. The first checkbox enables the project for WSE and the second will add the web service enhancement soap extensions to the project which is applicable to ASP.Net projects. The other tabs are not configured in the preparation of this tutorial.

The first check box adds reference to the Microsoft.web.services2.dll to the project and an element to the configuration of the web.config file as shown.

  <diagnostics />

The second checkbox adds the following to the configuration of the web.config file.

Microsoft.Web.Services2, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
priority="1" group="0" />

This procedure will be used in all the examples to follow as the various classes are explored.  In order to call up the Pipeline methods we need to instantiate a new instance of the pipeline using the constructor from among the overload list shown in this table.



Pipeline ()

Initializes a new instance of the Pipeline class.

Pipeline (Pipeline)

Initializes a new instance of the Pipeline class with the specified Pipeline object.

Pipeline (SoapInputFilterCollection, SoapOutputFilterCollection)

Initializes a new instance of Pipeline with the specified collections of SOAP input and output filters.

Actor Property

In the discussion to follow, we shall use the parameterless constructor for Pipeline. We shall add a WebMethod to the ASMX file after removing the HelloWorld example as shown. In order to reference the WSE2.0, an Imports Microsoft.Web.Services2 statement should be added to the TPProps class file. This property has a value System.Uri, the default value according to WSEREF [Web Services Extensions Reference Documentation] is Microsoft.Web.Services2.Addressing.WSAddressing.AnonymousRole. The following code will return the Pipeline's Actor property.

When you invoke this method in the browser, you will display the following, returned by the method:


InputFilters Property

As described in the basics, there are a number of filters in the pipeline and we should be able to find out what they are by looking at the InputFilters property by coding the following:
Return pline.InputFilters.Item(0).GetType.ToString
When the method is invoked in the browser, you display the following string:


In the same way, if you want to find how many filters there are, use the following:
Return pline.InputFilters.Count. This will display the following in the browser.


The following table summarizes the statements and the displayed results by invoking the method.


Type of Filter






Return pline.InputFilters.Item(1).GetType.ToString




Return pline.InputFilters.Item(2).GetType.ToString





OutputFilters Property

The OutputFilters property of the Pipeline follows the same pattern as the InputFilters property.  These are summarized in the following table.


Type of Filter

Return pline.OutputFilters.Item(0).GetType.ToString




Return pline.OutputFilters.Item(1).GetType.ToString




Return pline.OutputFilters.Item(2).GetType.ToString




IsIntermediary Property

When messages are going from an originating node(Sender) to an ultimate endpoint(Receiver) after passing thorough many 'routers'(soap Processing Nodes) in between, the IsIntermediary property provides a Boolean value of true, if the node is an Intermediary, and false otherwise. This property can also be set for a custom soap message. The following code returns a false as this node is not an intermediary.

Public Function PActor () As String
  Dim pline As New Pipeline
    Return pline.IsIntermediary
  Catch ex As SystemException
    Return ex.Message
  End Try
End Function

View Entire Article

User Comments

No comments posted yet.

Product Spotlight
Product Spotlight 

Community Advice: ASP | SQL | XML | Regular Expressions | Windows

©Copyright 1998-2024 ASPAlliance.com  |  Page Processed at 2024-06-15 2:30:18 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search