A lot of times JSON returned by your REST API grows to incredibly big structures and data sizes due to business logic complexity that is added over time. Then there are API methods returning a list of objects which can be huge in size. If you serve multiple clients, each one can have different demands on what is and is not needed from that data so backend can't decide on it's own what to prune and what to keep. Ideally, backend would always return full JSON by default but allow clients to specify exactly what they want and have backend adjust the response accordingly. We can achieve this using the power of Jackson library.
Goal:
– allow REST API clients to decide on their own which parts of JSON to receive (full JSON filtering)
Resources for this tutorial:
– Microprofile or JakartaEE platform (JAX-RS)
– Jackson library
– Java classes (lib) representing your API responses which are serialized to JSON
– some custom code to bring things together
The lib module
First lets define a few classes which represent our JSON responses.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 |
public class Car { private Engine engine; private List<Wheel> wheels; private String brand; //Getters and setters.. } public class Wheel { private BigDecimal pressure; //Getters and setters.. } public class Engine { private int numOfCylinders; private int hp; //Getters and setters.. } |
Our lib serialized to JSON would look something like this:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
{ "engine": { "numOfCylinders": 4, "hp": 180 }, "wheels": [ { "pressure": 30.2 }, { "pressure": 30.1 }, { "pressure": 30.0 }, { "pressure": 30.3 } ], "brand": "Jugular" } |
Let's say one of our clients only needs the engine horse power and brand information. We want to be able to specify a query parameter like filter=car:engine,brand;engine:hp and receive the following:
|
|
{ "engine": { "hp": 180 }, "brand": "Jugular" } |
Step in Jackson
Jackson provides an annotation for such tasks called @JsonFilter. This annotation expects a filter name as a parameter and a named filter must be applied to serialization mapper, for example:
|
|
FilterProvider filters = new SimpleFilterProvider() .addFilter("carFilter", SimpleBeanPropertyFilter.filterOutAllExcept("wheels")); String jsonString = mapper.writer(filters)... |
As you can see, all we need is already there but is a rather static affair. We need to take this and make it fully dynamic and client driven.
The reason filter needs a name is because each one is bound to a class and attribute filtering is done on that class. What we need to do is transform car:engine,brand into a carFilter and SimpleBeanPropertyFilter.filterOutAllExcept("engine", "brand").
For starters, lets add the filters to our classes:
|
|
@JsonFilter("carFilter") public class Car {} @JsonFilter("engineFilter") public class Engine {} @JsonFilter("wheelFilter") public class Wheel {} |
There is one thing about this that bothers me.. the filter name is a static String so it is refactor unfriendly if class name changes some day. Couldn't we just name the filters by taking a look at the name of the underlying class? Yes we can, by extending Jackson introspection:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
public class MyJacksonAnnotationIntrospector extends JacksonAnnotationIntrospector { @Override public Object findFilterId(Annotated a) { JsonFilter ann = _findAnnotation(a, JsonFilter.class); if (ann != null) { String id = ann.value(); if (id.length() > 0) { return id; } else { try { //Use className+Filter as filter ID if ID is not set, e.g. Car -> carFilter Class<?> clazz = Class.forName(a.getName()); return StringUtils.uncapitalize(clazz.getSimpleName())+"Filter"; } catch (ClassNotFoundException e) { e.printStackTrace(); } } } return null; } } |
With this, any class annotated with @JsonFilter("") will automatically get a filter called classNameFilter. We no longer need to specify filter names and keep them in sync with class names.
Our lib now looks like:
|
|
@JsonFilter("") public class Car {} @JsonFilter("") public class Engine {} @JsonFilter("") public class Wheel {} |
Next step is to transform and apply the query parameters into our filter structure.
First, register a Jackson provider for JAX-RS server:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
@Provider public class JacksonProvider extends JacksonJsonProvider implements ContextResolver<ObjectMapper> { private final ObjectMapper mapper; public JacksonProvider() { mapper = new ObjectMapper(); mapper.registerModule(new JavaTimeModule()); mapper.setFilterProvider(new SimpleFilterProvider().setFailOnUnknownId(false)); mapper.setAnnotationIntrospector(new MyJacksonAnnotationIntrospector()); } @Override public ObjectMapper getContext(Class<?> type) { return mapper; } } |
We register our own introspector and disable failures on unknown filters (in case client filters by something nonexisting).
Provider must be registered in your rest Application.
|
|
@ApplicationPath("") public class MyApplication extends Application { @Override public Set<Class<?>> getClasses() { Set<Class<?>> classes = new HashSet<>(); classes.add(JacksonProvider.class); return classes; } } |
Finally, we implement our own MessageBodyWriter to override the default serialization and apply the filters dynamically.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 |
@Provider @Produces(MediaType.APPLICATION_JSON) public class JsonFilterProvider implements MessageBodyWriter<Object> { @Context private UriInfo uriInfo; @Context private JacksonProvider jsonProvider; public static final String PARAM_NAME = "filter"; public boolean isWriteable(Class<?> aClass, Type type, Annotation[] annotations, MediaType mediaType) { return MediaType.APPLICATION_JSON_TYPE.equals(mediaType); } public long getSize(Object object, Class<?> aClass, Type type, Annotation[] annotations, MediaType mediaType) { return -1; } public void writeTo(Object object, Class<?> aClass, Type type, Annotation[] annotations, MediaType mediaType, MultivaluedMap<String, Object> stringObjectMultivaluedMap, OutputStream outputStream) throws IOException, WebApplicationException { String queryParamValue = uriInfo.getQueryParameters().getFirst(PARAM_NAME); if (queryParamValue!=null && !queryParamValue.equals("")) { SimpleFilterProvider sfp = new SimpleFilterProvider().setFailOnUnknownId(false); //We link @JsonFilter annotation with dynamic property filter for (Map.Entry<String, Set<String>> entry : getFilterLogic(queryParamValue).entrySet()) { sfp.addFilter(entry.getKey() + "Filter", SimpleBeanPropertyFilter.filterOutAllExcept(entry.getValue())); } jsonProvider.locateMapper(aClass, mediaType).writer(sfp).writeValue(outputStream, object); } else { jsonProvider.locateMapper(aClass, mediaType).writeValue(outputStream, object); } } //Map of object names and set of fields private Map<String, Set<String>> getFilterLogic(String paramValue) { // ?jsonFilter=car:engine,brand;engine:numOfCylinders String[] filters = paramValue.split(";"); Map<String, Set<String>> filterAndFields = new HashMap<>(); for (String filterInstance : filters) { //car:engine,brand List<String> pair = Arrays.asList(filterInstance.split(":")); if (pair.size()!=2) { throw new RuntimeException(); } Set<String> fields = new HashSet<>(Arrays.asList(pair.get(1).split(","))); filterAndFields.put(pair.get(0), fields); } return filterAndFields; } } |
getFilterLogic method assembles the query parameter structure into a map of <String className, Set<String> fields> which is then applied as a Jackson filter.
Finally, we need to register our JsonFilterProvider in our Application as we did with JacksonProvider.
|
|
@ApplicationPath("") public class MyApplication extends Application { @Override public Set<Class<?>> getClasses() { Set<Class<?>> classes = new HashSet<>(); classes.add(JacksonProvider.class); classes.add(JsonFilterProvider.class); return classes; } } |
One small deficiency with this solution is that once you specify a class with fields to filter, it will be filtered wherever in the nested JSON structure it appears, you can't just filter a specific class at a specific level. Realistically, I think this is a rather minor problem compared to the benefits and the simplicity of the implementation.
Finally a question on documentation. How do you tell the client developer about all the possible filter object names and their attributes? If you use OpenAPI you are 95% there. Simply document that you can filter by model name followed by attribute name. Client developer can easily figure out the names from your OpenAPI specification. The only remaining problem is when you don't want to allow filtering on all classes. In this case my approach would be to document a filterable class in OpenAPI description:
|
|
@ApiModel(description = "[Filterable] A car.") |
This manual approach of documenting goes against the rest of the paradigm so a real purist would write an OpenAPI extension that would introspect all @JsonFilter annotations and modify the descriptions automatically. But let's leave that for a future blog post.
A similar, more advanced and out-of-the-box solution is squiggly, which also uses Jackson under the hood.
Cen
GitHub
Eurobattle.net
Lagabuse.com
Bnetdocs
