Merge pull request #6 from decebals/jackson

Add pippo-jackson to ContentTypeEngines document

Author: decebals

_posts/2015-04-02-content-types.md

@@ -9,11 +9,11 @@ order: 55
 When we send a Response to the client we must specify the content type. In most cases the content type is __html__ (`text/html`) but are situations (for example a REST application/module)
 when we want to return __plain text__ (`text/plain`) or __json__ (`application/json`) or __xml__ (`application/xml`) or __yaml__ (`application/x-yaml`).  
 To resolve these situations Pippo comes with a nice concept [ContentTypeEngine]({{ site.coreurl }}/src/main/java/ro/pippo/core/ContentTypeEngine.java).  
-Pippo comes bultin (direct or via modules) with the following content type engines: 
+Pippo comes bultin (direct or via modules) with the following content type engines:
 
 - plain text ([TextPlainEngine]({{ site.coreurl }}/src/main/java/ro/pippo/core/TextPlainEngine.java))
 - xml ([JaxbEngine]({{ site.coreurl }}/src/main/java/ro/pippo/core/JaxbEngine.java), [XstreamEngine]({{ site.codeurl }}/pippo-xstream/src/main/java/ro/pippo/xstream/XstreamEngine.java))
-- json ([GsonEngine]({{ site.codeurl }}/pippo-gson/src/main/java/ro/pippo/gson/GsonEngine.java), [FastjsonEngine]({{ site.codeurl }}/pippo-fastjson/src/main/java/ro/pippo/fastjson/FastjsonEngine.java))
+- json ([GsonEngine]({{ site.codeurl }}/pippo-gson/src/main/java/ro/pippo/gson/GsonEngine.java), [FastjsonEngine]({{ site.codeurl }}/pippo-fastjson/src/main/java/ro/pippo/fastjson/FastjsonEngine.java), [JacksonEngine]({{ site.codeurl }}/pippo-jackson/src/main/java/ro/pippo/jackson/JacksonEngine.java))
 - yaml ([SnakeYamlEngine]({{ site.codeurl }}/pippo-snakeyaml/src/main/java/ro/pippo/snakeyaml/SnakeYamlEngine.java))
 
 If you want to develop a new engine of content type you can do it very easily. All you have to do is to implement ContentTypeEngine.  
@@ -51,7 +51,7 @@ To register a content type engine in your application you have two options:
 - add programatically the content type engine in `Application.onInit()` with `Application.registerContentTypeEngine(XstreamEngine.class)`
 - create an [Initializer]({{ site.coreurl }}/src/main/java/ro/pippo/core/Initializer.java) in your project that register the content type engine
 
-For above _XstreamEngine_ we can create an _XstreamInitializer_ with this possible content: 
+For above _XstreamEngine_ we can create an _XstreamInitializer_ with this possible content:
 
 ```java
 public class XstreamInitializer implements Initializer {
@@ -88,9 +88,9 @@ public class BasicApplication extends Application {
 			.setId(12345)
 			.setName("John")
 			.setPhone("0733434435")
-			.setAddress("Sunflower Street, No. 6");	
+			.setAddress("Sunflower Street, No. 6");
 	}
-	
+
 }
 ```
 
@@ -100,7 +100,7 @@ header may also be used if an agreeable content type engine can not be determine
 If no Content-Type can not be negotiated then the response will not be modified. This behavior allows specification of a default Content-Type
 using one of the methods such as `xml()` or `json()`.
 
-See below an example related to content type negotiation: 
+See below an example related to content type negotiation:
 
 ```java
 public class BasicApplication extends Application {
@@ -120,4 +120,3 @@ public class BasicApplication extends Application {
 In above example `routeContext.xml().negotiateContentType().send(contact)` would set the default Content-Type as `application/xml` and
 then attempt to negotiate the client's preferred type. If negotiation failed, then the default `application/xml` would be sent and used to
 serialize the outgoing object.  
-