Web Services Quiz: Issue 10 – the Answer

The correct answer to Issue 10 was already mentioned by Andrew & Mario:   Service T1 will deny access, and therefore return a HTTP status 401 error: “Access Denied”   If we want to allow the called services to impersonate the caller’s identity, we have to explicitly pass on its credentials. In the default scenario,…


Interested in Z#?

A. Wöß and H. Mössenböck from the University of Linz just published the following courseware:   Compiler Construction – Concepts and Practical Application to .NETThis course builds a complete compiler for the programming language Z# (= subset of C#) that produces .NET executables. It will teach students the following skills: Acquire the practical skills to…


What’s wrong with rpc-literal?

This post is part of Issue 8’s answer   To say it as clear and simple as possible: rpc style encoding is more about the service implementation than the message on the wire itself. That’s just wrong! As already discussed in this answer series, every rpc-literal message can be described using doc-literal encodings. Therefore there…


How to consume an rpc-literal WS using .NET?

This post is part of Issue 8’s answer   The previous post in this answer series discussed rpc-literal from a platform independent standpoint, where this post focuses on the consumption of such services using .NET. You may ask why consumption only? Well, rpc-literal is so bad that you won’t use it for your own services….


What is rpc-literal anyway?

Although it’s a longtime ago, I want to follow up with the promised explanations for Issue 8:   Prolog: WS BP 1.0 prohibits the usage of rpc-encoded but explicitly allows rpc-literal. But what is rpc-literal anyway?   Rpc stands for remote procedure call. If you want to apply this technology in loosely coupled environments, you’ll…


Web Services Quiz: Issue 8 – the Answer

The number one problem in dealing with rpc-literal Web Services is the fact that they are unsupported on the .NET platform, yet. However, every rpc-literal message can be “built” using a doc-literal based implementations. By doing so, the .NET stub for the WSDL defined in Issue 8 may look the following:   [WebServiceBinding(Name=”CalculatorSoap”, Namespace=”uri.test.com”)] public…


Web Services Quiz: Issue 8

Given the following WSDL, how does your .NET proxy and stub look like? As always, answer and explanation will follow…   Note, it’s rpc-literal …   <?xml version=”1.0″ encoding=”utf-8″?> <wsdl:definitions targetNamespace=”uri.test.com”   xmlns:wsdl=”http://schemas.xmlsoap.org/wsdl/” xmlns:soap=”http://schemas.xmlsoap.org/wsdl/soap/” xmlns😡sd=”http://www.w3.org/2001/XMLSchema” xmlns:tns=”uri.test.com” xmlns=”http://schemas.xmlsoap.org/wsdl/”>    <wsdl:types>       <xsd:schema elementFormDefault=”qualified” targetNamespace=”uri.test.com”>                    <xsd:complexType name=”AddRequestType”>             <xsd:sequence>                <xsd:element minOccurs=”1″ maxOccurs=”1″ name=”a”…