The Cave

18 Feb

JSR 311

JSR-311 Java API for RESTful Web Services

Ummm, OK. Good in concept, but considering the, er, mixed quality coming out of JSRland I’m not sure I’m keen on this.

Sidebar: Is ‘random quality’ a less disparaging term?

I could enumerate reasons to be uneasily concerned about the outcome, but others have already done the job for me:

Remember, these are the same jokers who gave us servlets and the
URLConnection class as well as gems like JAX-RPC and JAX-WS. They still
seem to believe that these are actually good specs, and they are
proposing to tunnel REST services through JAX-WS (Java API for XML Web
Services) endpoints.

and then goes from bad to worse

To give you an idea of the background we’re dealing with here, one of
the two people who wrote the proposal “represents Sun on the W3C XML
Protocol and W3C WS-Addressing working groups where he is co-editor of
the SOAP 1.2 and WS-Addressing 1.0 specifications. Marc was
co-specification lead for JAX-WS 2.0 (the Java API for Web Services)
developed at the JCP and has also served as Sun’s technical lead and
alternate board member at the Web Services Interoperability Organization
(WS-I).”

The other submitter seems to be a primary instigator of the Fast Infoset
effort to hide XML in binary goop.

A tad more doom’n'gloom perhaps than likely, but for several reasons (all too understandable) this should be viewed with cautious skepticism, despite any hopeful optimism.

Read the posted responses for more details.

FacebookGoogle GmailGoogle BookmarksTechnorati FavoritesTwitterHotmailYahoo MailYahoo MessengerWordPressStumbleUponRedditEmailInstapaperGoogle+Share

Comments are closed.

© 2014 The Cave | Entries (RSS) and Comments (RSS)

GPS Reviews and news from GPS Gazettewordpress logo