Commits on May 9, 2011
  1. Merge pull request #1 from mcbennn/master

    kriswallsmith committed May 9, 2011
    Fixes setApplicationEntityManager call
Commits on Mar 17, 2011
  1. [Config] Component refactoring

    vicb committed Mar 14, 2011
    The Config component API have changed and the extension configuration files must be updated accordingly:
    1. Array nodes must enclosed their children definition in ->children() ... ->end() calls:
        $treeBuilder->root('zend', 'array')
        $treeBuilder->root('zend', 'array')
    2. The 'builder' method (in NodeBuilder) has been dropped in favor of an 'append' method (in ArrayNodeDefinition)
        $treeBuilder->root('doctrine', 'array')
        $treeBuilder->root('doctrine', 'array')
    3. The root of a TreeBuilder is now an NodeDefinition (and most probably an ArrayNodeDefinition):
        $root = $treeBuilder->root('doctrine', 'array');
        public function addDbalSection(NodeBuilder $node)
        $root = $treeBuilder->root('doctrine', 'array');
        public function addDbalSection(ArrayNodeDefinition $node)
    4. The NodeBuilder API has changed (this is seldom used):
        $node = new NodeBuilder('connections', 'array');
    The recommended way is to use a tree builder:
        $treeBuilder = new TreeBuilder();
        $node = $treeBuilder->root('connections', 'array');
    An other way would be:
        $builder = new NodeBuilder();
        $node = $builder->node('connections', 'array');
    Some notes:
    - Tree root nodes should most always be array nodes, so this as been made the default:
        $treeBuilder->root('doctrine', 'array') is equivalent to $treeBuilder->root('doctrine')
    - There could be more than one ->children() ... ->end() sections. This could help with the readability:
Commits on Mar 16, 2011
Commits on Mar 11, 2011
Commits on Mar 6, 2011
Commits on Feb 20, 2011
  1. added a DI extension for DoctrineMigrations, removed --bundle option …

    lsmith77 committed Feb 20, 2011
    …in favor of application level settings
Commits on Feb 19, 2011
Commits on Feb 5, 2011
Commits on Feb 4, 2011
  1. fixed previous commit

    fabpot committed Feb 4, 2011
  2. [Bundle] Make getPath() less error prone by allowing both backward an…

    vicb authored and fabpot committed Jan 29, 2011
    …d forward slashes
