JSON serialization and parsing support

Table of Contents
  1. JSON support overview

    1. Example

  2. JsonSerializer class

    1. @Bean and @BeanProperty annotations

    2. Collections

    3. JSON-Schema support

    4. Non-tree models and recursion detection

    5. Configurable properties

    6. Other notes

  3. JsonParser class

    1. Parsing into generic POJO models

    2. Configurable properties

    3. Other notes

  4. REST API support

    1. REST server support

      1. Using RestServletDefault

      2. Using RestServlet with annotations

      3. Using JAX-RS DefaultProvider

      4. Using JAX-RS BaseProvider with annotations

    2. REST client support

1 -JSON support overview

Juneau supports converting arbitrary POJOs to and from JSON using ultra-efficient serializers and parsers.
The JSON serializer converts POJOs directly to JSON without the need for intermediate DOM objects using a highly-efficient state machine.
Likewise, the JSON parser creates POJOs directly from JSON without the need for intermediate DOM objects.

Juneau can serialize and parse instances of any of the following POJO types:

Refer to POJO Categories for a complete definition of supported POJOs.

Prerequisites

The Juneau JSON serialization and parsing support does not require any external prerequisites. It only requires Java 1.6 or above.

1.1 - JSON support overview - example

The example shown here is from the Address Book resource located in the org.apache.juneau.sample.war application.
The POJO model consists of a List of Person beans, with each Person containing zero or more Address beans.

When you point a browser at /sample/addressBook, the POJO is rendered as HTML:

By appending ?Accept=mediaType&plainText=true to the URL, you can view the data in the various supported JSON formats:

Normal JSON
Simple JSON

In addition to serializing POJOs to JSON, Juneau includes support for serializing POJO metamodels to JSON Schema.

JSON Schema

The JSON data type produced depends on the Java object type being serialized.

Examples:
POJO type Example Serialized form
String serializer.serialize("foobar"); 'foobar'
Number serializer.serialize(123); 123
Boolean serializer.serialize(true); true
Null serializer.serialize(null); null
Beans with properties of any type on this list serializer.serialize(new MyBean()); {p1:'val1',p2:true}
Maps with values of any type on this list serializer.serialize(new TreeMap()); {key1:'val1',key2:true}
Collections and arrays of any type on this list serializer.serialize(new Object[]{1,"foo",true}); [1,'foo',true]

In addition, swaps can be used to convert non-serializable POJOs into serializable forms, such as converting Calendar object to ISO8601 strings, or byte[] arrays to Base-64 encoded strings.
These swaps can be associated at various levels:

For more information about transforms, refer to org.apache.juneau.transform.

2 - JsonSerializer class

{@link org.apache.juneau.json.JsonSerializer} is the class used to convert POJOs to JSON.
{@link org.apache.juneau.json.JsonSchemaSerializer} is the class used to generate JSON-Schema from POJOs.

The JSON serializer includes several configurable settings.
Static reusable instances of Json serializers are provided with commonly-used settings:

Notes about examples

The examples shown in this document will use single-quote, readable settings.
For brevity, the examples will use public fields instead of getters/setters to reduce the size of the examples.
In the real world, you'll typically want to use standard bean getters and setters.

To start off simple, we'll begin with the following simplified bean and build upon it.

