The Symfony CMF Book

1
2
3
4
# app/config/config.yml
cmf_routing:
dynamic:
enabled: true
This is the minimum configuration required to load the DynamicRouter as a service, thus making
it capable of performing any routing. Actually, when you browse the default pages that come with
the Symfony CMF SE, it is the DynamicRouter that matches your requests with the Controllers and
Templates.
Getting the Route Object
The provider to use can be configured to best suit each implementation's needs, and must implement
the RouteProviderInterface. As part of this bundle, an implementation for PHPCR-ODM 2 is provided.
Also, you can easily create your own, as the Router itself is storage agnostic. The default provider loads
the route at the path in the request and all parent paths to allow for some of the path segments being
parameters.
For more detailed information on this implementation and how you can customize or extend it, refer to
The RoutingBundle.
The DynamicRouter is able to match the incoming request to a Route object from the underlying
provider. The details on how this matching process is carried out can be found in the Routing.
To have the route provider find routes, you also need to provide the data in your storage. With
PHPCR-ODM, this is either done through the admin interface (see at the bottom) or with fixtures.
However, before we can explain how to do that, you need to understand how the DynamicRouter
works. An example will come later in this document.
Getting the Controller and Template
A Route needs to specify which Controller should handle a specific Request. The DynamicRouter uses
one of several possible methods to determine it (in order of precedence):
• Explicit: The stored Route document itself can explicitly declare the target Controller by
specifying the '_controller' value in getRouteDefaults().
• By alias: the Route returns a 'type' value in getRouteDefaults(), which is then matched
against the provided configuration from config.yml
• By class: requires the Route instance to implement RouteObjectInterface and return an
object for getRouteContent(). The returned class type is then matched against the provided
configuration from config.yml.
• Default: if configured, a default Controller will be used.
Apart from this, the DynamicRouter is also capable of dynamically specifying which Template will be
used, in a similar way to the one used to determine the Controller (in order of precedence):
• Explicit: The stored Route document itself can explicitly declare the target Template in
getRouteDefaults().
• By class: requires the Route instance to implement RouteObjectInterface and return an
object for getRouteContent(). The returned class type is then matched against the provided
configuration from config.yml.
Here's an example of how to configure the above mentioned options:
2. https://github.com/doctrine/phpcr-odm
PDF brought to you by
generated on June 13, 2013
Chapter 2: Routing | 10