We are constantly told that APIs built on REST have great advantages for distributed systems that have to be scalable. We are told this by speakers at conferences, by various blog writers that we read, and even by wikipedia. And then somewhere, they lose us. They start talking about Representational State transfer, and the transfer of "representations" of "resources". And somewhere in there they lose most people in the language they choose to describe what REST is.
REST
Submitted by david on Fri, 07/30/2010 - 22:56
I was toying with the idea of creating this as a generic Web Services Section, I think that REST is important enough to get it's own.
-
javaREST
-
Well, I've worked on Seam and RESTEasy integration last year, so this would be the comfortable option. The problem is: I know this stuff, so it's a safe fallback - I can always use that combination if everything else fails. But the grass always looks greener on the other side. So I definitely want to look at other solutions first, see what they have to offer. Also, Bill just now started talking about a non-servlet deployment option for RESTEasy, which is what I'd use.REST
-
In the Java™ world, you can build a RESTful web service in several ways: Some folks use JSR 311(JAX-RS) and its reference implementation Jersey, others use the Restlet framework, and some might even implement from scratch. Spring, the well-known framework for building Java EE applications, now supports REST in its MVC layer. This article introduces the "Spring way" to build RESTful web services. Learn how to use Spring APIs and annotations to build RESTful web services, and see how Spring integrates this new feature seamlessly into its original framework.RESTspringSpringMVC