public class Person { // Bean properties public int id; public String name; // Bean constructor (needed by parser) public Person() {} // Normal constructor public Person(int id, String name) { this.id = id; this.name = name; } }

The following code shows how to convert this to simple JSON:

// Use serializer with readable output, simple mode. JsonSerializer s = JsonSerializer.DEFAULT_LAX_READABLE; // Create our bean. Person p = new Person(1, "John Smith"); // Serialize the bean to JSON. String json = s.serialize(p);

We could have also created a new serializer with the same settings using the following code:

JsonSerializer s = new JsonSerializerBuilder().simple().ws().sq().build();

The code above produces the following output:

{ id: 1, name: 'John Smith' }

2.1 - @Bean and @BeanProperty annotations

The {@link org.apache.juneau.annotation.Bean @Bean} and {@link org.apache.juneau.annotation.BeanProperty @BeanProperty} annotations are used to customize the behavior of beans across the entire framework.
They have various uses:

For example, we now add a birthDate property, and associate a swap with it to transform it to an ISO8601 date-time string in GMT time.
We'll also add a couple of URI properties.
By default, Calendars are treated as beans by the framework, which is usually not how you want them serialized.
Using swaps, we can convert them to standardized string forms.

public class Person { // Bean properties public int id; public String name; public URI uri; public URI addressBookUri; @BeanProperty(swap=CalendarSwap.ISO8601DTZ.class) public Calendar birthDate; // Bean constructor (needed by parser) public Person() {} // Normal constructor public Person(int id, String name, String uri, String addressBookUri, String birthDate) throws Exception { this.id = id; this.name = name; this.uri = new URI(uri); this.addressBookUri = new URI(addressBookUri); this.birthDate = new GregorianCalendar(); this.birthDate.setTime(DateFormat.getDateInstance(DateFormat.MEDIUM).parse(birthDate)); } }

Next, we alter our code to pass in the birthdate:

// Create our bean. Person p = new Person(1, "John Smith", "http://sample/addressBook/person/1", "http://sample/addressBook", "Aug 12, 1946");

Now when we rerun the sample code, we'll get the following:

{ id: 1, name: 'John Smith', uri: 'http://sample/addressBook/person/1', addressBookUri: 'http://sample/addressBook', birthDate: '1946-08-12T00:00:00Z' }

Another useful feature is the {@link org.apache.juneau.annotation.Bean#propertyNamer()} annotation that allows you to plug in your own logic for determining bean property names.
The {@link org.apache.juneau.PropertyNamerDLC} is an example of an alternate property namer. It converts bean property names to lowercase-dashed format.

Example:

@Bean(propertyNamer=PropertyNamerDLC.class) public class Person { ...

Results

{ id: 1, name: 'John Smith', uri: 'http://sample/addressBook/person/1', 'address-book-uri': 'http://sample/addressBook', 'birth-date': '1946-08-12T00:00:00Z' }

2.2 - Collections

In our example, let's add a list-of-beans property to our sample class:

public class Person { // Bean properties public LinkedList<Address> addresses = new LinkedList<Address>(); ... }

The Address class has the following properties defined:

public class Address { // Bean properties public URI uri; public URI personUri; public int id; public String street, city, state; public int zip; public boolean isCurrent; }

Next, add some quick-and-dirty code to add an address to our person bean:

// Use serializer with readable output, simple mode. JsonSerializer s = JsonSerializer.DEFAULT_LAX_READABLE; // Create our bean. Person p = new Person(1, "John Smith", "http://sample/addressBook/person/1", "http://sample/addressBook", "Aug 12, 1946"); Address a = new Address(); a.uri = new URI("http://sample/addressBook/address/1"); a.personUri = new URI("http://sample/addressBook/person/1"); a.id = 1; a.street = "100 Main Street"; a.city = "Anywhereville"; a.state = "NY"; a.zip = 12345; a.isCurrent = true; p.addresses.add(a);

Now when we run the sample code, we get the following:

{ id: 1, name: 'John Smith', uri: 'http://sample/addressBook/person/1', addressBookUri: 'http://sample/addressBook', birthDate: '1946-08-12T00:00:00Z', addresses: [ { uri: 'http://sample/addressBook/address/1', personUri: 'http://sample/addressBook/person/1', id: 1, street: '100 Main Street', city: 'Anywhereville', state: 'NY', zip: 12345, isCurrent: true } ] }

2.3 - JSON-Schema support

Juneau provides the {@link org.apache.juneau.json.JsonSchemaSerializer} class for generating JSON-Schema documents that describe the output generated by the {@link org.apache.juneau.json.JsonSerializer} class.
This class shares the same properties as JsonSerializer.
For convenience the {@link org.apache.juneau.json.JsonSerializer#getSchemaSerializer()} method has been added for creating instances of schema serializers from the regular serializer instance.

Note: As of this writing, JSON-Schema has not been standardized, so the output generated by the schema serializer may be subject to future modifications.

Lets start with the classes from the previous examples:

public class Person { // Bean properties public int id; public String name; public URI uri; public URI addressBookUri; @BeanProperty(swap=CalendarSwap.ISO8601DTZ.class) public Calendar birthDate; public LinkedList<Address> addresses = new LinkedList<Address>(); // Bean constructor (needed by parser) public Person() {} // Normal constructor public Person(int id, String name, String uri, String addressBookUri, String birthDate) throws Exception { this.id = id; this.name = name; this.uri = new URI(uri); this.addressBookUri = new URI(addressBookUri); this.birthDate = new GregorianCalendar(); this.birthDate.setTime(DateFormat.getDateInstance(DateFormat.MEDIUM).parse(birthDate)); } } public class Address { // Bean properties public URI uri; public URI personUri; public int id; public String street, city, state; public int zip; public boolean isCurrent; }

The code for creating our POJO model and generating JSON-Schema is shown below:

// Get the schema serializer for one of the default JSON serializers. JsonSchemaSerializer s = JsonSerializer.DEFAULT_LAX_READABLE.getSchemaSerializer(); // Create our bean. Person p = new Person(1, "John Smith", "http://sample/addressBook/person/1", "http://sample/addressBook", "Aug 12, 1946"); Address a = new Address(); a.uri = new URI("http://sample/addressBook/address/1"); a.personUri = new URI("http://sample/addressBook/person/1"); a.id = 1; a.street = "100 Main Street"; a.city = "Anywhereville"; a.state = "NY"; a.zip = 12345; a.isCurrent = true; p.addresses.add(a); // Get the JSON Schema corresponding to the JSON generated above. String jsonSchema = s.serialize(p);

Results

{ type: 'object', description: 'org.apache.juneau.sample.Person', properties: { id: { type: 'number', description: 'int' }, name: { type: 'string', description: 'java.lang.String' }, uri: { type: 'any', description: 'java.net.URI' }, addressBookUri: { type: 'any', description: 'java.net.URI' }, birthDate: { type: 'any', description: 'java.util.Calendar' }, addresses: { type: 'array', description: 'java.util.LinkedList<org.apache.juneau.sample.Address>', items: { type: 'object', description: 'org.apache.juneau.sample.Address', properties: { uri: { type: 'any', description: 'java.net.URI' }, personUri: { type: 'any', description: 'java.net.URI' }, id: { type: 'number', description: 'int' }, street: { type: 'string', description: 'java.lang.String' }, city: { type: 'string', description: 'java.lang.String' }, state: { type: 'string', description: 'java.lang.String' }, zip: { type: 'number', description: 'int' }, isCurrent: { type: 'boolean', description: 'boolean' } } } } } }

2.4 - Non-tree models and recursion detection

The JSON serializer is designed to be used against POJO tree structures.
It expects that there not be loops in the POJO model (e.g. children with references to parents, etc...).
If you try to serialize models with loops, you will usually cause a StackOverflowError to be thrown (if {@link org.apache.juneau.serializer.SerializerContext#SERIALIZER_maxDepth} is not reached first).

If you still want to use the JSON serializer on such models, Juneau provides the {@link org.apache.juneau.serializer.SerializerContext#SERIALIZER_detectRecursions} setting.
It tells the serializer to look for instances of an object in the current branch of the tree and skip serialization when a duplicate is encountered.

For example, let's make a POJO model out of the following classes:

public class A { public B b; } public class B { public C c; } public class C { public A a; }

Now we create a model with a loop and serialize the results.

// Clone an existing serializer and set property for detecting recursions. JsonSerializer s = JsonSerializer.DEFAULT_LAX_READABLE.builder().detectRecursions(true).build(); // Create a recursive loop. A a = new A(); a.b = new B(); a.b.c = new C(); a.b.c.a = a; // Serialize to JSON. String json = s.serialize(a);

What we end up with is the following, which does not serialize the contents of the c field:

{ b: { c: { } } }

Without recursion detection enabled, this would cause a stack-overflow error.

Recursion detection introduces a performance penalty of around 20%.
For this reason the setting is disabled by default.

2.5 - Configurable properties

See the following classes for all configurable properties that can be used on this serializer:

2.6 - Other notes

3 - JsonParser class

The {@link org.apache.juneau.json.JsonParser} class is the class used to parse JSON back into POJOs.

The JSON parser supports ALL valid JSON, including:

A static reusable instance of JsonParser is also provided for convenience:

Let's build upon the previous example and parse the generated JSON back into the original bean.
We start with the JSON that was generated.

// Use serializer with readable output, simple mode. JsonSerializer s = JsonSerializer.DEFAULT_LAX_READABLE; // Create our bean. Person p = new Person(1, "John Smith", "http://sample/addressBook/person/1", "http://sample/addressBook", "Aug 12, 1946"); Address a = new Address(); a.uri = new URI("http://sample/addressBook/address/1"); a.personUri = new URI("http://sample/addressBook/person/1"); a.id = 1; a.street = "100 Main Street"; a.city = "Anywhereville"; a.state = "NY"; a.zip = 12345; a.isCurrent = true; p.addresses.add(a); // Serialize the bean to JSON. String json = s.serialize(p);

This code produced the following:

{ id: 1, name: 'John Smith', uri: 'http://sample/addressBook/person/1', addressBookUri: 'http://sample/addressBook', birthDate: '1946-08-12T00:00:00Z', addresses: [ { uri: 'http://sample/addressBook/address/1', personUri: 'http://sample/addressBook/person/1', id: 1, street: '100 Main Street', city: 'Anywhereville', state: 'NY', zip: 12345, isCurrent: true } ] }

The code to convert this back into a bean is:

// Parse it back into a bean using the reusable JSON parser. Person p = JsonParser.DEFAULT.parse(json, Person.class); // Render it back as JSON. json = JsonSerializer.DEFAULT_LAX_READABLE.serialize(p);

We print it back out to JSON to show that all the data has been preserved:

{ id: 1, name: 'John Smith', uri: 'http://sample/addressBook/person/1', addressBookUri: 'http://sample/addressBook', birthDate: '1946-08-12T00:00:00Z', addresses: [ { uri: 'http://sample/addressBook/address/1', personUri: 'http://sample/addressBook/person/1', id: 1, street: '100 Main Street', city: 'Anywhereville', state: 'NY', zip: 12345, isCurrent: true } ] }

3.1 - Parsing into generic POJO models

The JSON parser is not limited to parsing back into the original bean classes.
If the bean classes are not available on the parsing side, the parser can also be used to parse into a generic model consisting of Maps, Collections, and primitive objects.

You can parse into any Map type (e.g. HashMap, TreeMap), but using {@link org.apache.juneau.ObjectMap} is recommended since it has many convenience methods for converting values to various types.
The same is true when parsing collections. You can use any Collection (e.g. HashSet, LinkedList) or array (e.g. Object[], String[], String[][]), but using {@link org.apache.juneau.ObjectList} is recommended.

When the map or list type is not specified, or is the abstract Map, Collection, or List types, the parser will use ObjectMap and ObjectList by default.

Starting back with our original JSON:

{ id: 1, name: 'John Smith', uri: 'http://sample/addressBook/person/1', addressBookUri: 'http://sample/addressBook', birthDate: '1946-08-12T00:00:00Z', addresses: [ { uri: 'http://sample/addressBook/address/1', personUri: 'http://sample/addressBook/person/1', id: 1, street: '100 Main Street', city: 'Anywhereville', state: 'NY', zip: 12345, isCurrent: true } ] }

We can parse this into a generic ObjectMap:

// Parse JSON into a generic POJO model. ObjectMap m = JsonParser.DEFAULT.parse(json, ObjectMap.class); // Convert it back to JSON. String json = JsonSerializer.DEFAULT_LAX_READABLE.serialize(m);

What we end up with is the exact same output.
Even the numbers and booleans are preserved because they are parsed into Number and Boolean objects when parsing into generic models.

{ id: 1, name: 'John Smith', uri: 'http://sample/addressBook/person/1', addressBookUri: 'http://sample/addressBook', birthDate: '1946-08-12T00:00:00Z', addresses: [ { uri: 'http://sample/addressBook/address/1', personUri: 'http://sample/addressBook/person/1', id: 1, street: '100 Main Street', city: 'Anywhereville', state: 'NY', zip: 12345, isCurrent: true } ] }

Once parsed into a generic model, various convenience methods are provided on the ObjectMap and ObjectList classes to retrieve values:

// Parse JSON into a generic POJO model. ObjectMap m = JsonParser.DEFAULT.parse(json, ObjectMap.class); // Get some simple values. String name = m.getString("name"); int id = m.getInt("id"); // Get a value convertable from a String. URI uri = m.get(URI.class, "uri"); // Get a value using a swap. CalendarSwap swap = new CalendarSwap.ISO8601DTZ(); Calendar birthDate = m.get(swap, "birthDate"); // Get the addresses. ObjectList addresses = m.getObjectList("addresses"); // Get the first address and convert it to a bean. Address address = addresses.get(Address.class, 0);

As a general rule, parsing into beans is often more efficient than parsing into generic models.
And working with beans is often less error prone than working with generic models.

3.2 - Configurable properties

See the following classes for all configurable properties that can be used on this parser:

3.3 - Other notes

4 - REST API support

Juneau provides fully-integrated support for JSON serialization/parsing in the REST server and client APIs.
The next two sections describe these in detail.

4.1 - REST server support

There are four general ways of defining REST interfaces with support for JSON. Two using the built-in Juneau Server API, and two using the JAX-RS integration component.

In general, the Juneau REST server API is much more configurable and easier to use than JAX-RS, but beware that the author may be slightly biased in this statement.

4.1.1 - Using RestServletDefault

The quickest way to implement a REST resource with JSON support is to create a subclass of {@link org.apache.juneau.rest.RestServletDefault}.
This class provides support for JSON, XML, HTML, URL-Encoding, and others.

The AddressBookResource example shown in the first chapter uses the RestServletJenaDefault class which is a subclass of RestServletDefault with additional support for RDF languages.
The start of the class definition is shown below:

// Proof-of-concept resource that shows off the capabilities of working with POJO resources. // Consists of an in-memory address book repository. @RestResource( messages="nls/AddressBookResource", title="$L{title}", description="$L{description}", htmldoc=@HtmlDoc( links="{options:'?method=OPTIONS'}" ), properties={ @Property(name=SerializerContext.SERIALIZER_quoteChar, value="'"), @Property(name=HtmlSerializerContext.HTML_uriAnchorText, value=TO_STRING) }, encoders=GzipEncoder.class ) public class AddressBookResource extends RestServletJenaDefault {

Notice how serializer and parser properties can be specified using the @RestResource.properties() annotation.
The SERIALIZER_quoteChar is a property common to all serializers, including the JSON serializer. The remaining properties are specific to the HTML serializer.

The $L{...} variable represent localized strings pulled from the resource bundle identified by the messages annotation. These variables are replaced at runtime based on the HTTP request locale. Several built-in runtime variable types are defined, and the API can be extended to include user-defined variables. See {@link org.apache.juneau.rest.RestContext#getVarResolver()} for more information.

This document won't go into all the details of the Juneau RestServlet class.
Refer to the org.apache.juneau.rest documentation for more information on the REST servlet class in general.

The rest of the code in the resource class consists of REST methods that simply accept and return POJOs.
The framework takes care of all content negotiation, serialization/parsing, and error handling.
Below are 3 of those methods to give you a general idea of the concept:

// GET person request handler @RestMethod(name="GET", path="/people/{id}/*", rc={200,404}) public Person getPerson(RestRequest req, RestResponse res, @Path int id) throws Exception { res.setPageTitle(req.getPathInfo()); return findPerson(id); } // POST person handler @RestMethod(name="POST", path="/people", guards=AdminGuard.class, rc={307,404}) public void createPerson(RestResponse res, @Body CreatePerson cp) throws Exception { Person p = addressBook.createPerson(cp); res.sendRedirect(p.uri); } // DELETE person handler @RestMethod(name="DELETE", path="/people/{id}", guards=AdminGuard.class, rc={200,404}) public String deletePerson(RestResponse res, @Path int id) throws Exception { Person p = findPerson(id); addressBook.remove(p); return "DELETE successful"; }

The resource class can be registered with the web application like any other servlet, or can be defined as a child of another resource through the {@link org.apache.juneau.rest.annotation.RestResource#children()} annotation.

4.1.2 - Using RestServlet with annotations

For fine-tuned control of media types, the {@link org.apache.juneau.rest.RestServlet} class can be subclassed directly.
The serializers/parsers can be specified through annotations at the class and/or method levels.

An equivalent AddressBookResource class could be defined to only support JSON using the following definition:

@RestResource( serializers={JsonSerializer.class}, parsers={JsonParser.class}, properties={ @Property(name=SerializerContext.SERIALIZER_quoteChar, value="'") } ) public class AddressBookResource extends RestServlet {

Likewise, serializers and parsers can be specified/augmented/overridden at the method level like so:

// GET person request handler @RestMethod(name="GET", path="/people/{id}/*", rc={200,404}, serializers={JsonSerializer.class}, parsers={JsonParser.class}, properties={ @Property(name=SerializerContext.SERIALIZER_quoteChar, value="'") } ) public Person getPerson(RestRequest req, RestResponse res, @Path int id) throws Exception { res.setPageTitle(req.getPathInfo()); return findPerson(id); }

The {@link org.apache.juneau.rest.annotation.RestMethod#serializersInherit()} and {@link org.apache.juneau.rest.annotation.RestMethod#parsersInherit()} control how various artifacts are inherited from the parent class.
Refer to org.apache.juneau.rest for additional information on using these annotations.

4.1.3 - Using JAX-RS DefaultProvider

JSON media type support in JAX-RS can be achieved by using the {@link org.apache.juneau.rest.jaxrs.DefaultProvider} class.
It implements the JAX-RS MessageBodyReader and MessageBodyWriter interfaces for all Juneau supported media types.

The DefaultProvider class definition is shown below:

@Provider @Produces( "application/json,text/json,"+ // JsonSerializer "application/json+simple,text/json+simple"+ // JsonSerializer.Simple "application/json+schema,text/json+schema"+ // JsonSchemaSerializer "text/xml"+ // XmlDocSerializer "text/xml+simple"+ // XmlDocSerializer.Simple "text/xml+schema"+ // XmlSchemaDocSerializer "text/html"+ // HtmlDocSerializer "application/x-www-form-urlencoded"+ // UrlEncodingSerializer "text/xml+soap"+ // SoapXmlSerializer "application/x-java-serialized-object" // JavaSerializedObjectSerializer ) @Consumes( "application/json,text/json,"+ // JsonParser "text/xml,"+ // XmlParser "text/html,"+ // HtmlParser "application/x-www-form-urlencoded,"+ // UrlEncodingParser "application/x-java-serialized-object" // JavaSerializedObjectParser ) @JuneauProvider( serializers={ JsonSerializer.class, JsonSerializer.Simple.class, JsonSchemaSerializer.class, XmlDocSerializer.class, XmlDocSerializer.Simple.class, XmlSchemaDocSerializer.class, HtmlDocSerializer.class, UrlEncodingSerializer.class, SoapXmlSerializer.class, JavaSerializedObjectSerializer.class }, parsers={ JsonParser.class, XmlParser.class, HtmlParser.class, UrlEncodingParser.class, JavaSerializedObjectParser.class, } ) public final class DefaultProvider extends BaseProvider {}

That's the entire class. It consists of only annotations to hook up media types to Juneau serializers and parsers. The @Provider, @Produces, and @Consumes annotations are standard JAX-RS annotations, and the @JuneauProvider annotation is from Juneau.

To enable the provider, you need to make the JAX-RS environment aware of it. In Wink, this is accomplished by adding an entry to a config file.

<web-app version="2.3"> <servlet> <servlet-name>WinkService</servlet-name> <servlet-class>org.apache.wink.server.internal.servlet.RestServlet</servlet-class> <init-param> <param-name>applicationConfigLocation</param-name> <param-value>/WEB-INF/wink.cfg</param-value> </init-param> </servlet>

Simply include a reference to the provider in the configuration file.

org.apache.juneau.rest.jaxrs.DefaultProvider

Properties can be specified on providers through the {@link org.apache.juneau.rest.jaxrs.JuneauProvider#properties()} annotation.
Properties can also be specified at the method level by using the {@link org.apache.juneau.rest.annotation.RestMethod#properties} annotation, like so:

@GET @Produces("*/*") @RestMethod( /* Override some properties */ properties={ @Property(name=SerializerContext.SERIALIZER_quoteChar, value="'") } ) public Message getMessage() { return message; }

Limitations

In general, the Juneau REST API is considerably more flexible than the JAX-RS API, since you can specify and override serializers, parsers, properties, transforms, converters, guards, etc... at both the class and method levels.
Therefore, the JAX-RS API has the following limitations that the Juneau Server API does not:

  • The ability to specify different media type providers at the class and method levels.
    For example, you may want to use JsonSerializer with one set of properties on one class, and another instance with different properties on another class.
    There is currently no way to define this at the class level.
    You can override properties at the method level, but this can be cumbersome since it would have to be done for all methods in the resource.
  • The Juneau Server API allows you to manipulate properties programatically through the {@link org.apache.juneau.rest.RestResponse#setProperty(String,Object)} method, and through the {@link org.apache.juneau.rest.annotation.Properties} annotation.
    There is no equivalent in JAX-RS.

4.1.4 - Using JAX-RS BaseProvider with annotations

To provide support for only JSON media types, you can define your own provider class, like so:

@Provider @Produces( "application/json,text/json,"+ // JsonSerializer "application/json+simple,text/json+simple,"+ // JsonSerializer.Simple "application/json+schema,text/json+schema" // JsonSchemaSerializer ) @Consumes( "application/json,text/json" // JsonParser ) @JuneauProvider( serializers={ JsonSerializer.class, JsonSerializer.Simple.class, JsonSchemaSerializer.class, }, parsers={ JsonParser.class, } properties={ @Property(name=SerializerContext.SERIALIZER_quoteChar, value="'") } ) public final class MyRdfProvider extends BaseProvider {}

Then register it with Wink the same way as DefaultProvider.

4.2 - REST client support

The {@link org.apache.juneau.rest.client.RestClient} class provides an easy-to-use REST client interface with pluggable media type handling using any of the Juneau serializers and parsers.
Defining a client to support JSON media types on HTTP requests and responses can be done in one line of code:

// Create a client to handle JSON requests and responses. RestClient client = new RestClientBuilder().build();

The client handles all content negotiation based on the registered serializers and parsers.

The following code is pulled from the main method of the ClientTest class in the sample web application, and is run against the AddressBookResource class running within the sample app.
It shows how the client can be used to interact with the REST API while completely hiding the negotiated content type and working with nothing more than beans.

Example:

String root = "http://localhost:9080/sample/addressBook"; // Get the current contents of the address book AddressBook ab = client.doGet(root).getResponse(AddressBook.class); System.out.println("Number of entries = " + ab.size()); // Delete the existing entries for (Person p : ab) { String r = client.doDelete(p.uri).getResponse(String.class); System.out.println("Deleted person " + p.name + ", response = " + r); } // Make sure they're gone ab = client.doGet(root).getResponse(AddressBook.class); System.out.println("Number of entries = " + ab.size()); // Add 1st person again CreatePerson cp = new CreatePerson( "Barack Obama", toCalendar("Aug 4, 1961"), new CreateAddress("1600 Pennsylvania Ave", "Washington", "DC", 20500, true), new CreateAddress("5046 S Greenwood Ave", "Chicago", "IL", 60615, false) ); Person p = client.doPost(root + "/people", cp).getResponse(Person.class); System.out.println("Created person " + p.name + ", uri = " + p.uri); // Add 2nd person again, but add addresses separately cp = new CreatePerson( "George Walker Bush", toCalendar("Jul 6, 1946") ); p = client.doPost(root + "/people", cp).getResponse(Person.class); System.out.println("Created person " + p.name + ", uri = " + p.uri); // Add addresses to 2nd person CreateAddress ca = new CreateAddress("43 Prairie Chapel Rd", "Crawford", "TX", 76638, true); Address a = client.doPost(p.uri + "/addresses", ca).getResponse(Address.class); System.out.println("Created address " + a.uri); ca = new CreateAddress("1600 Pennsylvania Ave", "Washington", "DC", 20500, false); a = client.doPost(p.uri + "/addresses", ca).getResponse(Address.class); System.out.println("Created address " + a.uri); // Find 1st person, and change name Person[] pp = client.doGet(root + "?q={name:\"'Barack+Obama'\"}").getResponse(Person[].class); String r = client.doPut(pp[0].uri + "/name", "Barack Hussein Obama").getResponse(String.class); System.out.println("Changed name, response = " + r); p = client.doGet(pp[0].uri).getResponse(Person.class); System.out.println("New name = " + p.name);

Results

Number of entries = 2 Deleted person Barack Obama, response = DELETE successful Deleted person George Walker Bush, response = DELETE successful Number of entries = 0 Created person Barack Obama, uri = http://localhost:9080/sample/addressBook/people/3 Created person George Walker Bush, uri = http://localhost:9080/sample/addressBook/people/4 Created address http://localhost:9080/sample/addressBook/addresses/7 Created address http://localhost:9080/sample/addressBook/addresses/8 Changed name, response = PUT successful New name = Barack Hussein Obama

*** fín ***