At least one developer has turned away from SOAP Web Services to REST Web Services because REST is easier to understand and has a shorter time to productivity. REST is lightweight enough that it can still be done by hand (without IDE wizards). REST models itself after the web and runs on the HTTP Protocol. Knowledge about scaling, caching, and securing web pages can be applied to REST Web Service URLs. This presentation will demonstrate one approach to provide REST Web Services using the following enabling technologies:
Richard works as a Java Developer providing application solutions written in Java, Spring, JDBC, JSP and Swing. Richard has presented at Spring Dallas User Group and Talk Java, Drink Java and taught college courses in Web Page Design and Computer Game Programming. His experience includes Order and Inventory Tracking Systems and Financial Banking. He thinks the following are intensely great technologies: Java, Groovy, Grails, Spring, Apache Commons, Eclipse, Maven, JavaDoc, Google, the Internet, Tomcat, REST Web Services and 3-D Computer Games. He enjoys making art images by programming with Processing.org and Groovy. After riding the Java bandwagon, he has jumped onto the Spring bandwagon, thankfully missed the EJB one and has so far refused to get on the PHP bandwagon. Richard feels an affinity for Agile software practices.
This presentation was presented to the Spring Dallas User Group on Wednesday 10/17/2007.
