One thing I'd note - Sanjiva writes:
REST is now beyond the peak of the hype curve and is sliding down. Waay down.
REST is now being seriously hyped, and it will eventually follow the inevitable curve – no objections (even though I saw things differently little over half a year ago). But I disagree it's beyond the peak already, on the contrary: it's still going way, way up.
For the record, I don't think the hype has got much to do with actual technical facts, positive or negative. Also for the record, I don't think users in general accept REST has won and the SOAP stack is a failure – in fact, most of them still don't know there are any doubts about how great WS-* is.
Still, I can't resist to respond to Sanjiva again:
Oh yeah we support both WS-* and RESTful services. However, they won't meet the RESTafarian fanatics like Tim Bray's coolaid drunkenness level of REST ..
You mean you don't like people to point out that Axis2's "REST support" has got nothing to do with REST? ;-)
Here's a very good summary of the problems when trying to align the WS-* and REST models:
IMO the real underlying problem is that as long as programmers expect to write a class and flip a switch to get a service or one or more RESTful resources then we have nothing really but RPC masquerading as something else. Both resource and service advocates would be well-off in trying to move the developer community to get past the “class is all I need” stage. If REST is successful in getting developers to get their hands dirty more power to it.