Commits on Feb 3, 2011
Commits on Jan 24, 2011
Commits on Jan 20, 2011
  1. refactored bundle management

    fabpot committed Jan 18, 2011
    Before I explain the changes, let's talk about the current state.
    Before this patch, the registerBundleDirs() method returned an ordered (for
    resource overloading) list of namespace prefixes and the path to their
    location. Here are some problems with this approach:
     * The paths set by this method and the paths configured for the autoloader
       can be disconnected (leading to unexpected behaviors);
     * A bundle outside these paths worked, but unexpected behavior can occur;
     * Choosing a bundle namespace was limited to the registered namespace
       prefixes, and their number should stay low enough (for performance reasons)
       -- moreover the current Bundle\ and Application\ top namespaces does not
       respect the standard rules for namespaces (first segment should be the
       vendor name);
     * Developers must understand the concept of "namespace prefixes" to
       understand the overloading mechanism, which is one more thing to learn,
       which is Symfony specific;
     * Each time you want to get a resource that can be overloaded (a template for
       instance), Symfony would have tried all namespace prefixes one after the
       other until if finds a matching file. But that can be computed in advance
       to reduce the overhead.
    Another topic which was not really well addressed is how you can reference a
    file/resource from a bundle (and take into account the possibility of
    overloading). For instance, in the routing, you can import a file from a
    bundle like this:
      <import resource="FrameworkBundle/Resources/config/internal.xml" />
    Again, this works only because we have a limited number of possible namespace
    This patch addresses these problems and some more.
    First, the registerBundleDirs() method has been removed. It means that you are
    now free to use any namespace for your bundles. No need to have specific
    prefixes anymore. You are also free to store them anywhere, in as many
    directories as you want. You just need to be sure that they are autoloaded
    The bundle "name" is now always the short name of the bundle class (like
    FrameworkBundle or SensioCasBundle). As the best practice is to prefix the
    bundle name with the vendor name, it's up to the vendor to ensure that each
    bundle name is unique. I insist that a bundle name must be unique. This was
    the opposite before as two bundles with the same name was how Symfony2 found
    A new getParent() method has been added to BundleInterface. It returns the
    bundle name that the bundle overrides (this is optional of course). That way,
    there is no ordering problem anymore as the inheritance tree is explicitely
    defined by the bundle themselves.
    So, with this system, we can easily have an inheritance tree like the
    FooBundle < MyFooBundle < MyCustomFooBundle
    MyCustomFooBundle returns MyFooBundle for the getParent() method, and
    MyFooBundle returns FooBundle.
    If two bundles override the same bundle, an exception is thrown.
    Based on the bundle name, you can now reference any resource with this
    This notation is the input of the Kernel::locateResource() method, which
    returns the location of the file (and of course it takes into account
    So, in the routing, you can now use the following:
        <import resource="@FrameworkBundle/Resources/config/internal.xml" />
    The template loading mechanism also use this method under the hood.
    As a bonus, all the code that converts from internal notations to file names
    (controller names: ControllerNameParser, template names: TemplateNameParser,
    resource paths, ...) is now contained in several well-defined classes. The
    same goes for the code that look for templates (TemplateLocator), routing
    files (FileLocator), ...
    As a side note, it is really easy to also support multiple-inheritance for a
    bundle (for instance if a bundle returns an array of bundle names it extends).
    However, this is not implemented in this patch as I'm not sure we want to
    support that.
    How to upgrade:
     * Each bundle must now implement two new mandatory methods: getPath() and
       getNamespace(), and optionally the getParent() method if the bundle extends
       another one. Here is a common implementation for these methods:
         * {@inheritdoc}
        public function getParent()
            return 'MyFrameworkBundle';
         * {@inheritdoc}
        public function getNamespace()
            return __NAMESPACE__;
         * {@inheritdoc}
        public function getPath()
            return strtr(__DIR__, '\\', '/');
     * The registerBundleDirs() can be removed from your Kernel class;
     * If your code relies on getBundleDirs() or the kernel.bundle_dirs parameter,
       it should be upgraded to use the new interface (see Doctrine commands for
       many example of such a change);
     * When referencing a bundle, you must now always use its name (no more \ or /
       in bundle names) -- this transition was already done for most things
       before, and now applies to the routing as well;
     * Imports in routing files must be changed:
        Before: <import resource="Sensio/CasBundle/Resources/config/internal.xml" />
        After:  <import resource="@SensioCasBundle/Resources/config/internal.xml" />
Commits on Jan 18, 2011
  1. normalized license messages in PHP files

    blue-eyes authored and fabpot committed Jan 15, 2011
Commits on Nov 27, 2010
  1. [Command] Changing the InputOption::PARAMETER_* constants to InputOpt…

    weaverryan authored and fabpot committed Nov 27, 2010
    …ion::VALUE_* to more accurately reflect that these constants refer to the value or lack of value assigned to a particular option (e.g. --verbose or --em=doctrine).
    To keep language consistent, three methods were changed in InputOption:
     * `InputOption::acceptParameter()` -> `InputOption::acceptValue()`
     * `InputOption::isParameterRequired()` -> InputOption::isValueRequired()`
     * `InputOption::isParameterOptional()` -> `InputOption::isValueOptional()`
    The InputDefinition::asXml() method was also modified to update the `accept_value` and `is_value_required` attributes.
Commits on Oct 18, 2010
Commits on Sep 17, 2010
  1. removed Symfony\Framework

    fabpot committed Sep 15, 2010
    Things have been moved to Symfony\Component\HttpKernel
    and Symfony\Bundle\FrameworkBundle
    The kernel configuration namespace was removed and merged
    with the main web configuration namespace (kernel:config => web:config,
    kernel:test => web:test, and kernel:session => web:session):
    <kernel:config charset="UTF-8" error_handler="null" />
    <web:config csrf-secret="xxxxxxxxxx">
        <web:router resource="%kernel.root_dir%/config/routing.xml" />
        <web:validation enabled="true" annotations="true" />
    <web:config csrf-secret="xxxxxxxxxx" charset="UTF-8" error-handler="null">
        <web:router resource="%kernel.root_dir%/config/routing.xml" />
        <web:validation enabled="true" annotations="true" />
    Renamed classes:
    Symfony\{Framework => Bundle\FrameworkBundle}\Cache\Cache
    Symfony\{Framework => Bundle\FrameworkBundle}\Client
    Symfony\{Framework => Bundle\FrameworkBundle}\Debug\EventDispatcher
    Symfony\{Framework => Bundle\FrameworkBundle}\Debug\EventDispatcherTraceableInterface
    Symfony\{Framework => Bundle\FrameworkBundle}\EventDispatcher
    Symfony\{Framework => Component\HttpFoundation}\UniversalClassLoader
    Symfony\{Framework => Component\HttpKernel}\Bundle\Bundle
    Symfony\{Framework => Component\HttpKernel}\Bundle\BundleInterface
    Symfony\{Framework => Component\HttpKernel}\ClassCollectionLoader
    Symfony\{Framework => Component\HttpKernel}\Debug\ErrorException
    Symfony\{Framework => Component\HttpKernel}\Debug\ErrorHandler
    Symfony\{Bundle\FrameworkBundle => Component\HttpKernel}\Debug\ExceptionListener
    Symfony\{Framework => Component\HttpKernel}\Kernel
Commits on Aug 20, 2010
Commits on Aug 1, 2010
Commits on Jul 9, 2010
  1. renamed Symfony\Foundation to Symfony\Framework

    fabpot committed Jul 9, 2010
    In existing applications, you need to updated the autoload.php file, the
    XXXKernel file and all XXXBundle classes.
  2. renamed Symfony\Framework to Symfony\Bundle

    fabpot committed Jul 9, 2010
    For existing Symfony2 applications, references to Symfony\Framework are found
    in the main Kernel class (registerBundles() and registerBundleDirs()), and in
    all Controller classes. You also need to change the console script.