List of Figures | Programming MicrosoftВ® .NET XML Web Services (Pro-Developer)

Chapter 1: Web Services 101

Figure 1-1: A Web application as a three-tier application
Figure 1-2: Web services can be at the heart of everything.
Figure 1-3: The model for a .NET distributed enterprise application
Figure 1-4: The test page for our simple1.asmx service
Figure 1-5: Our service returns a response in raw XML.
Figure 1-6: The life cycle of a Web service request
Figure 1-7: A SOAP message has an Envelope that encompasses <Header> and <Body> elements.
Figure 1-8: Web Matrix has a Web service wizard.
Figure 1-9: A new service, but this time with a warning
Figure 1-10: Solution Explorer shows the files in our Web service project.
Figure 1-11: A simple Windows Forms client for our Web services
Figure 1-12: The Add Web Reference dialog box
Figure 1-13: Solution Explorer offers easy access to our Web service’s information.
Figure 1-14: Class view provides the name of the service proxy class and method signatures.
Figure 1-15: A simple Web client
Figure 1-16: A simple Web Forms client is just as effective as a Windows Forms client.
Figure 1-17: The Copy Project dialog box

Chapter 2: Web Services and SOAP

Figure 2-1: The traditional SOAP message structure
Figure 2-2: Form for sample Windows application that uses the CalcPercent Web service
Figure 2-3: Using the SOAPSender ASP.NET application to search for an artist
Figure 2-4: The SOAP document that the SOAPSender application returns
Figure 2-5: Using the SOAPSender ASP.NET form to log in as Chris
Figure 2-6: SOAP fault indicating that the closing <GetArtist> element was not found
Figure 2-7: Client application displaying details of a SoapException object to the user

Chapter 3: Describing Web Services

Figure 3-1: Major elements of WSDL and their relationships
Figure 3-2: Error returned when a one-way method returns a value
Figure 3-3: Documentation elements are pulled from the WSDL file.
Figure 3-4: Overloading methods isn’t as simple as it could be.
Figure 3-5: Overloaded methods take the wrong name.
Figure 3-6: Overloaded methods in the Object Browser
Figure 3-7: Proxy code created by wsdl.exe
Figure 3-8: The Add Web Reference dialog box
Figure 3-9: Finding the RecordFinder service
Figure 3-10: Viewing the proxy code
Figure 3-11: Proxy code created by Visual Studio .NET
Figure 3-12: Updating a Web reference

Chapter 4: Discovering Web Services

Figure 4-1: A dynamically generated discovery document
Figure 4-2: A discovery document from an .asmx file
Figure 4-3: Adding a reference using a discovery document in Visual Studio .NET 2003
Figure 4-4: Adding a reference using a discovery document in Visual Studio .NET 2002
Figure 4-5: Adding a reference from a discovery document with multiple Web services
Figure 4-6: Overview of the data structures used by UDDI
Figure 4-7: Searching the Microsoft UBR
Figure 4-8: Specifying the query type to further refine a search
Figure 4-9: Viewing service details
Figure 4-10: A provider added to the Microsoft UBR
Figure 4-11: A contact added to a provider
Figure 4-12: A tModel added
Figure 4-13: A WSDL document added to the tModel
Figure 4-14: A service added to the provider
Figure 4-15: An access point added to the service
Figure 4-16: Searching for a tModel to add to a service
Figure 4-17: Category details added to a service
Figure 4-18: A tModel added to a service binding
Figure 4-19: Web services that match the tModel
Figure 4-20: The results from a dynamically referenced Web service
Figure 4-21: Editing the business details
Figure 4-22: Editing the service details
Figure 4-23: Editing the binding details
Figure 4-24: Searching for tModels
Figure 4-25: Searching for Web services in Visual Studio .NET
Figure 4-26: Using the Add Web Reference dialog box to search for Web services
Figure 4-27: Adding a business to the Microsoft UBR in Visual Studio .NET
Figure 4-28: Adding a service to the Microsoft UBR in Visual Studio .NET
Figure 4-29: Managing roles with UDDI Enterprise Services

Chapter 5: Raw Handlers and Clients

Figure 5-1: The steps beneath the Web method abstraction
Figure 5-2: A simple response from a simple handler
Figure 5-3: The Add/Edit Application Extension Mapping dialog box
Figure 5-4: Restricting the HTTP request types allowed for a file extension.
Figure 5-5: How an ASP.NET request is passed to ASP.NET by IIS
Figure 5-6: The ASP.NET HTTP pipeline. Read-only classes are drawn as rectangles.
Figure 5-7: A child application’s pipeline settings are the sum of the root’s settings, its parent’s settings, and its own.
Figure 5-8: You can implement the client-side interaction with Web services using System.Net.
Figure 5-9: The user-interface elements of the client don’t need to be very complex.

Chapter 7: Creating Web Methods

Figure 7-1: Browsing the Service1.asmx file of RecordStoreWebService
Figure 7-2: Visual Studio .NET’s Add New Project dialog box with the Web Setup Project template selected
Figure 7-3: The Visual Studio .NET Add Project Output Group dialog box

Chapter 8: Consuming Web Services

