I’m sure everyone saw Tim’s post today, but while looking for something official on BEA’s commercial support for Spring, I also saw this: http://dev2dev.bea.com/blog/wgroth2/archive/2007/02/web_20_rest_and.html. There is absolutely nothing amazing about the code shown. In fact, there’s nothing particularly BEA-y about it either. But what is just a little interesting is that the VP of BEA Workshop felt compelled to show that they too can do REST.
{ 2007 02 05 }
Greg Clarke | 09-Feb-07 at 8:28 pm | Permalink
Yes, hopefully the momentum is building.
Interesting that Bill wanted to prove they can “do REST” by showing how to consume a service. He doesn’t show how to provide a REST service from his product.
I had a conversation with a different big vendor pre-sales tech yesterday that went something like this.
Me: “You’ve shown us how to create a SOAP/XML service, but how would we present that as a plain XML service?”
Vendor: “Oh you mean REST. That would be hard - you’d have to write something to strip off the SOAP and then you’d have to build a URL destination somehow. But I really don’t understand why you would want to do that anyway. None of our other customers are asking for REST. Wouldn’t you want to use the most standards-compliant way of building services? Anybody using .net or similar will have the tools to support SOAP.”
Eric Newcomer's Weblog | 13-Feb-07 at 4:25 pm | Permalink
WS-* vs REST is not the question…
It’s nice to see the Workshop get some attention in the blogosphere (hope I constructed those Google and Technorati searches ok). For a while there I wasn’t sure it was going to happen. But it’s a bit disconcerting to see how much of the interest is…