Joe Murray Joe Murray - 3 months ago 13
JSON Question

MessageBodyWriter not found vogella tutorial

I am attempting to recreate the most excellent vogella tutorial for create REST with java, JAX-RS and Jersey.

I'm using eclipse Kepler with Java-EE perspective, tomcat 7.0.

I have create the Todo class, the TodoResource class with the appropriate annotations and deployed on tomcat 7. I have imported the jaxrs-ri libs into the WEB-INF/lib folder as instructed.

Todo class:

package com.vogella.jersey.jaxb.model;

import javax.xml.bind.annotation.XmlRootElement;

public class Todo {
private String summary;
private String description;
public String getSummary() {
return summary;
public void setSummary(String summary) {
this.summary = summary;
public String getDescription() {
return description;
public void setDescription(String description) {
this.description = description;


TodoResource with annotations:

package com.vogella.jersey.jaxb.model;


public class TodoResource {
// This method is called if XMLis request
@Produces({ MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON })
public Todo getXML() {
Todo todo = new Todo();
todo.setSummary("This is my first todo");
todo.setDescription("This is my first todo");
return todo;

// This can be used to test the integration with the browser
@Produces({ MediaType.TEXT_XML })
public Todo getHTML() {
Todo todo = new Todo();
todo.setSummary("This is my first Todo");
todo.setDescription("This is my first Todo");
return todo;



<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="" xmlns="" xsi:schemaLocation="" id="WebApp_ID" version="3.0">
<servlet-name>Jersey REST Service</servlet-name>
<servlet-name>Jersey REST Service</servlet-name>

I have also created the client as instructed.

package com.vogella.jersey.first.client;


import org.glassfish.jersey.client.ClientConfig;
import org.glassfish.jersey.client.ClientResponse;
import org.glassfish.jersey.message.internal.MediaTypes;

public class Test {

public static void main(String[] args) {

ClientConfig config = new ClientConfig();

Client client = ClientBuilder.newClient(config);

WebTarget target =;


.accept(MediaType.APPLICATION_XML ).get(Response.class)



.accept(MediaType.APPLICATION_JSON ).get(Response.class)



private static URI getBaseURI() {

return UriBuilder.fromUri("http://localhost:8080/com.vogella.jersey.jaxb").build();


Everything works perfectly for the MediaType.APPLICATION_XML - the server returns:

InboundJaxrsResponse{ClientResponse{method=GET, uri=http://localhost:8080/com.vogella.jersey.jaxb/rest/todo, status=200, reason=OK}}

However, for the MediaType APPLICATION_JSON - which is what I actually need, I get an error:

InboundJaxrsResponse{ClientResponse{method=GET, uri=http://localhost:8080/com.vogella.jersey.jaxb/rest/todo, status=500, reason=Internal Server Error}}

Tomcat clearly shows me the problem - it seems to me it doesn't know how to return a JSON response -

Nov 02, 2014 11:59:19 AM org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor aroundWriteTo
SEVERE: MessageBodyWriter not found for media type=application/json, type=class com.vogella.jersey.jaxb.model.Todo, genericType=class com.vogella.jersey.jaxb.model.Todo.

My understanding is that the jaxrs-ri 2.13 bundle includes everything required including dependencies to let me do this - and that I don't need to add any kind of JSON provider. I have done so anyway, I have tried adding gson for example, I have downloaded the moxy jars and attempting to add them to my WEB-INF/lib folder and deploy - all to no avail. I don't know if I'm completely out in the weeds, or if I'm missing something simple?


My understanding is that the jaxrs-ri 2.13 bundle includes everything required including dependencies to let me do this - and that I don't need to add any kind of JSON provider.

That's actually incorrect. As stated at the Jersey User Guide 8.1. JSON

Jersey JSON support comes as a set of extension modules where each of these modules contains an implementation of a Feature that needs to be registered into your Configurable instance (client/server). There are multiple frameworks that provide support for JSON processing and/or JSON-to-Java binding. The modules listed below provide support for JSON representations by integrating the individual JSON frameworks into Jersey. At present, Jersey integrates with the following modules to provide JSON support:

  • MOXy - JSON binding support via MOXy is a default and preferred way of supporting JSON binding in your Jersey applications since Jersey 2.0. When JSON MOXy module is on the class-path, Jersey will automatically discover the module and seamlessly enable JSON binding support via MOXy in your applications. (See Section 4.3, “Auto-Discoverable Features”.)

  • Among a few others

So the main Jersey download doesn't come with these extra modules. We need to obtain them separately. That being said, the easiest way to get the required jersey-media-moxy is through Maven.


If you're not using Maven (which looking through the tutorial, it doesn't), you're going to have to do some searching for the dependencies. The jersey-media-moxy artifact has 16 dependencies, but Fortunately, most are contained within the Jersey distribution. So after filtering out what was already included in the Jersey distro, these are the remaining jars you will have to find on your own (I just created a User Library to test out)

enter image description here

Adding these dependencies will get the example up and running. Tested and works as expected after adding these.

Now you have Eclipse, which I assume came with the Maven (m2e) plugin. So maybe the easiest way to get these dependencies is to create a new Maven project, and add the dependency shown above. After you build the project, maven should download all the extra dependencies into your local Maven Repo. Just grab them from there for your main project.

Other Resources/Notes

  • Jersey User Guide
  • I would download the Jersey Example package, which is more up to date then the tutorial you are using.
  • If you don't know Maven, I would strongly suggest learning at least the basic of dependency management, and let the build framework grab all the dependencies for you. Also all the examples in the examples package uses Maven, so it would help to know the basics.