Jersey is the reference implementation of JAX-RS and is the implementation that you will find in both WebLogic Server and GlassFish. Lets take a look at the programming model.First, if you stick with the best practices and the standard approach to REST you will create ‘services’ out of ‘resources’. At runtime, you will be able to generate a WADL which specifies the URIs and supported HTTP methods/verbs (GET, PUT, POST, DELETE) and you can use this to create client-side applications. The JAX-RS specification only provides details for server-side APIs but if you use Jersey then you can take advantage of the classes that it offers to consume REST services.Just like SOAP, the container will take care of mapping your data representation, whether it is in XML or JSON, to your Java POJOs. In addition, JAX-RS takes care of HTTP handshaking and allows you to perform content negotiation at runtime. Also, JAX-RS supports HTTP communication ONLY. There are no other transports supported.
Evolution over XML-RPCAllowed you to get around firewalls with HTTPSimply put, a format for sending messages
Both SOAP and REST have their rightful place within enterprise and consumer applications, and there is no reason they can’t co-exist and support the same enterprise application. REST is ideally suited for exposing data over the internet (or networks in general) and has low bandwidth and CPU requirements. It’s also good for creating mashups of different content from various providers on a web page.However, if you look at the enterprise requirements for messaging, you may find that SOAP is a better fit because it offers enterprise features like High Reliability with WS-RM
RESTful Services with JAX-RS, JQuery Bonus Content: JSF 2.0 Jeffrey West Application Grid Product Management
JAX-RS(Jersey) Programming Model Stub Resource JAX-RS API JAX-RS API Server Side Runtime System Client side Runtime System Protocol (REST/HTTP) Transport WADL Service Client Service Endpoint Container WADL<->Java Mapping Dispatch
REST – Representational State Transfer JSR-311: JAX-RS Exposes named RESOURCES which represent DATA Resource: POJO URI path template ID Uses simple Nouns (Resources) and verbs (HTTP Methods) GET/PUT/POST/DELETE Emphasis on simple, stateless point-to-point communication over HTTP Supports multiple data formats JSON/XML/TEXT/XHTML Runtime Content Negotiation
SOAP – Simple Object Access Protocol Exposes OPERATIONS that implement/represent LOGIC Provides loose coupling for integrating diverse systems Designed for distributed computing Designed to be extensible – WS-* Standard error messaging – SOAP faults with standard Code/Subcode for error types Aligns with Enterprise Application needs and goals Supports other transport protocols than HTTP – SMTP, JMS Supports enterprise security with WS-Security Supports language neutrality Supports ACID, Atomic transactions with WS-AT Supports Reliable Messaging with WS-RM Easy governance with strong typing Broad Development Tools support
REST vs. SOAP REST Exposes RESOURCES which represent DATA Uses HTTP Verbs (GET/POST/DELETE) Emphasis on simple point-to-point communication over HTTP Supports multiple data formats Emphasizes stateless communication SOAP Exposes OPERATIONS which represent LOGIC Uses HTTP POST Emphasis on loosely coupled distributed messaging Supports only XML (and attachments) Supports stateless and stateful/conversational operations Supports asynchronous messaging Strong Typing
SOAP is better than REST! Building a client for REST can be challenging I can easily generate client-side artifacts from a WSDL I don’t want to write raw HTTP calls I don’t want to look at the HTTP response code for success/failure – I want to use my own exception types and codes Many IDE’s support SOAP development – both client and server REST only supports HTTP/HTTPS HTTP is synchronous and in order to scale I need to be able to have asynchronous messaging REST is not secure Parameters as part of the URI No support for acquiring tokens RESTful services have no contract I have a WADL that specifies URL’s but what about schemas for object definition REST is not reliable I have to handle failures with retries – no Reliable Messaging REST can’t be governed How do I know who is consuming my services without a Service Registry? How do I discover RESTful services?
Both SOAP and REST have their rightful places REST Good for: Web Services Limited bandwidth (smaller message size) Limited resources (no xml parsing required) Exposing data over the Internet Combining content from many different sources in a web browser SOAP Good for: Enterprise services High Reliability with WS-RM Transactions with WS-AT Security with WS-Security Asynchronous processing Contract-first development Stateful /conversational operations Standards support, interoperability with business applications Tooling Support
JSF 2.0 Great Blog Post: http://andyschwartz.wordpress.com/2009/07/31/whats-new-in-jsf-2/#ajax Annotation-Driven Managed Bean Annotations Converter Annotations Composite Components Not required: UIComponent, Renderer, faces-config.xml Ajax support Navigation Implicit Navigation Conditional Navigation Project Stage: ‘Development’ provides more detailed error messaging (not just HTTP 500) Resource Libraries Loading ‘Libraries’ for CSS, Images, Etc
PrimeFaces – www.primefaces.org “PrimeFaces is a lightweight open source component suite for Java Server Faces 2.0 featuring 100+ rich set of JSF components” Easy to use, good looking components Multiple themes