JSON and XML views

By enabling RequestHandlerComponent in your application, and enablingsupport for the json and/or xml extensions, you can automaticallyleverage the new view classes. JsonView and XmlView will be referred toas data views for the rest of this page.

There are two ways you can generate data views. The first is by using the_serialize key, and the second is by creating normal template files.

Before you can use the data view classes, you’ll first need to load theCake\Controller\Component\RequestHandlerComponent in yourcontroller:

This can be done in your AppController and will enable automatic view classswitching on content types. You can also set the component up with theviewClassMap setting, to map types to your custom classes and/or map otherdata types.

You can optionally enable the json and/or xml extensions withRouting File Extensions. This will allow you to access the JSON, XML orany other special format views by using a custom URL ending with the name of theresponse type as a file extension such as .

Using Data Views with the Serialize Key

The _serialize key is a special view variable that indicates which otherview variable(s) should be serialized when using a data view. This lets you skipdefining template files for your controller actions if you don’t need to do anycustom formatting before your data is converted into json/xml.

If you need to do any formatting or manipulation of your view variables beforegenerating the response, you should use template files. The value of_serialize can be either a string or an array of view variables toserialize:

namespace App\Controller;
 
class ArticlesController extends AppController
{
    public function initialize()
    {
        parent::initialize();
        $this->loadComponent('RequestHandler');
 
    public function index()
    {
        // Set the view vars that have to be serialized.
        $this->set('articles', $this->paginate());
        // Specify which view vars JsonView should serialize.
        $this->set('_serialize', 'articles');
    }
}

You can also define _serialize as an array of view variables to combine:

Defining _serialize as an array has added the benefit of automaticallyappending a top-level <response> element when using .If you use a string value for _serialize and XmlView, make sure that yourview variable has a single top-level element. Without a single top-levelelement the Xml will fail to generate.

You should use template files if you need to do some manipulation of your viewcontent before creating the final output. For example if we had articles, that hada field containing generated HTML, we would probably want to omit that from aJSON response. This is a situation where a view file would be useful:

// Controller code
class ArticlesController extends AppController
{
    public function index()
    {
        $articles = $this->paginate('Articles');
    }
}
 
// View code - src/Template/Articles/json/index.ctp
foreach ($articles as &$article) {
    unset($article->generated_html);
}
echo json_encode(compact('articles'));

Note

As of 3.1.0 until 3.5.0, AppController in the application skeleton automatically added'_serialize' => true to all XML/JSON requests. You will need to removethis code from the beforeRender callback or set '_serialize' => false inyour controller’s action if you want to use view files.

Creating XML Views

• class XmlView
• By default when using _serialize the XmlView will wrap your serializedview variables with a node. You can set a custom name forthis node using the _rootNode view variable.

The XmlView class supports the _xmlOptions variable that allows you tocustomize the options used to generate XML, e.g. tags vs attributes.

An example of using XmlView would be to generate a sitemap.xml. This document type requires that youchange _rootNode and set attributes. Attributes are defined using the @prefix:

• class JsonView
• The JsonView class supports the _jsonOptions variable that allows you tocustomize the bit-mask used to generate JSON. See thejson_encode documentation for the validvalues of this option.

For example, to serialize validation error output of CakePHP entities in a consistent form of JSON do:

// In your controller's action when saving failed
$this->set('errors', $articles->errors());
$this->set('_jsonOptions', JSON_FORCE_OBJECT);

Example Usage

While the RequestHandlerComponent can automatically set the view basedon the request content-type or extension, you could also handle viewmappings in your controller: