JAX-RS 2.0: RESTful Java on Steroids

JAX-RS 2.0: RESTful Java on Steroids What’s in JSR-339?

Marek Potociar JAX-RS 2.0 Specification Lead Oracle

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Part I. How we got here…


• RESTFul Principles –  Assign everything an ID –  Link things together –  Use common set of methods –  Allow multiple representations –  Stateless communications

Shortest REST Primer Ever


•  JAX-RS 1.0 is Java API for RESTful Services –  Current version: JAX-RS 1.1

• Goals –  POJO-Based Resource API •  Server-side

–  HTTP Centric –  Entity Format Independence –  Container Independence –  Inclusion in Java EE •  But no hard dependency on Java EE though

JAX-RS Intro


@Path(“atm/{cardId}")public class AtmResource {

@GET @Path(“balance") @Produces("text/plain") public String balance(@PathParam("cardId") String card, @QueryParam("pin") String pin) { return Double.toString(getBalance(card, pin)); } …

JAX-RS API




JAX-RS API

Resource path templates




JAX-RS API


URI parameter injection




JAX-RS API



HTTP method binding




JAX-RS API


Built-in Serialization


HTTP method binding


…

@POST @Path(“withdrawal") @Consumes("text/plain") @Produces("application/json") public Money withdraw(@PathParam("card") String card, @QueryParam("pin") String pin, String amount){ return getMoney(card, pin, amount); }}

JAX-RS API


…

@POST @Path(“withdrawal") @Consumes("text/plain") @Produces("application/json") public Money withdraw(@PathParam("card") String card, @QueryParam("pin") String pin, String amount){ return getMoney(card, pin, amount); }}

JAX-RS API

Custom Serialization

Built-in Serialization


JAX-RS Most Wanted

Filters Handlers

Validation

Asynchronous Processing

Hypermedia

Server Side Conneg

JSR 330

MVC Client API


• EG Formed in February 2011 –  Oracle Leads •  Marek Potociar / Santiago Pericas-Geertsen

–  Expert Group: •  Jan Algermissen, Florent Benoit (OW2), Sergey Beryozkin

(Talend), Adam Bien, Bill Burke (RedHat), Clinton Combs, Bill De Hora, Markus Karg, Sastri Malladi (Ebay), Julian Reschke, Guilherme Silveira, Dionysios Synodinos

• Early Draft published on Oct 21st, 2011

JSR 339: JAX-RS 2.0

Part II. Where we are going…


New in JAX-RS 2.0

Filters Handlers

Validation


Hypermedia

Server Side Conneg

JSR 330

MVC Client API

✔ ✔

✔

✔ ✔

✔ ✔

✗


Client API

Filters Handlers

Validation


Hypermedia

Server Side Conneg

JSR 330

Client API


• HTTP client libraries too low level •  Sharing features with JAX-RS server API

–  E.g., MBRs and MBWs

•  Supported by some JAX-RS 1.x implementations –  Need for a standard

Client API


Client API

Client Resource Target “atm”

Request Builder

Resource Target “{cardId}”

Resource Target “balance”

Resource Target “withdrawal”

Client Factory

Response

Invocation

Configuration Configuration Configuration


// Get instance of ClientClient client = ClientFactory.newClient();

// Get account balanceString bal = client.target("http://.../atm/{cardId}/balance") .pathParam("cardId", "111122223333") .queryParam("pin", "9876") .request("text/plain").get(String.class);

Client API


// Withdraw some moneyMoney mon = client.target("http://.../atm/{cardId}/withdrawal") .pathParam("cardId", "111122223333") .queryParam("pin", "9876") .request("application/json") .post(text("50.0"), Money.class);

Client API


Invocation inv1 = client.target("http://.../atm/{cardId}/balance")… .request(“text/plain”).buildGet();

Invocation inv2 = client.target("http://.../atm/{cardId}/withdraw")… .request("application/json") .buildPost(text("50.0"));

Client API


Collection<Invocation> invocations = Arrays.asList(inv1, inv2);

Collection<Response> responses = Collections.transform( invocations, new F<Invocation, Response>() { public Response apply(Invocation inv) { return inv.invoke(); } });

Client API


// Create client and register MyProvider1Client client = ClientFactory.newClient();client.configuration().register(MyProvider1.class);

// Create atm target; inherits MyProvider1Target atm = client.target("http://.../atm");// Register MyProvider2atm.configuration().register(MyProvider2.class);

// Create balance target; inherits MyProvider1, MyProvider2Target balance = atm.path(”{cardId}/balance");// Register MyProvider3balance.configuration().register(MyProvider3.class);

Client API


Filters & Handlers

Filters Handlers

Validation


Hypermedia

Server Side Conneg

JSR 330

Client API


• Customize JAX-RS request/response processing –  Use Cases: Logging, Compression, Security, Etc.

•  Shared by client and server APIs • Replace existing proprietary support

–  Provided by most JAX-RS 1.x implementations •  All using slightly different types or semantics

Filters & Handlers


• Non-wrapping filter chain –  Managed by the JAX-RS runtime –  Each filter decides to proceed or break the chain •  By returning FilterAction.NEXT or FilterAction.STOP

• Request Request –  RequestFilter interface •  Server-side specialty: PreMatchRequestFilter

• Response Response –  ResponseFilter interface

Filters & Handlers


@Providerclass LoggingFilter implements RequestFilter, ResponseFilter {

// RequestFilter implementation @Override public FilterAction preFilter(FilterContext ctx) throws IOException { logRequest(ctx.getRequest()); return FilterAction.NEXT; }

…

Filters & Handlers


…

// ResponseFilter implementation @Override public FilterAction postFilter(FilterContext ctx) throws IOException { logResponse(ctx.getResponse()); return FilterAction.NEXT; }

}

Filters & Handlers


• Wrapping handler (interceptor) chain –  Each handler decides to proceed or break chain •  By calling context.proceed()

• Read message handler –  ReadFromHandler interface

• Write message handler –  WriteToHandler interface

Filters & Handlers


@Providerclass GzipHandler implements ReadFromHandler {

@Override public Object readFrom(ReadFromHandlerContext context) throws IOException { if (gzipEncoded(context)) { InputStream old = context.getInputStream(); context.setInputStream(new GZIPInputStream(old)); } return context.proceed(); } }

Filters & Handlers


• Associating filters and handlers with resources • Declaring relative position in the chain

–  @BindingPriority(priority)

•  Same mechanism for filters and handlers

Filters & Handlers Bindings

Name Binding Global Binding

Static @NameBinding / @Qualifier ? DEFAULT

Dynamic DynamicBinding interface DynamicBinding interface


@NameBinding // or @Qualifier [email protected]({ElementType.TYPE, ElementType.METHOD})@Retention(value = RetentionPolicy.RUNTIME)public @interface Logged {}

@[email protected]@BindingPriority(USER)public class LoggingFilter implements RequestFilter, ResponseFilter { … }



@Path("/greet/{name}")@Produces("text/plain")public class MyResourceClass {

@Logged @GET public String hello(@PathParam("name") String name) { return "Hello " + name; }}



Validation

Filters Handlers

Validation


Hypermedia

Server Side Conneg

JSR 330

Client API


•  Services must validate data • Bean Validation already provides the mechanism

–  Integration into JAX-RS

•  Support for constraint annotations in: –  Fields and properties –  Parameters (including request entity) –  Methods (response entities) –  Resource classes

Validation


@Path("/")class MyResourceClass {

@POST @Consumes(MediaType.APPLICATION_FORM_URLENCODED) public void registerUser( @NotNull @FormParam("firstName") String firstName, @NotNull @FormParam("lastName") String lastName, @Email @FormParam("email") String email) { ... } }

Validation

Built-in

Custom


@Target({ METHOD, FIELD, PARAMETER })@Retention(RUNTIME)@Constraint(validatedBy = EmailValidator.class)public @interface Email { ... }

class EmailValidator implements ConstraintValidator<Email, String> { public void initialize(Email email) { … } public boolean isValid(String value, ConstraintValidatorContext context) { // Check 'value' is e-mail address … }}

Validation


@ValidationAclass User { ... }

@Path("/")class MyResourceClass { @POST @Consumes("application/xml") public void registerUser1(@Valid User u) { … }

@POST @Consumes("application/json") public void registerUser12(@ValidationB @Valid User u) { … } }

Validation


Async Processing

Filters Handlers

Validation


Hypermedia

Server Side Conneg

JSR 330

Client API


•  Server API support –  Off-load container threads •  Long-running operations

–  Efficient asynchronous event processing •  Suspend while waiting for an event •  Resume when event arrives

–  Leverage Servlet 3.x async support (if available)

• Client API support –  Asynchronous request invocation API •  Future<RESPONSE>, InvocationCallback<RESPONSE>

Async Processing


@Path("/async/longRunning")public class MyResource { @Context private ExecutionContext ctx;

@GET @Produces("text/plain") @Suspend public void longRunningOp() { Executors.newSingleThreadExecutor().submit( new Runnable() { public void run() { … ctx.resume("Hello async world!"); } }); }}

Async Processing


@Path("/async/longRunning")public class MyResource { @Context private ExecutionContext ctx;

@GET @Produces("text/plain") public void longRunningOp() { Executors.newSingleThreadExecutor().submit( new Runnable() { public void run() { … ctx.resume("Hello async world!"); } }); ctx.suspend(); // Suspend connection and return }}

Async Processing


// Build target URITarget target = client.target("http://.../balance”)…

// Start async call and register callbackFuture<?> handle = target.request().async().get( new InvocationCallback<String>() { public void complete(String balance) { … } public void failed(InvocationException e) { … } });

// After waiting for a while …if (!handle.isDone()) handle.cancel(true);

Async Processing


Hypermedia

Filters Handlers

Validation


Hypermedia

Server Side Conneg

JSR 330

Client API


• REST principles –  Identifiers and Links –  HATEOAS (Hypermedia As The Engine Of App State)

• Link types: –  Structural Links –  Transitional Links

Hypermedia


Link: <http://.../orders/1/ship>; rel=ship, <http://.../orders/1/cancel>; rel=cancel ...<order id="1"> <customer>http://.../customers/11</customer> <address>http://.../customers/11/address/1</address> <items> <item> <product>http://.../products/111</product> <quantity>2</quantity> </item> <items> ... </order>

Hypermedia

Transitional Links

Structural Links


• Transitional Links Only • Link and LinkBuilder classes

–  RFC 5988: Web Linking

•  Support for Link in ResponseBuilder • Create Target from Link in Client API

Hypermedia


// Producer API (server-side)Link self = Link.fromResourceMethod(MyResource.class, ”handleGet”) .build();Link update = Link .fromResourceMethod(MyResource.class, “handlePost”) .rel(”update”).build();

...

Response res = Response.ok(order) .link("http://.../orders/1/ship", "ship") .links(self, update) .build();

Hypermedia


Response order = client.target(…).request("application/xml").get();

// Consumer API (client-side)if (order.getLink(“ship”) != null) { Response shippedOrder = client.target(order.getLink("ship")) .request("application/xml").post(…); … }

Hypermedia


Other Topics

Filters Handlers

Validation


Hypermedia

Server Side Conneg

JSR 330

Client API …


GET http://.../widgets2Accept: text/*; q=1…

Path("widgets2")public class WidgetsResource2 { @GET @Produces("text/plain", "text/html") public Widgets getWidget() {...}}

Server Side Conneg


GET http://.../widgets2Accept: text/*; q=1…

Path("widgets2")public class WidgetsResource2 { @GET @Produces("text/plain; qs=0.5", "text/html; qs=0.75") public Widgets getWidget() {...}}

Server Side Conneg


• Better integration with JSR 330 –  Support @Inject and @Qualifier –  @Qualifier as a replacement for @NamedBinding ? –  Provider vs. ContextResolver

•  Support for MVC ? • High-level client API ?

Other Topics

Thank You!

http://jcp.org/en/jsr/detail?id=339 (JSR) http://java.net/projects/jax-rs-spec (Project)

[email protected] (Users alias)


Filters & Handlers

Req/Resp

Filter Resource Matching Filter … Filter Filter …

Filter Filter … Filter

MBR/W

Handler

Handler

MBR/W

Handler

Handler

MBR/W

Handler

Handler

Request

Response

JAX-RS 2.0: RESTful Java on Steroids - Coding the Webmarek.potociar.net/wp-content/uploads/Devoxx-2011-JAXRS... · 2011-11-17 · ... RESTful Java on Steroids What’s in JSR-339?

Text of JAX-RS 2.0: RESTful Java on Steroids - Coding the...

RESTful Java

Anabolic Steroids Testosterone 400 Anabolic Steroids For Sale

Security Testing For RESTful Applications - WordPress.com · 2013-04-06 · About RESTful Web Services • RESTful WS in the Wild • Security of RESTful WS • Pen-testing RESTful

Restful webservices

JAX-RS: Java API for RESTful Web Servicesdownload.oracle.com/otn-pub/jcp/jaxrs-1.0-pr-oth-JSpec/...JAX-RS: Java API for RESTful Web Services Public Review Draft April 18, 2008 Editors:

Androgens and Anabolic Steroids - Commercial · Androgens/Anabolic Steroids

GIDS 2012: JAX-RS 2.0: RESTful Java on Steroids

Steroids Steroids Some questions we need answers to Some questions we need answers to What are steroids? What are steroids? Who takes steroids Who takes

Restful imaginarium

JAX-RS 2.0: RESTful Web services on steroids at Geecon 2012

JAX-RS: Java API for RESTful Web Services - Oracledownload.oracle.com/otn-pub/jcp/jaxrs-2_1-final-eval-spec/jaxrs-2... · JAX-RS: Java™ API for RESTful Web Services Version 2.1

Steroids: the Good, the BAD and the Ugly · OUTLINE • History of steroids in asthma • Steroids: Types, preparations, routes of administration • “The Good”: Benefits of steroids

Chandrasekharan, J Steroids Hormon Sci 2013, S12 Steroids ... · Chandrasekharan, J Steroids Hormon Sci 2013, S12 ... J Steroids Hormon Sci Steroid Hormone Metabolism ISSN: 2157-7536

Dialogic® PowerMedia™ XMS RESTful API/media/manuals/xms/XMS_RESTfulAPIDe… · RESTful API Description PowerMedia XMS RESTful API uses a Representational State Transfer (RESTful)

JAX-RS 2.0: RESTful Web services on steroids

The multiple roles of steroids and anabolic steroids and

JugTAAS ReSTful

The Steroids - Northgateusing anabolic steroids. • Shotgunning—taking steroids on an inconsistent basis. • Stacking—using a combination of two or more anabolic steroids. Before

RESTFul APIs

RESTful Web Services [email protected]. What is RESTful?

restful development

JAX-RS: Java API for RESTful Web Servicesdownload.oracle.com/otn-pub/jcp/jaxrs-2_0-pr-spec/339...JAX-RS: Java API for RESTful Web Services Version 2.0 Public Review September 26, 2012

JAX-RS: Java API for RESTful Web Servicesdownload.oracle.com/otn-pub/jcp/jaxrs-2_0-fr-eval-spec/jsr339-jax... · JAX-RS: Java™ API for RESTful Web Services Version 2.0 Final Release

Today's Top "RESTful" Services and Why They Are Not RESTful

(ATS4-DEV04) Protocols as RESTful Services and RESTful URL Routing

Building RESTful - NetBeansBuilding RESTful Web Services in NetBeans 6.0 RESTful component palette. • Generation of JavaScript client stubs from RESTful web services for building

RESTful web

Restful Patterns

RESTful Server Configuration with iDRAC RESTful API

Documents

JAX-RS 2.0: RESTful Java on Steroids - Coding the Webmarek.potociar.net/wp-content/uploads/Devoxx-2011-JAXRS... · 2011-11-17 · ... RESTful Java on Steroids What’s in JSR-339?

Text of JAX-RS 2.0: RESTful Java on Steroids - Coding the...