JBoss.orgCommunity Documentation

Chapter 24. JSON Support via Jackson

RESTEasy supports integration with the Jackson project. For more on Jackson 2, see https://github.com/FasterXML/jackson-databind/wiki. Besides having Jakarta XML Binding like APIs, it has a JavaBean based model, described at https://github.com/FasterXML/jackson-databind/wiki/Databind-annotations, which allows the marshalling of Java objects to and from JSON. RESTEasy integrates with the JavaBean model. While Jackson does come with its own Jakarta RESTful Web Services integration, RESTEasy expanded it a little, as described below.

24.1. Using Jackson 2 Outside of WildFly

If deploying RESTEasy outside WildFly, add the RESTEasy Jackson provider to the pom.xml:


24.2. Jakarta XML Binding Annotations

In Jackson 2.13+ com.fasterxml.jackson.module.jakarta.xmlbind.JakartaXmlBindAnnotationModule must be registered in order to use XML binding annotations for Jackson to marshall/unmarshall them in JSON. To do this, com.fasterxml.jackson.databind.ObjectMapper must be provided via an implementation of jakarta.ws.rs.ext.ContextResolver.

An example jakarta.ws.rs.ext.ContextResolver:

public class ObjectMapperProvider implements ContextResolver<ObjectMapper> {
    static final JsonMapper MAPPER = JsonMapper.builder()
            .addModule(new JakartaXmlBindAnnotationModule())

    public ObjectMapper getContext(final Class<?> type) {
        return MAPPER;

24.3. Additional RESTEasy Specifics

RESTEasy added support for "application/*+json". Jackson supports "application/json" and "text/json" as valid media types. This allows the creation of json-based media types and still lets Jackson perform the marshalling. For example:

public class MyService {

    public Customer[] getCustomers() {}

24.4. JSONP Support

RESTEasy supports JSONP. It can be enabled by adding provider org.jboss.resteasy.plugins.providers.jackson.Jackson2JsonpInterceptor to the deployment. Jackson and JSONP can be used together. If the media type of the response is json and a callback query parameter is given, the response will be a javascript snippet with a method call of the method defined by the callback parameter. For example:

GET /resources/stuff?callback=processStuffResponse

will produce this response:

processStuffResponse(<nomal JSON body>)

This supports the default behavior of jQuery. To enable Jackson2JsonpInterceptor in WildFly, annotations must be imported from the org.jboss.resteasy.resteasy-jackson2-provider module. To do that a jboss-deployment-structure.xml file must be added to the application's WAR:

      <module name="org.jboss.resteasy.resteasy-jackson2-provider" annotations="true"/>

The name of the callback parameter can be changed by setting the callbackQueryParameter property.

Jackson2JsonpInterceptor can wrap the response into a try-catch block:

try{processStuffResponse(<normal JSON body>)}catch(e){}

This feature can be enabled by setting the resteasy.jsonp.silent property to true

Note. Because JSONP can be used in Cross Site Scripting Inclusion (XSSI) attacks, Jackson2JsonpInterceptor is disabled by default. Two steps are necessary to enable it:

  1. As noted above, Jackson2JsonpInterceptor must be included in the deployment. For example, a service file META-INF/services/jakarta.ws.rs.ext.Providers with the line
    may be included on the classpath
  2. Parameter "resteasy.jsonp.enable" must be set to "true". [See Section 3.4, “Configuration” for more information about application configuration.]

24.5. Jackson JSON Decorator

If using the Jackson 2 provider, RESTEasy has provided a pretty-printing annotation similar with the one in Jakarta XML Binding provider:


Here is an example:

public Product getFormattedProduct()
    return new Product(333, "robot");

As the example shown above, the @Formatted annotation will enable the underlying Jackson option "SerializationFeature.INDENT_OUTPUT".

24.6. JSON Filter Support

Jackson2 provides annotation, JsonFilter. @JsonFilter is used to apply filtering during serialization/de-serialization for example which properties are to be used or not. Here is an example which defines mapping from "nameFilter" to filter instances and filter bean properties when serialized to json format:

public class Jackson2Product {
    protected String name;
    protected int id;
    public Jackson2Product() {
    public Jackson2Product(final int id, final String name) {
        this.id = id;
        this.name = name;
    public String getName() {
        return name;
    public void setName(String name) {
        this.name = name;
    public int getId() {
        return id;
    public void setId(int id) {
        this.id = id;

@JsonFilter annotates a resource class to filter out some property not to be serialized in the json response. To map the filter id and instance we need to create another jackson class to add the id and filter instance map:

public class ObjectFilterModifier extends ObjectWriterModifier {
	public ObjectFilterModifier() {
	public ObjectWriter modify(EndpointConfigBase<?> endpoint,
			MultivaluedMap<String, Object> httpHeaders, Object valueToWrite,
			ObjectWriter w, JsonGenerator jg) throws IOException {

		FilterProvider filterProvider = new SimpleFilterProvider().addFilter(
		return w.with(filterProvider);


Here the method modify() takes care of filtering all properties except "name" property before a write. To make this work, the mapping information must be accessible to RESTEasy. This can be made available through a WriterInterceptor that uses Jackson's ObjectWriterInjector:

public class JsonFilterWriteInterceptor implements WriterInterceptor{

	private ObjectFilterModifier modifier = new ObjectFilterModifier();
	public void aroundWriteTo(WriterInterceptorContext context)
			throws IOException, WebApplicationException {
		//set a threadlocal modifier


Alternatively, Jackson's documentation suggest doing the same in a servlet filter; that however potentially leads to issues in RESTEasy. The ObjectFilterModifier is stored using a ThreadLocal object and there's no guarantee the same thread serving the servlet filter will be running the resource endpoint execution. For the servlet filter scenario, RESTEasy offers its own injector that relies on the current thread context classloader for carrying the specified modifier:

public class ObjectWriterModifierFilter implements Filter {
	private static ObjectFilterModifier modifier = new ObjectFilterModifier();

	public void init(FilterConfig filterConfig) throws ServletException {

	public void doFilter(ServletRequest request, ServletResponse response,
			FilterChain chain) throws IOException, ServletException {
		ResteasyObjectWriterInjector.set(Thread.currentThread().getContextClassLoader(), modifier);
		chain.doFilter(request, response);

	public void destroy() {


24.7. Polymorphic Typing deserialization

Due to numerous CVEs for a specific kind of Polymorphic Deserialization (see details in FasterXML Jackson documentation), starting from Jackson 2.10 users have a means to allow only specified classes to be deserialized. RESTEasy enables this feature by default. It allows controlling the content of the whitelist of allowed classes/packages.

Table 24.1. 
Property Description  
resteasy.jackson.deserialization.whitelist.allowIfBaseType.prefix Method for appending a matcher that will allow all subtypes in cases where nominal base type's class name starts with specific prefix. "*" can be used for allowing any class.  
resteasy.jackson.deserialization.whitelist.allowIfSubType.prefix Method for appending a matcher that will allow specific subtype (regardless of declared base type) in cases where subclass name starts with specified prefix. "*" can be used for allowing any class.