WCF Extensibility for Interoperability….

Jurgen’s posted a great real world example of why WCF extensibility is essential for interop. The scenario he describes is that of having to a connect a TANDEM system written in COBOL to a Windows client using WCF. Which is an example of why you would need WCF extensibility even if SOAP is used. But what if…

0

Contract-first Design Quotes

Relevant Quote Link The trouble is this promotes a very code-first approach. This really sucks from a BizTalk developer’s point of view. I already have my schemas. I know the shape of the messages I want to receive. Where’s the support for the Schema- and WSDL-first approach? http://geekswithblogs.net/dmillard/archive/2004/11/09/14651.aspx If contract-first means wrestling with the nine-headed…

0

How Actions differ from Operations…

I haven’t thought about the relationship between “Actions” and “Operations” for quite a while. Therefore, I thought I’d give my brain dump. I look forward to your feedback in case I have it wrong.   First, I thought it useful to summarize the description of a SoapAction:   An action (or SoapAction in Soap 1.1)…

0

Contract-first Domain Specific Language (DSL)

Pedro was kind enough inform me about this cool DSL called “Contract-first” DSL: http://www.edwardbakker.nl/PermaLink,guid,0f4e80f7-2ebd-4ab4-a8b4-954cadfc622b.aspx I recommend that you take a look. I am eagerly waiting to play with this once is made public. Cheers, Ali

1

Adding DataSets to services… Why not?

There a lot of customers, for better or worse, who are using DataSets in their services and (I shudder as I say this) there are times when it might make sense to do so. An example might be when the developer has control of both the client and the service provider, is working in .NET, and…

0

Operation inference and Contract-first Design

After Tomas’s comment on my last blog, I’ve been thinking about the operation inference feature in Christian’s WSCF tool. I’m not sure that inferring operations based on the message name has been standardized. (Please correct me if I’m wrong) I’ve, nevertheless, noticed that several companies such as eBay name their messages in a standard manner…

3

It’s about the schema, stupid!

One of my big realizations has been that Contract-first is not about the WSDL it’s about the schema. CWeyer’s tool generates a WSDL, but the value of the tool is that it allows you to stich together the schema for the data/messages that you have created. A lot of customers today spend most of their…

4

Policy and Contract-first Design

After talking to a lot of people, I am trying to cement the relationship of policy to the contract. There is a thought that policy is part of the contract. That policy is created up front and negotiated between the two parties alongside the rest of the contract (i.e. WSDL). Others have aligned themselves better with the four…

2

Great quotes on Contract-driven (aka Contract-First) Development…

I was trying to get a pulse on Contract-driven Development and what the industry was saying, so I compiled a list of quotes and links. As I think this might be useful for anyone interested in the area, I thought I’d share this out. Let me know what you think and if you have anything…

2

Describing a reference model for SOA…

I got an email from Nichole last week about a talk that she was going to give on the OASIS Reference Model for SOA this Wednesday (tommorow) on the Microsoft campus. See: http://www.iasahome.org/iasaweb/appmanager/home/chapterdetail?_nfpb=true&_pageLabel=chapterdetail_meetings&chapterdetail_meeting_portletid=15401&chapterdetail_meeting_portletchannel=3216 As this was the first time that I had heard of the reference model, I decided to read through it. Fortunately, I found nothing…

2