I've held off posting on the WSDL-first approach so far because I've been waiting for the tools to arrive to make my gripes go away. Well, I'm still waiting... and waiting... In the BizTalk world, we already have a Service Oriented mindset. We communicate in terms of schema-defined documents; we offer up services not APIs. We want to be interoperable with as many people as possible. I don't care whether you're using Java, .NET or ARM assembler - if you can send me a soap message, I'll talk to you. ......
Things I like to see in my MSN window #1:
"Can you get up to TVP? Halo 2 team are here and we're playing."
WOOHOO! Just had a 6 minute deathmatch round against the UK XBox team. We lost about 50-20, which is pretty shabby, but I did manage to score a double kill. Dual wielding SMGs is teh roxx0rs! I just about resisted temptation to hit campaign mode ;-)
Roll on Thursday.
I was chatting to my colleague Charles Young earlier today and it reminded me of an idea that I had a while back. Wouldn't it be nice if, instead of having expression shapes (and the awful expression editor window ;-) ), we instead had an ASP.NET-like "code behind" model allowing us to use any .NET language, and not have to worry about working within the restrictions of XLANG/s. Of course I appreciate the design principle that Orchestrations shouldn't be littered with code and you should instead ......