Java API for RESTful Web Services 2.1 Released

| by Amit K Gupta Follow 5 Followers on Aug 26, 2017. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

JAX-RS 2.1 Java API for RESTful Web Services  was released this week. According to Santiago Pericas-Geertsen, principal member of technical staff at Oracle and specifications lead for the JSR, JAX-RS 2.1 will include support for server-sent events, JSON-B and improved support for JSON-P. The API will also have a reactive extension to the client API, with built-in support for Java 8 CompletionStage and an extension point for other reactive APIs like RxJava.

According to the JAX-RS 2.1 specs, the goals for the release include annotations for POJOs, flexible API with high-level support for common HTTP usage patterns and applications including WebDAV and the Atom Publishing Protocol. The API will support various HTTP entity body content types, servlet containers and JAX-WS Providers. The API will support Java EE features and components within a web resource class.

InfoQ spoke to Pericas-Geertsen, who elaborated on server-sent events:

Server-sent-event (SSE) resources inject a special type called SseEventSink and produce text/event-stream. SSE clients use a SseEventSource to read events from a connection.

This mechanism uses long-lived connections and broadcasting, which provides improved performance over polling and resource-intensive, short-lived connections.

The following block illustrates the usage of SSE.


public void getMessageQueue(@Context Sse sse, @Context SseEventSink eventSink) {
    // Resource method is invoked when a client subscribes to an event stream.
    // That implies that sending events will most likely happen from different
    // context - thread / event handler / etc, so common implementation of the
    // resource method will store the eventSink instance and the application 
    // logic will retrieve it when an event should be emitted to the client.
    // sending events:


WebTarget target = ClientBuilder.newClient().target("server-sent-events");

SseEventSource eventSource =;

// EventSource#register(Consumer<InboundSseEvent>)
// Registered event handler will print the received message.

// Subscribe to the event stream.;

Pericas-Geertsen added:

  • JAX-RS 2.1 is fully backward compatible with previous releases.

  • The new features integrate very well with the existing JAX-RS concepts. For example, simply injecting a method call in a client invocation can switch processing from synchronous to reactive.

  • SSE relies on streaming HTTP-based connections so it is a natural extension to the existing APIs.

Since the API will use annotations and lambda expressions extensively, it will support applications developed in Java SE 8 or later.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you