Comments on: How IBM WebSphere got REST Religion but forgot to tell anyone. Thoughts from Connect09

By: James Governor

James Governor — Tue, 08 Dec 2009 18:23:08 +0000

ATM – thanks for the clarifications. but if anyone was guilty of over selling UDDI it was systinet… http://www.redmonk.com/jgovernor/2006/01/09/mercury-buys-systinet-uddi-way-or-the-highway/

By: Anne Thomas Manes

Anne Thomas Manes — Wed, 02 Dec 2009 18:56:14 +0000

Just thought I’d point out that WSRR never implemented UDDI. In response to customer demand, IBM enabled WSRR to UDDI synchronization, but WSRR has always used a proprietary model and API. It was originally a bit REST-like — except that it used a proprietary URL-like addressing scheme to reference entries in the registry. In v2 they got some sense and exposed those entries directly via URLs and HTTP. But the RESTiness only works for artifacts (WSDLs, schemas, etc) in the registry. Nice that they now make updates to the registry available via Atom, but it’s a bit late in coming. And the registry is still only partially RESTful. Meanwhile HP’s Systinet Repository has always been completely RESTful — everything in the repository (including stored queries) is accessed via a URL, and any query can be exposed as an Atom feed. (Note that Systinet Repository is different from Systinet Registry — which is UDDI compliant.)

By: uogbuji

uogbuji — Wed, 02 Dec 2009 17:09:38 +0000

♺@distobj my old InfoQ hypermedia article getting link love from #redmonk. One of my best articles. http://is.gd/5a85l http://is.gd/5a86S

This comment was originally posted on Twitter

By: distobj

distobj — Wed, 02 Dec 2009 15:54:53 +0000

my old InfoQ hypermedia article getting some link love from #redmonk. One of my best articles. http://is.gd/5a85l http://is.gd/5a86S

This comment was originally posted on Twitter

By: Analyst: IBM WebSphere appears to be more well-RESTed | Service-Oriented Architecture | ZDNet.com

Sun, 29 Nov 2009 17:12:43 +0000

[...] products. James Governor, for one, says IBM — without much fanfare — is now enabling service oriented architecture through the REST style of architecture on its WebSphere registry/repos…. In all fairness, IBM claims it did send out the memo on that. Nevertheless, this represents a sea [...]

By: Barb

Barb — Thu, 26 Nov 2009 01:31:23 +0000

But just because IBM is now taking advantage of REST and more lightweight integration methods doesn’t mean its customers are. IBM’s main education efforts in SOA were about the style that is now being superceded. IBM customers are usually two to three, if not four to five, years behind current state of the art. Its time for IBM to start beating the drum for the new development and integration style. Customers are behind the curve. Federation is as good a place as any to start.

This comment was originally posted on FriendFeed

By: c1pher

c1pher — Wed, 25 Nov 2009 22:31:48 +0000

How IBM WebSphere got REST Religion but forgot to tell anyone. Thoughts from Connect09 http://bit.ly/5bdldN (via feedly)

This comment was originally posted on Twitter

By: monkchips

monkchips — Wed, 25 Nov 2009 15:09:24 +0000

That said, the title “Will WOA API Adoption Kill Integration?” is kind of silly. Of course not. See http://bit.ly/65paXq

This comment was originally posted on Twitter

By: vlvl

vlvl — Wed, 25 Nov 2009 07:02:22 +0000

Ha! @monkchips gets the question right – http://bit.ly/5uK9vi – how to connect on-demand offerings with existing on-premise applications?

This comment was originally posted on Twitter

By: andrkoel

andrkoel — Tue, 24 Nov 2009 21:12:27 +0000

soa evolution in websphere: more rest http://bit.ly/7bUT9B “We told you guys to do SOA but instead you did point to point ESB integration”

This comment was originally posted on Twitter