| Creating and Using Custom SOAP Headers |
| ASP Alliance |
| This quick demo shows you how to create and consume a .NET Web Service using a custom SOAP Header. This first part demonstrates how to create the Web Service. Notice that we first need to import the System.Web.Services.Protocols namespace (**1**). Then we create our class (**2**) that we want to use for the SOAP Header. And lastly we create an instance of the SOAP Header class (**3**) in our Web Service class, and then specify the SoapHeaderAttribute() (**4**). |
|
| Interoperability with Message Exchange Patterns Created Using BEA WebLogic 8.1.3 |
| MSDN |
| Covers interoperability using message exchange patterns and shows how a pattern can be implemented using BEA WebLogic 8.1.3. |
|
| Intrusion Prevention: Build Security Into Your Web Services with WSE 2.0 and ISA Server 2004 |
| MSDN |
| Web Services Enhancements 2.0 and ISA Server 2004 help you build better Web services security |
|
| Licensing Your ASPNet Web Services |
| DotNetJunkies |
| While ASP.Net makes building powerful SOAP based web services quick and easy, their usefulness in a business context is limited until one can effectively license those web services. Licensing requires the ability to examine each method invocation, determine whether or not the call is being made by a valid client and then reject or allow the call based on that determination. This article will explain one way to use Visual Studio .Net to tackle this issue. Specifically, we’ll explore using a combination of cu |
|
| Reliable XML Web Services |
| MSDN |
| Among the various FAQs about building XML Web services, reliability falls into the top five issues facing developers implementing decentralized Web services. The problem space, when broken down into small pieces, is not that difficult. So, this month I decided to jump off into the extreme area of building reliable XML Web services. |
|
| Using SOAP Header to Authenticate a Web Service Consumer |
| C# Corner |
| In this Article we are going to use SOAP Header to authenticate the WebService users. Let’s consider a WebService that allows consumers to get the order details based on order ID (which they placed from the web). |
|
| Using Web Services Instead of DCOM |
| MSDN |
| This document examines the advantages of using XML Web services over DCOM and demonstrates how to implement an XML Web service and consume it with a Microsoft .NET client application |
|
| Web Services Security in The .NET Framework |
| 15 Seconds |
| Security has always been a top issue for all kinds of applications, especially Web applications. Web apps are accessible to almost the entire universe and are open to attack. |
|
