JBoss.orgCommunity Documentation
Errai includes a comprehensive marshalling framework which permits the serialization of domain objects between the browser and the server. From the perspective of GWT, this is a complete replacement for the provided GWT serialization facilities and offers a great deal more flexibility. You are be able to map both application-specific domain model, as well as preexisting model, including model from third-party libraries using the custom definitions API.
All classes that you intend to be marshalled between the client and the server must be exposed to the marshalling framework. There are several ways you can do it and this section will take you through the different approaches you can take to fit your needs.
The simplest and most straight-forward way to map your domain entities is to annotate it with the
org.jboss.errai.common.client.api.annotations.Portable
annotation. Doing so will cause the marshalling system to discover the entities at both compile-time and runtime to produce the marshalling code and definitions to marshal and de-marshal the objects.
The mapping strategy that will be used depends on how much information you provide about your model up-front. If you simply annotate a domain object with
@Portable
and do nothing else, the marshalling system will use and exhaustive strategy to determine how to construct and deconstruct the object.
Let's take a look at how this works.
@Portable
public class Person {
private String name;
private int age;
public Person() {
}
public Person(String name, int age) {
this.name = name;
this.age = age;
}
public String getName() {
return name;
}
public int getAge() {
return age;
}
}
This is a pretty vanilla domain object. Note the default, public, no-argument constructor. In this case, it will be necessary to have one explicitly declared. But notice we have no setters. In this case, the marshaler will rely on private field access to write the values on each side of the marshalling transaction. For simple domain objects, this is both nice and convenient. But you may want to make the class immutable and have a constructor enforce invariance. See the next section for that.
Immutability is almost always a good practice, and the marshalling system provides you a straight forward way to tell it how to marshal and de-marshal objects which enforce an immutable contract. Let's modify our example from the previous section.
@Portable
public class Person {
private final String name;
private final int age;
public Person(@MapsTo("name") String name, @MapsTo("age") int age) {
this.name = name;
this.age = age;
}
public String getName() {
return name;
}
public int getAge() {
return age;
}
}
Here we have set both of the class fields final. By doing so, we had to remove our default constructor. But that's okay, because we have annotated the remaining constructor's parameters using the
org.jboss.errai.marshalling.client.api.annotations.MapsTo
annotation.
By doing this, we have told the marshaling system, for instance, that the first parameter of the constructor maps to the property
name
. Which in this case, defaults to the name of the corresponding field. This may not always be the case – as will be explored in the section on custom definitions. But for now that's a safe assumption.
Another good practice is to use a factory pattern to enforce invariance. Once again, let's modify our example.
@Portable
public class Person {
private final String name;
private final int age;
private Person(String name, int age) {
this.name = name;
this.age = age;
}
public static Person createPerson(@MapsTo("name") String name, @MapsTo("age") int age) {
return new Person(name, age);
}
public String getName() {
return name;
}
public int getAge() {
return age;
}
}
Here we have made our only declared constructor private, and created a static factory method. Notice that we've simply used the same
@MapsTo
annotation in the same way we did on the constructor from our previous example. The marshaller will see this method and know that it should use it to construct the object.
Some classes may be out of your control, making it impossible to annotate them for auto-discovery by the marshalling framework. For cases such as this, there are two approaches which can be undertaken to include these classes in your application.
The first approach is the easiest, but is contingent on whether or not the class is directly exposed to the GWT compiler. That means, the classes must be part of a GWT module and within the GWT client packages. See the GWT documentation on Client-Side Code for information on this.
If you have client-exposed classes that cannot be annotated with the
@Portable
annotation, you may manually map these classes so that the marshaller framework will comprehend and produce marshallers for them.
To do this, you may specify them in your
ErraiApp.properties
file, using the
errai.marshalling.serializableTypes
attribute with a whitespace separated list of classes to make portable.
Example 4.1. Example ErraiApp.properties defining portable classes.
errai.marshalling.serializableTypes=org.foo.client.UserEntity \
org.foo.client.GroupEntity \
org.abcinc.model.client.Profile
The marshalling framework supports and promotes the concept of marshalling by interface contract, where possible. For instance, the framework ships with a marshaller which can marshall data to and from the
java.util.List
interface. Instead of having custom marshallers for classes such as
ArrayList
and
LinkedList
, by default, these implementations are merely aliased to the
java.util.List
marshaller.
There are two distinct ways to go about doing this. The most straightforward is to specify which marshaller to alias when declaring your class is
@Portable
.
package org.foo.client;
@Portable(aliasOf = java.util.List.class)
public MyListImpl extends ArrayList {
// .. //
}
In the case of this example, the marshaller will not attempt to comprehend your class. Instead, it will merely rely on the
java.util.List
marshaller to dematerialize and serialize instances of this type onto the wire.
If for some reason it is not feasible to annotate the class, directly, you may specify the mapping in the
ErraiApp.properties
file using the
errai.marshalling.mappingAliases
attribute.
errai.marshalling.mappingAliases=org.foo.client.MyListImpl->java.uti.List \
org.foo.client.MyMapImpl->java.util.MapThe list of classes is whitespace-separated so that it may be split across lines.
The example above shows the equivalent mapping for the
MyListImpl
class from the previous example, as well as a mapping of a class to the
java.util.Map
marshaller.
The syntax of the mapping is as follows:
<class_to_map>
->
<contract_to_map_to>
.
When you alias a class to another marshalling contract, extended functionality of the aliased class will not be available upon deserialization. For this you must provide custom marshallers for those classes.
Although the default marshalling strategies in Errai Marshalling will suit the vast majority of use cases, there may be situations where it is necessary to manually map your classes into the marshalling framework to teach it how to construct and deconstruct your objects.
This is accomplished by specifying
MappingDefinition
classes which inform the framework exactly how to read and write state in the process of constructing and deconstructing objects.
All manual mappings should extend the
org.jboss.errai.marshalling.rebind.api.model.MappingDefinition
class. This is base metadata class which contains data on exactly how the marshaller can deconstruct and construct objects.
Consider the following class:
public class MySuperCustomEntity {
private final String mySuperName;
private String mySuperNickname;
public MySuperCustomEntity(String mySuperName) {
this.mySuperName = mySuperName;;
}
public String getMySuperName() {
return this.mySuperName;
}
public void setMySuperNickname(String mySuperNickname) {
this.mySuperNickname = mySuperNickname;
}
public String getMySuperNickname() {
return this.mySuperNickname;
}
}
Let us construct this object like so:
MySuperCustomEntity entity = new MySuperCustomEntity("Coolio");
entity.setSuperNickname("coo");
It is clear that we may rely on this object's two getter methods to extract the totality of its state. But due to the fact that the
mySuperName
field is final, the only way to properly construct this object is to call its only public constructor and pass in the desired value of
mySuperName
.
Let us consider how we could go about telling the marshalling framework to pull this off:
@CustomMapping
public MySuperCustomEntityMapping extends MappingDefinition {
public MySuperCustomEntityMapping() {
super(MySuperCustomEntity.class); // (1)
SimpleConstructorMapping cnsMapping = new SimpleConstructorMapping();
cnsMapping.mapParmToIndex("mySuperName", 0, String.class); // (2)
setInstantiationMapping(cnsMapping);
addMemberMapping(new WriteMapping("mySuperNickname", String.class, "setMySuperNickname")); // (3)
addMemberMapping(new ReadMapping("mySuperName", String.class, "getMySuperName")); // (4)
addMemberMapping(new ReadMapping("mySuperNickname", String.class, "getMySuperNickname")); // (5)
}
}
And that's it. This describes to the marshalling framework how it should go about constructing and deconstructing
MySuperCustomEntity
.
Paying attention to our annotating comments, let's describe what we've done here.
Call the constructor in
MappingDefinition
passing our reference to the class we are mapping.
Using the
SimpleConstructorMapping
class, we have indicated that a custom constructor will be needed to instantiate this class. We have called the
mapParmToIndex
method with three parameters. The first,
"mySupername"
describes the class field that we are targeting. The second parameter, the integer
0
indicates the parameter index of the constructor arguments that we'll be providing the value for the aforementioned field – in this case the first and only, and the final parameter
String.class
tells the marshalling framework which marshalling contract to use in order to de-marshall the value.
Using the
WriteMapping
class, we have indicated to the marshaller framework how to write the
"mySuperNickname"
field, using the
String.class
marshaller, and using the setter method
setMySuperNickname
.
Using the
ReadMapping
class, we have indicated to the marshaller framework how to read the
"mySuperName"
field, using the
String.class
marshaller, and using the getter method
getMySuperName
.
Using the
ReadMapping
class, we have indicated to the marshaller framework how to read the
"mySuperNickname"
field, using the
String.class
marshaller, and using the getter method
getMySuperNickname
.
There is another approach to extending the marshalling functionality that doesn't involve mapping rules, and that is to implement your own
Marshaller
class. This gives you complete control over the parsing and emission of the JSON structure.
The implementation of marshallers is made relatively straight forward by the fact that both the server and the client share the same JSON parsing API.
Consider the included
java.util.Date
marshaller that comes built-in to the marshalling framework:
Example 4.2. DataMarshaller.java from the built-in marshallers
@ClientMarshaller @ServerMarshaller
public class DateMarshaller extends AbstractNullableMarshaller<Date> {
@Override
public Class<Date> getTypeHandled() {
return Date.class;
}
@Override
public Date demarshall(EJValue o, MarshallingSession ctx) {
// check if the JSON element is null
if (o.isNull() != null) {
// if the JSON element is null, so is our object!
return null;
}
// instantiate our Date!
return new Date(Long.parseLong(o.isObject().get(SerializationParts.QUALIFIED_VALUE).isString().stringValue()));
}
@Override
public String marshall(Date o, MarshallingSession ctx) {
// if the object is null, we encode "null"
if (o == null) { return "null"; }
// return the JSON representation of the object
return "{\"" + SerializationParts.ENCODED_TYPE + "\":\"" + Date.class.getName() + "\"," +
"\"" + SerializationParts.OBJECT_ID + "\":\"" + o.hashCode() + "\"," +
"\"" + SerializationParts.QUALIFIED_VALUE + "\":\"" + o.getTime() + "\"}";
}
}
The class is annotated with both
@ClientMarshaller
and
@ServerMarshaller
indicating that this class should be used for both marshalling on the client and on the server.
The
demarshall()
method does what its name implies: it is responsible for demarshalling the object from JSON and turning it back into a Java object.
The
marshall()
method does the opposite, and encodes the object into JSON for transmission on the wire.