JAX-RS 2.0 REST Client Features by Example

December 30th, 2013 by

JAX-RS 2.0 aka JSR 339 not also specifies the API to build up a RESTful webservice but also enhances the client side API to easen up the process of writing a client for a REST service.

In the following tutorial we’re building up a client for a ready-to-play REST service and explore the different new options e.g. how to handle requests in a synchronous or asynchronous way, how to add callback handlers for a request, how to specify invocation targets to build up requests for a later execution or how to filter the client-server communication using client request filters and client response filters.


Ready to Play

For the of you who would like to reproduce the following client examples, I’ve added a full RESTful webservice runnable via Maven and an embedded application server or a standalone application server instance (war-file available as download below).

To download the project and startup the REST server you may use the following command chain (downloading dependencies might take a while..):

git clone https://bitbucket.org/hascode/jaxrs2-client-tutorial.git && cd jaxrs2-client-tutorial && make rest-server

Now following some details regarding the REST service and the entity we’re using in the following examples – please feel free to skip to the client examples directly if you’re not interested in those details!

REST Service

This is the REST service used to run the following client examples. The injected BookRepository is simply an @Singleton, @Startup marked session bean that emulates storing/fetching book entities.

The service exports methods to save a book, delete a book, find a book by its identifier and fetch all available books.

When a book is persisted, its id is generated and set and every method in the REST-service that returns an entity or a list of entities returns JSON data.

package com.hascode.tutorial.jaxrs.server;
import java.util.List;
import javax.ejb.EJB;
import javax.ejb.Stateless;
import javax.ws.rs.Consumes;
import javax.ws.rs.DELETE;
import javax.ws.rs.GET;
import javax.ws.rs.POST;
import javax.ws.rs.Path;
import javax.ws.rs.PathParam;
import javax.ws.rs.Produces;
import javax.ws.rs.core.GenericEntity;
import javax.ws.rs.core.MediaType;
import javax.ws.rs.core.Response;
import com.hascode.tutorial.jaxrs.entity.Book;
public class BookStoreService {
	private BookRepository bookRepository;
	public Response saveBook(final Book book) {
		Book bookPersisted = bookRepository.saveBook(book);
		return Response.ok(bookPersisted).build();
	public Response deleteBook(final @PathParam("id") String id) {
		return Response.ok().build();
	public Response getAll() {
		List<Book> books = bookRepository.getAll();
		GenericEntity<List<Book>> bookWrapper = new GenericEntity<List<Book>>(
				books) {
		return Response.ok(bookWrapper).build();
	public Response getById(final @PathParam("id") String id) {
		Book book = bookRepository.getById(id);
		return Response.ok(book).build();

An additional note: I’ve modified the application server to use Jackson as JSON provider using the service discovery mechanism.

Book Entity

The following bean is used throughout the tutorial .. a book .. has an id, a title, a price and a published-date.

package com.hascode.tutorial.jaxrs.entity;
import java.io.Serializable;
import java.math.BigDecimal;
import java.util.Calendar;
public class Book implements Serializable {
	private static final long serialVersionUID = 1L;
	private String id;
	private String title;
	private BigDecimal price;
	private Calendar published;
	// getter+setter..

Creating and Binding a Client

We’re able to create a rest client and to bind it to a specific target URL and dedicated, parameterized paths using the following steps:

  • Obtain a client reference using the ClientBuilder: Client client = ClientBuilder.newClient();
  • Bind the target to the REST service’s URL using the target() method: client.target(“http://localhost:8080/myrestservice”);
  • Handle dynamic URL path parameters using path() and resolveTemplate(): client.target(..).path(“{id}”).resolveTemplate(“id”, someId);
  • Use the request() method to start building up the request followed by one of the methods e.g. post(), get(): client.target(..).request().get();
  • Each steps offers a variety of possible parameters and configuration options, I’ll be covering some of them like asynchronous requests, callback handler and registering filters and feature classes later.

Now let’s move on to some more concrete examples …

Client Examples

As I have put the client examples in test cases running with jUnit and Hamcrest, the following setup code is used for every following test case but ommitted in the article  to keep it short.

private static final String REST_SERVICE_URL = "http://localhost:8080/tutorial/rs/book";
private static final String TITLE = "One big book";
private static final BigDecimal PRICE = new BigDecimal("20.0");
private static final GregorianCalendar PUBLISHED = new GregorianCalendar(
		2013, 12, 24);
Client client = ClientBuilder.newClient().register(JacksonFeature.class);
public Book mockBook() {
	Book book = new Book();
	return book;

The only notable thing here is that I’ve added the Jackson framework to the client runtime and that we may obtain a client instance using the javax.ws.rs.client.ClientBuilder.

Maven Coordinates

I’ve used the following dependencies for the examples below to run:


Basic Operations

In the following example we’re first sending a post request with a book entity serialized to the JSON format to save the book.

Afterwards we’re using the client’s path() and resolveTemplate() methods to match the server’s specification here to receive a single book entity by its identifier.

In the third step we receive a list of all available books and finally we’re deleting the book.

public void crudExample() {
	// 1. Save a new book
	Book book = mockBook();
	Book bookPersisted = client
			.post(Entity.entity(book, MediaType.APPLICATION_JSON),
	String bookId = bookPersisted.getId();
	assertThat(bookId, notNullValue());
	// 2. Fetch book by id
	Book book2 = client.target(REST_SERVICE_URL).path("/{bookId}")
			.resolveTemplate("bookId", bookId).request().get(Book.class);
	assertThat(book2, notNullValue());
	assertThat(book2.getTitle(), equalTo(TITLE));
	assertThat(book2.getPrice(), equalTo(PRICE));
	assertThat(book2.getPublished().getTime(), equalTo(PUBLISHED.getTime()));
	// 3. Fetch all books
	GenericType<List<Book>> bookType = new GenericType<List<Book>>() {
	}; // generic type to wrap a generic list of books
	List<Book> books = client.target(REST_SERVICE_URL).request()
	assertThat(books.size(), equalTo(1));
	// 4. Delete a book
			.resolveTemplate("bookId", bookId).request().delete();
	List<Book> books2 = client.target(REST_SERVICE_URL).request()
	assertThat(books2.isEmpty(), equalTo(true));

Asynchronous Processing

Adding a simple async() to the request builder enables us to process the requests asynchronous using Java’s Future API and their possibilities.

In the following example we’re adding a book in the first client request, delete it afterwards and fetch a list of available books afterwards.

public void asyncExample() throws Exception {
	Book book = mockBook();
	Future<Book> fb = client
			.post(Entity.entity(book, MediaType.APPLICATION_JSON),
	Book bookPersisted = fb.get();
	String bookId = bookPersisted.getId();
	assertThat(bookId, notNullValue());
			.resolveTemplate("bookId", bookId).request().async().delete()
	Future<List<Book>> bookRequest = client.target(REST_SERVICE_URL)
			.request().async().get(new GenericType<List<Book>>() {
	List<Book> books2 = bookRequest.get();
	assertThat(books2.isEmpty(), equalTo(true));

Invocation Callback

Another way to interfere with the server response during a client communication is to add an InvocationCallback handler to a request.

In the following example with the enormous indent the callback handler added to the requests prints information about the persisted book or – in the case of an error – a stacktrace.

public void invocationCallbackExample() throws Exception {
	Book book = mockBook();
			.post(Entity.entity(book, MediaType.APPLICATION_JSON),
					new InvocationCallback<Book>() {
						public void completed(final Book bookPersisted) {
							System.out.println("book saved: "
									+ bookPersisted);
						public void failed(final Throwable throwable) {
			.get(new InvocationCallback<List<Book>>() {
				public void completed(final List<Book> books) {
					System.out.println(books.size() + " books received");
					assertThat(books.size(), greaterThanOrEqualTo(1));
				public void failed(final Throwable throwable) {

Delayed Invocations / Request Building

The javax.ws.rs.client.Invocation class allows us to build up a request for later use – either synchronous or asynchronous.

In the following example we’re building up two invocations for later use – one to persist a book and the other to fetch all available books and we’re using both afterwards to persist a book and fetch all available books.

Use invoke() for a synchronous request and submit() for an asynchronous request – either methods may return either a javax.ws.rs.core.Response or the desired entity if you give the entity’s class as method parameter.

public void requestPreparationExample() throws Exception {
	Book book = mockBook();
	Invocation saveBook = client.target(REST_SERVICE_URL).request()
			.buildPost(Entity.entity(book, MediaType.APPLICATION_JSON));
	Invocation listBooks = client.target(REST_SERVICE_URL).request()
	Response response = saveBook.invoke();
	Book b1 = response.readEntity(Book.class);
	// alternative: Book b1 = saveBook.invoke(Book.class);
	assertThat(b1.getId(), notNullValue());
	// async invocation
	Future<List<Book>> b = listBooks.submit(new GenericType<List<Book>>() {
	List<Book> books = b.get();
	assertThat(books.size(), greaterThanOrEqualTo(2));

Client Request Filter

JAX-RS allows us to intercept outgoing requests between client and server using a request filter.

We simply need to write an implementation of the interface javax.ws.rs.client.ClientRequestFilter and when creating the client, register this class using the client’s register() method.

The javax.ws.rs.client.ClientRequestContext object grants access to the contextual information we need here.

This is our client request filters that modifies the price of book entities for all outgoing requests with a POST operation and an entity present (non-ideal production use-case ;) ) by adjusting it to the tax rate.

package com.hascode.tutorial.client;
import java.io.IOException;
import java.math.BigDecimal;
import javax.ws.rs.client.ClientRequestContext;
import javax.ws.rs.client.ClientRequestFilter;
import com.hascode.tutorial.jaxrs.entity.Book;
public class TaxAdjustmentFilter implements ClientRequestFilter {
	public static final BigDecimal TAX_RATE = new BigDecimal("2.5");
	public void filter(final ClientRequestContext rc) throws IOException {
		String method = rc.getMethod();
		if ("POST".equals(method) && rc.hasEntity()) {
			Book book = (Book) rc.getEntity();
			BigDecimal priceWithTaxes = book.getPrice().multiply(TAX_RATE);

Now in our test case we simply need to register the filter class for the client and when persisting a book we’re able to see that the price has been updated according to the tax rate.

public void clientRequestFilterExample() {
	Book book = mockBook();
	Client client = ClientBuilder.newClient()
	Book bookPersisted = client
			.post(Entity.entity(book, MediaType.APPLICATION_JSON),
	String bookId = bookPersisted.getId();
	assertThat(bookId, notNullValue());

Client Response Filter

To gain control over the server’s response we’ve got a similar solution: the client response filter.

Again we simply need to implement javax.ws.rs.client.ClientResponseFilter and we’re able to modify or introspect the server’s response.

The following response filter simply prints out some HTTP headers to STDOUT:

package com.hascode.tutorial.client;
import java.io.IOException;
import java.util.List;
import java.util.Map.Entry;
import javax.ws.rs.client.ClientRequestContext;
import javax.ws.rs.client.ClientResponseContext;
import javax.ws.rs.client.ClientResponseFilter;
public class ClientResponseLoggingFilter implements ClientResponseFilter {
	public void filter(final ClientRequestContext reqCtx,
			final ClientResponseContext resCtx) throws IOException {
		System.out.println("status: " + resCtx.getStatus());
		System.out.println("date: " + resCtx.getDate());
		System.out.println("last-modified: " + resCtx.getLastModified());
		System.out.println("location: " + resCtx.getLocation());
		for (Entry<String, List<String>> header : resCtx.getHeaders()
				.entrySet()) {
			System.out.print("\t" + header.getKey() + " :");
			for (String value : header.getValue()) {
				System.out.print(value + ", ");
		System.out.println("media-type: " + resCtx.getMediaType().getType());

Again we simply need to register our filter class for the client used:

public void clientResponseFilterExample() {
	Book book = mockBook();
	Client client = ClientBuilder.newClient()
			.post(Entity.entity(book, MediaType.APPLICATION_JSON),

Running the post request to the embedded GlassFish yields the following result:

status: 200
date: Sat Dec 28 18:50:16 CET 2013
last-modified: null
location: null
 Date :Sat, 28 Dec 2013 17:50:16 GMT,
 Transfer-Encoding :chunked,
 Content-Type :application/json,
 Server :GlassFish Server Open Source Edition 3.1,
 X-Powered-By :Servlet/3.0 JSP/2.2 (GlassFish Server Open Source Edition 3.1 Java/Oracle Corporation/1.7),
media-type: application

Tutorial Sources

Please feel free to download the tutorial sources from my Bitbucket repository, fork it there or clone it using Git:

git clone https://bitbucket.org/hascode/jaxrs2-client-tutorial.git

REST-Server Download as war-File

If you want to use your own application server to run the RESTful webservice you may download the war-file from my repository’s download section on Bitbucket.org:


JAX-RS 1.0 and JAX-B

If you’re interested in examples for an older version of the specification, please feel free to have a look at my article “Creating a REST Client Step-by-Step using JAX-RS, JAX-B and Jersey“.


Additional REST articles of mine

Please feel free to have a look at these tutorials of mine covering different aspects of handling or creating RESTful webservices.

Article Updates

  • 2015-08-06: Links to other REST articles of mine added.
  • 2015-10-22: Link list updated.

Tags: , , , , , , , , , , , , ,

13 Responses to “JAX-RS 2.0 REST Client Features by Example”

  1. Brinal Says:

    Awesome tutorial. Great help :)

  2. Regnarock Says:

    Thanks a lot for that article ! Helped me a lot.
    Keep on the good work =).

  3. micha kops Says:

    Thanks! You’re welcome :)

  4. Alexandre Says:


    I’m trying to deploy this application into Glassfish 4.0, Using Eclipse Luna. But I got a couple of errors belong: Could you help me?

    cannot Deploy rest-server
    deploy is failing=Error occurred during deployment: Exception while loading the app : CDI deployment failure:WELD-001408 Unsatisfied dependencies for type [Ref] with qualifiers [@Default] at injection point [[BackedAnnotatedParameter] Parameter 1 of [BackedAnnotatedConstructor] @Inject org.glassfish.jersey.server.internal.routing.UriRoutingContext(Ref, ProcessingProviders)]. Please see server.log for more details.

    2014-12-03T15:10:40.260-0200|Grave: Exception while loading the app : CDI deployment failure:WELD-001408 Unsatisfied dependencies for type [Ref] with qualifiers [@Default] at injection point [[BackedAnnotatedParameter] Parameter 1 of [BackedAnnotatedConstructor] @Inject org.glassfish.jersey.server.internal.routing.UriRoutingContext(Ref, ProcessingProviders)]
    org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Ref] with qualifiers [@Default] at injection point [[BackedAnnotatedParameter] Parameter 1 of [BackedAnnotatedConstructor] @Inject org.glassfish.jersey.server.internal.routing.UriRoutingContext(Ref, ProcessingProviders)]
    at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:403)
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:325)
    at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:177)
    at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:208)
    at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:519)
    at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:505)
    at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:480)
    at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:536)
    at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:216)
    at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:131)
    at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:328)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:493)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:219)
    at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:491)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:527)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:523)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAs(Subject.java:360)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:522)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:546)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1423)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1500(CommandRunnerImpl.java:108)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1762)
    at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1674)
    at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:534)
    at com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:224)
    at org.glassfish.grizzly.http.server.StaticHttpHandler.service(StaticHttpHandler.java:297)
    at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:246)
    at org.glassfish.grizzly.http.server.HttpHandler.runService(HttpHandler.java:191)
    at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:168)
    at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:189)
    at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)
    at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:288)
    at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:206)
    at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:136)
    at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:114)
    at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:77)
    at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:838)
    at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:113)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:115)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55)
    at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:135)
    at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:564)
    at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:544)
    at java.lang.Thread.run(Thread.java:745)

  5. Attila Says:

    thanks for this post, very well written and helpfull

  6. Intae Kim Says:

    Great article, very compact compared to official guide, and useful unit test case.

  7. micha kops Says:

    Thanks, you’re welcome! :)

  8. francis Says:

    Can you write a post real world scenarios on why we should use Asynchronous Processing or Invocation Callback?

    It looks like they are doing the same thing but I have a feeling that they fill in a specific need.

  9. YARA Says:

    how can i create and insert a value from (jax-rs)webservice into sql without using jersey

  10. micha kops Says:

    Hi Yara,

    could you provide some more details about your problem please? Do you want to skip mapping the reponse to an entity? Or do you want to use another JAX-RS implementation instead of Jersey?

  11. Vinícius Bueno Says:

    Great job, thanks for help, very good tutorial!

  12. micha kops Says:

    Thanks! You’re welcome! :)

  13. Anne Li Says:

    Thanks very much! Very good tutorial!