| commit | 0e7fab7a4b2b4384187cb175c42840af745e30f0 | [log] [tgz] |
|---|---|---|
| author | Tatu Saloranta <tsaloranta@gmail.com> | Tue Apr 17 10:11:55 2012 -0700 |
| committer | Tatu Saloranta <tsaloranta@gmail.com> | Tue Apr 17 10:11:55 2012 -0700 |
| tree | 251128a81db4d0a7be61ac9a7c2656d1cb6c2404 | |
| parent | 9e31e616358bcb980e997dd7d81f4a5a95ed4969 [diff] |
Change target to 1.5, was accidentally set to 1.6 for 2.0.0
This project contains general purpose annotations for Jackson Data Processor, used on value and handler types. The only annotations not included are ones that require dependency to the Databind package.
Project contains versions 2.0 and above: source code for earlier (1.x) versions is available from Codehaus SVN repository. Note that with version 1.x these annotations were part of the 'core jar'.
Full Listing of Jackson Annotations details all available annotations; Javadocs gives more details.
In addition to regular usage (see below), there are couple of noteworthy improvements Jackson does:
All annotations are in Java package com.fasterxml.core.annotation. To use annotations, you need to use Maven dependency:
<dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-annotations</artifactId> <version>2.0.0</version> </dependency>
or download jars from Maven repository or Download page
Let's start with simple use cases: renaming or ignoring properties, and modifying types that are used.
Note: while examples only show field properties, same annotations would work with method (getter/setter) properties.
One of most common tasks is to change JSON name used for a property: for example:
public class Name {
@JsonProperty("firstName")
public String _first_name;
}
would result in JSON like:
{ "firstName" : "Bob" }
instead of
{ "_first_name" : "Bob"
Sometimes POJOs contain properties that you do not want to write out, so you can do:
public class Value {
public int value;
@JsonIgnore public int internalValue;
}
and get JSON like:
{ "value" : 42 }
or, you may get properties in JSON that you just want to skip: if so, you can use:
@JsonIgnoreProperties({ "extra", "uselessValue" })
public class Value {
public int value;
}
which would be able to handle JSON like:
{ "value" : 42, "extra" : "fluffy", "uselessValue" : -13 }
Finally, you may even want to just ignore any "extra" properties from JSON (ones for which there is no counterpart in POJO). This can be done by adding:
@JsonIgnoreProperties(ignoreUnknown=true)
public class PojoWithAny {
public int value;
}
Sometimes the type Jackson uses when reading or writing a property is not quite what you want:
These cases can be handled by following annotations:
public class ValueContainer {
// although nominal type is 'Value', we want to read JSON as 'ValueImpl'
@JsonDeserialize(as=ValueImpl.class)
public Value value;
// although runtime type may be 'AdvancedType', we really want to serialize
// as 'BasicType'; two ways to do this:
@JsonSerialize(as=BasicType.class)
// or could also use: @JsonSerialize(typing=Typing.STATIC)
public BasicType another;
}
By default, Jackson tries to use the "default" constructor (one that takes no arguments), when creating value instances. But you can also choose to use another constructor, or a static factory method to create instance. To do this, you will need to use annotation @JsonCreator, and possibly @JsonProperty annotations to bind names to arguments:
public class CtorPOJO {
private final int _x, _y;
@JsonCreator
public CtorPOJO(@JsonProperty("x") int x, @JsonProperty("y") int y) {
_x = x;
_y = y;
}
}
@JsonCreator can be used similarly for static factory methods. But there is also an alternative usage, which is so-called "delegating" creator:
public class DelegatingPOJO {
private final int _x, _y;
@JsonCreator
public DelegatingPOJO(Map<String,Object> delegate) {
_x = (Integer) delegate.get("x");
_y = (Integer) delegate.get("y");
}
the difference being that the creator method can only take one argument, and that argument must NOT have @JsonProperty annotation.
If you need to read and write values of Objects where there are multiple possible subtypes (i.e. ones that exhibit polymorphism), you may need to enable inclusion of type information. This is needed so that Jackson can read back correct Object type when deserializing (reading JSON into Objects). This can be done by adding @JsonTypeInfo annotation on ''base class'':
// Include Java class name ("com.myempl.ImplClass") as JSON property "class"
@JsonTypeInfo(use=Id.CLASS, include=As.PROPERTY, property="class")
public abstract class BaseClass {
}
public class Impl1 extends BaseClass {
public int x;
}
public class Impl2 extends BaseClass {
public String name;
}
public class PojoWithTypedObjects {
public List<BaseClass> items;
}
and this could result in serialized JSON like:
{ "items" : [
{ "class":"Impl2", "name":"Bob" },
{ "class":"Impl1", "x":13 }
])
Note that this annotation has lots of configuration possibilities: for more information check out:
The default Jackson property detection rules will find:
But if this does not work, you can change visibility levels by using annotation @JsonAutoDetect. If you wanted, for example, to auto-detect ALL fields (similar to how packages like GSON work), you could do:
@JsonAutoDetect(fieldVisiblity=JsonAutoDetect.Visibility.ANY)
public class POJOWithFields {
private int value;
}
or, to disable auto-detection of fields altogether:
@JsonAutoDetect(fieldVisiblity=JsonAutoDetect.Visibility.NONE)
public class POJOWithNoFields {
// will NOT be included, unless there is access 'getValue()'
public int value;
}
Project-specific documentation:
Related: