Responder for action domain responder(adr) pattern

0.4.1 2014-11-20 08:36 UTC


AbstractResponder of action domain responder by Paul M Jones.



It is installable and autoloadable via composer as foa/responder-bundle.

composer require foa/responder-bundle


Scrutinizer Code Quality Code Coverage Build Status

This library attempts to comply with PSR-1, PSR-2, and PSR-4. If you notice compliance oversights, please send a patch via pull request.


To ask questions, provide feedback, or otherwise communicate with the Aura community, please join our Google Group, follow @auraphp on Twitter, or chat with us on #auraphp on Freenode.

Example usage

It is recommend you first go through the action domain responder paper and example code.

In this examples we are using few aura components, but foa/responder-bundle is not specifically for Aura framework. You can integrate in any framework if you like the concept using its classes.

Consider you are having a blog application, which you can browse the posts. Let us see how it looks in ADR. You should pay special attention to responder only. Action and Service layer components may differ with what you are using.


// BlogBrowseAction.php
namespace Vendor\Blog\Web\Action;

use FOA\DomainPayload\PayloadFactory;
use Vendor\Blog\Web\Responder\BlogBrowseResponder;

class BlogBrowseAction
    protected $domain;
    protected $responder;

    public function __construct(
        BlogService $domain,
        BlogBrowseResponder $responder
    ) {
        $this->domain = $domain;
        $this->responder = $responder;

    public function __invoke()
        $payload_factory = new PayloadFactory();
        $payload = $payload_factory->found(
                array('title' => 'Some awesome title', 'author' => 'Hari KT'),
                array('title' => 'Some awesome post', 'author' => 'Paul M Jones'),
                array('title' => 'Some awesome content', 'author' => 'Justin'),
        // Rather than the above code, you should actually do something like
        // $payload = $this->domain->fetchPage($page, $paging);
        return $this->responder->__invoke();


// BlogBrowseResponder.php
namespace Vendor\Blog\Web\Responder;

use FOA\Responder_Bundle\AbstractResponder;

class BlogBrowseResponder extends AbstractResponder
    protected $available = array(
        'text/html' => '',
        'application/json' => '.json',

    protected $payload_method = array(
        'FOA\DomainPayload\Found' => 'display'

    public function display()
        if ($this->negotiateMediaType()) {
            $content_type = $this->response->content->getType();
            if ($content_type) {
                $view .= $this->available[$content_type];
            $this->renderView('browse', 'layout');

First instantiate your templating engine of choice. Eg usage with Aura.View. See other templating engines supported below.

$factory = new \Aura\Html\HelperLocatorFactory;
$helpers = $factory->newInstance();

$engine = new \Aura\View\View(
    new \Aura\View\TemplateRegistry,
    new \Aura\View\TemplateRegistry,

$renderer = new \FOA\Responder_Bundle\Renderer\AuraView($engine);

Create your responder object

$web_factory = new \Aura\Web\WebFactory($GLOBALS);
$response = $web_factory->newResponse();

$accept_factory = new \Aura\Accept\AcceptFactory($_SERVER);
$accept = $accept_factory->newInstance();

$responder = new \Vendor\Blog\Web\Responder\BlogBrowseResponder($accept, $response, $renderer);

Rendering and Setting content to response

use FOA\DomainPayload\PayloadFactory;

$payload_factory = new PayloadFactory();
$payload = $payload_factory->found(array('name' => 'Hari KT'));


Calling __invoke will render and set the content on the response object. Now you can either use Aura\Web\ResponseSender to send the response, or get the headers from response object and set to your favourite library response.

echo $response->content->get();

Aura framework integration with Aura.Di

In your project config/Common.php define method add the below lines.

$di->params['FOA\Responder_Bundle\Renderer\AuraView']['engine'] = $di->lazyNew('Aura\View\View');
// responder
$di->params['FOA\Responder_Bundle\AbstractResponder']['response'] = $di->lazyGet('aura/web-kernel:response');
$di->params['FOA\Responder_Bundle\AbstractResponder']['renderer'] = $di->lazyNew('FOA\Responder_Bundle\Renderer\AuraView');
$di->params['FOA\Responder_Bundle\AbstractResponder']['accept'] = $di->lazyNew('Aura\Accept\Accept');

Don't forget to change the renderer with the one you like.

Integrated templating engines

Responder bundle integrates below templating engines. Feel free to choose the one you love.

  1. aura/view
  2. league/plates
  3. mustache/mustache
  4. twig/twig
  5. smarty/smarty

Integrating other templating engines

namespace FOA\Responder_Bundle\Renderer;

use FOA\Responder_Bundle\Renderer\RendererInterface;
use Your\TemplateEngine;

class YourTemplateEngine implements RendererInterface
    public function __construct(TemplateEngine $engine)
        $this->engine = $engine;

    public function render($data, $view, $layout = null)
        // according to how the rendering engine works. See other implementations
        // $this->engine->render

Yes, and we love tests!.