• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (5)

1 localhost commented Permalink

Bill: Yeah, I think REST is simply not on most enterprise application architects' radar. J2EE uses JAX-RPC, which uses SOAP and WSDL; Web services = SOAP; case closed.One of the main motivations for using Web services and SOAP from J2EE is interoperability with non-J2EE apps (.NET, etc.). So the REST advocates need to start publishing articles showing how J2EE and .NET apps can be integrated using REST--otherwise, everyone assumes SOAP is the way to go.

2 localhost commented Permalink

It would be interesting to ask some of your enterprise clients' architects and developers whether or not they're familiar with REST, whether or not they'd consider it to support enterprise business apps, and why or why not.

3 localhost commented Permalink

"As I've already noted in REST vs. SOAP/WSDL, Amazon claims (according to Tim O'Reilly) that its AWS traffic is 85% REST, 15% SOAP. So REST proponents claim anecdotal evidence like this means REST is more popular.""But I'm interested in the enterprise application market, not the hobbyist market, and enterprise applications that use Web services use SOAP.""But for now at least, SOAP is the "most common" Web services technology."this series of statements seems predicated on the notion that the volume of enterprise web services outweighs the volume of non-enterprise web services - are you sure that's true? in other words, are the production implementations of J2EE - or .NET, for that matter - greater or fewer in number than the implementations of Amazon, del.icio.us, eBay, Flickr, Google, Yahoo, etc?i think it would be more accurate to say that "for now at least, SOAP is the "most common" [enterprise] Web services technology."but maybe it's just me.

4 localhost commented Permalink

Stephen: OK, enterprise Web services. (Whatever those are.) This is a J2EE blog.As for the volume litmus test: Spam's the most popular type of e-mail; doesn't make it best; doesn't even make it popular.

5 localhost commented Permalink

It seems that you're assuming that because an enterprise doesn't know what REST is, that it therefore isn't using it. I think that's an incorrect assumption.Perhaps you should ask your enterprise clients how many are exchanging data over email, FTP, or HTTP. If any say yes, then, if they're not doing full blown REST, they're at least doing the most important part (the uniform interface).

Add a Comment Add a Comment