Figure 8-1: Visual Studio .NET’s Add Web Reference dialog box
Figure 8-2: Newly added WeatherFetcher Web reference
Figure 8-3: Building a form for the USWeather Web service client in Visual Studio .NET
Figure 8-4: USWeather Web service client displaying formatted results
Figure 8-5: Using Visual Studio .NET’s Customize Toolbox dialog box to add the Windows Media Player component to a project
Figure 8-6: Forms Designer view of the main form of the Windows Forms Web service client
Figure 8-7: The famous Shane DeSeranno—vacant and happy
Figure 8-8: Designing a Web Forms application that calls a Web service asynchronously
Figure 8-9: Asynchronous USWeather Web service client in action
Figure 8-10: Designing a Web Forms application that calls a Web service asynchronously and that allows the calls to complete out of order
Figure 8-11: Calling a Web method several times with different data and then receiving the results out of order
Figure 8-12: Supplying a reference
Figure 8-13: Legacy Visual Basic 6.0 application accessing a .NET Web service
Figure 8-14: Viewing the XML returned by the USWeather Web service in Internet Explorer
Figure 8-15: ASP Web service client
Figure 8-16: Web service client application using XSLT

Chapter 9: ADO.NET and Web Services

Figure 9-1: Schema created from the Records table in DansRecords.mdb
Figure 9-2: A Windows Forms client application for FileSystemDataProvider
Figure 9-3: The FileSystemDataProvider client application downloading a file
Figure 9-4: The schema for FSDataSet shown in the Visual Studio .NET Schema view

Chapter 10: Extending the Web Services Framework

Figure 10-1: A closer look at HTTP modules in the grand scheme of the ASP.NET pipeline
Figure 10-2: SOAP extensions work within the default ASMX handlers.
Figure 10-3: Our SimpleModule successfully blocks requests with a 403 Forbidden response.
Figure 10-4: The events exposed by the HttpApplication object, in chronological order
Figure 10-5: EventListModule in action
Figure 10-6: Events are always handled in order by multiple modules and global.asax.
Figure 10-7: SimpleExtension blocks SOAP requests with a SOAP fault.
Figure 10-8: The order of method calls during the life of a SOAP extension
Figure 10-9: GetInitializer is called only once, but Initialize is called frequently. The initializer object remains in the ASP.NET cache throughout.
Figure 10-10: The LessThanExtension SOAP extension in action

Chapter 11: General Security

Figure 11-1: Configuring authentication methods in IIS Manager
Figure 11-2: The Authentication Client application accessing a Web service using anonymous authentication
Figure 11-3: The Authentication Client application accessing a Web service using Basic authentication
Figure 11-4: The Authentication Client application accessing a Web service using Digest authentication
Figure 11-5: The Authentication Client application accessing a Web service using Integrated authentication
Figure 11-6: Configuring a Web service to require SSL access

Chapter 12: The Global XML Web Services Architecture

Figure 12-1: A simple DIME message
Figure 12-2: The DIME record structure

Chapter 13: Web Service Enhancements

Figure 13-1: Message path through the WSE pipeline and the filters
Figure 13-2: The proxy class after manual editing to support WSE
Figure 13-3: Internal architecture of SoapHttpClientProtocol.Invoke
Figure 13-4: The Web Settings Tool generates the DiagnosticsWSWse class.
Figure 13-5: The SOAP envelope sent to the MakeMyDay method
Figure 13-6: The SOAP envelope returned from the MakeMyDay method
Figure 13-7: Trace filters don’t show DIME messages.
Figure 13-8: The trace utility allows you to debug DIME messages.
Figure 13-9: The TimestampClient application
Figure 13-10: Message returned showing the Timestamp details
Figure 13-11: Timestamp details with no expiration date
Figure 13-12: An expired message throws a TimestampFault exception.
Figure 13-13: The CustomFilterClient application
Figure 13-14: Entries written to event log by the custom filter

Chapter 14: Routing and Referral

Figure 14-1: Internal architecture of the RoutingHandler.ProcessRequest method
Figure 14-2: Basic server-controlled routing scenario
Figure 14-3: We can’t view WSDL for a router.
Figure 14-4: The RoutingClient application showing the server-controlled routing tab
Figure 14-5: Return showing the path that was taken to TellMe.asmx
Figure 14-6: Server-controlled routing chain
Figure 14-7: Routing chains on the same server are optimized.
Figure 14-8: The custom routing scenario
Figure 14-9: The RoutingClient application showing the Custom tab
Figure 14-10: Returned message from Tokyo.asmx showing the path taken to the Web service
Figure 14-11: The RoutingClient application showing the client-controlled routing tab
Figure 14-12: Returned message showing the path that was taken to TellMe.asmx

Chapter 15: Web Service Security

Figure 15-1: Viewing certificates for the current user
Figure 15-2: Viewing certificates in the Local Computer certificate store
Figure 15-3: SecurityToken inheritance
Figure 15-4: The AuthenticationClient application
Figure 15-5: The X509Client application
Figure 15-6: The PartsClient application

Chapter 16: Looking to the Future

Figure 16-1: The basic plumbing of the WSA and the standards that currently implement it
Figure 16-2: The wire stack and the technologies involved in each layer
Figure 16-3: The WSA description stack
Figure 16-4: The current implementation of the discovery agencies stack is almost completely dependent on UDDI.
Figure 16-5: The Extended Web Services Architecture

Appendix A: The XSD Simple Types

Figure A-1: The conceptual type hierarchy
Figure A-2: The numeric type group; primitive types are in ovals.
Figure A-3: The date and time type group contains only primitive types.
Figure A-4: The XML type group
Figure A-5: The remaining three XSD built-in types are all primitive types.