Removing all "Sensio" namespace references to "Acme" so that we're consistent across the board

The Sensio namespace is legitimately used in the standard distribution, meaning if you try to start playing around with with the standard distribution using using the Sensio namespace, you'll have extra autoloading difficulties

Author: weaverryan

book/bundles.rst

@@ -37,9 +37,9 @@ Here are some valid bundle namespaces and class names:
 =================================== ==============================
 Namespace Bundle Class Name
 =================================== ==============================
-``Sensio\Bundle\BlogBundle`` ``SensioBlogBundle``
-``Sensio\Bundle\Social\BlogBundle`` ``SensioSocialBlogBundle``
-``Sensio\BlogBundle`` ``SensioBlogBundle``
+``Acme\Bundle\BlogBundle``  ``AcmeBlogBundle``
+``Acme\Bundle\Social\BlogBundle``  ``AcmeSocialBlogBundle``
+``Acme\BlogBundle``  ``AcmeBlogBundle``
 =================================== ==============================
 
 By convention, the ``getName()`` method of the bundle class should return the
@@ -48,7 +48,7 @@ class name.
 .. note::
 
  If you share your bundle publicly, you must use the bundle class name as
- the name of the repository (``SensioBlogBundle`` and not ``BlogBundle``
+ the name of the repository (``AcmeBlogBundle`` and not ``BlogBundle``
  for instance).
 
 Directory Structure
@@ -203,8 +203,8 @@ using the Symfony2 built-in mechanisms.
 For simple configuration settings, rely on the default ``parameters`` entry of
 the Symfony2 configuration. Symfony2 parameters are simple key/value pairs; a
 value being any valid PHP value. Each parameter name must start with a
-lower-cased version of the bundle name (``hello`` for ``HelloBundle``, or
-``sensio.social.blog`` for ``Sensio\Social\BlogBundle`` for instance).
+lower-cased version of the bundle name (``acme.hello`` for ``AcmeHelloBundle``,
+or ``sensio.social.blog`` for ``Acme\Social\BlogBundle`` for instance).
 
 The end user can provide values in any configuration file:
 

book/controller.rst

@@ -81,9 +81,9 @@ object. Controllers are also called *actions*.
 
 .. code-block:: php
 
- // src/Sensio/HelloBundle/Controller/HelloController.php
+ // src/Acme/HelloBundle/Controller/HelloController.php
 
- namespace Sensio\HelloBundle\Controller;
+ namespace Acme\HelloBundle\Controller;
  use Symfony\Component\HttpFoundation\Response;
 
  class HelloController
@@ -138,21 +138,21 @@ but let's create a simple route to our controller:
 
  .. code-block:: yaml
 
- # src/Sensio/HelloBundle/Resources/config/routing.yml
+ # src/Acme/HelloBundle/Resources/config/routing.yml
  hello:
  pattern: /hello/{name}
  defaults: { _controller: Hello:Hello:index }
 
  .. code-block:: xml
 
- <!-- src/Sensio/HelloBundle/Resources/config/routing.xml -->
+ <!-- src/Acme/HelloBundle/Resources/config/routing.xml -->
  <route id="hello" pattern="/hello/{name}">
  <default key="_controller">Hello:Hello:index</default>
  </route>
 
  .. code-block:: php
 
- // src/Sensio/HelloBundle/Resources/config/routing.php
+ // src/Acme/HelloBundle/Resources/config/routing.php
  $collection->add('hello', new Route('/hello/{name}', array(
  '_controller' => 'Hello:Hello:index',
  )));
@@ -195,9 +195,9 @@ passed to that method:
 .. code-block:: php
 
  <?php
- // src/Sensio/HelloBundle/Controller/HelloController.php
+ // src/Acme/HelloBundle/Controller/HelloController.php
 
- namespace Sensio\HelloBundle\Controller;
+ namespace Acme\HelloBundle\Controller;
  use Symfony\Bundle\FrameworkBundle\Controller\Controller;
 
  class HelloController extends Controller
@@ -218,22 +218,22 @@ example:
 
  .. code-block:: yaml
 
- # src/Sensio/HelloBundle/Resources/config/routing.yml
+ # src/Acme/HelloBundle/Resources/config/routing.yml
  hello:
  pattern: /hello/{first_name}/{last_name}
  defaults: { _controller: Hello:Hello:index, color: green }
 
  .. code-block:: xml
 
- <!-- src/Sensio/HelloBundle/Resources/config/routing.xml -->
+ <!-- src/Acme/HelloBundle/Resources/config/routing.xml -->
  <route id="hello" pattern="/hello/{first_name}/{last_name}">
  <default key="_controller">Hello:Hello:index</default>
  <default key="color">green</default>
  </route>
 
  .. code-block:: php
 
- // src/Sensio/HelloBundle/Resources/config/routing.php
+ // src/Acme/HelloBundle/Resources/config/routing.php
  $collection->add('hello', new Route('/hello/{first_name}/{last_name}', array(
  '_controller' => 'Hello:Hello:index',
  'color' => 'green',
@@ -320,9 +320,9 @@ Add the ``use`` statement atop the ``Controller`` class and then modify the
 
 .. code-block:: php
 
- // src/Sensio/HelloBundle/Controller/HelloController.php
+ // src/Acme/HelloBundle/Controller/HelloController.php
 
- namespace Sensio\HelloBundle\Controller;
+ namespace Acme\HelloBundle\Controller;
  use Symfony\Bundle\FrameworkBundle\Controller\Controller;
  use Symfony\Component\HttpFoundation\Response;
 

book/doctrine/mongodb-odm/configuration.rst

@@ -93,8 +93,8 @@ can control. The following configuration options exist for a mapping:
  share. This prefix should never conflict with prefixes of other defined
  mappings otherwise some of your documents cannot be found by Doctrine. This
  option defaults to the bundle namespace + ``Document``, for example for an
- application bundle called "HelloBundle" prefix would be
- ``Sensio\HelloBundle\Document``.
+ application bundle called ``AcmeHelloBundle``, the prefix would be
+ ``Acme\HelloBundle\Document``.
 - ``alias`` Doctrine offers a way to alias document namespaces to simpler,
  shorter names to be used in queries or for Repository access.
 - ``is_bundle`` This option is a derived value from ``dir`` and by default is
@@ -107,7 +107,7 @@ To avoid having to configure lots of information for your mappings you should
 follow these conventions:
 
 1. Put all your entities in a directory ``Document/`` inside your bundle. For
- example ``Sensio/HelloBundle/Document/``.
+ example ``Acme/HelloBundle/Document/``.
 2. If you are using xml, yml or php mapping put all your configuration files
  into the ``Resources/config/doctrine/metadata/doctrine/mongodb/`` directory
  suffixed with dcm.xml, dcm.yml or dcm.php respectively.
@@ -244,9 +244,9 @@ First, let's write a simple User class.
 
 .. code-block:: php
 
- // src/Sensio/HelloBundle/Document/User.php
+ // src/Acme/HelloBundle/Document/User.php
 
- namespace Sensio\HelloBundle\Document;
+ namespace Acme\HelloBundle\Document;
 
  class User
  {

book/doctrine/mongodb-odm/overview.rst

@@ -33,9 +33,9 @@ yaml.
 
  .. code-block:: php-annotations
 
- // Sensio/HelloBundle/Document/User.php
+ // Acme/HelloBundle/Document/User.php
 
- namespace Sensio\HelloBundle\Document;
+ namespace Acme\HelloBundle\Document;
 
  /**
  * @mongodb:Document(collection="users")
@@ -85,8 +85,8 @@ yaml.
 
  .. code-block:: yaml
 
- # Sensio/HelloBundle/Resources/config/doctrine/metadata/mongodb/Sensio.HelloBundle.Document.User.dcm.yml
- Sensio\HelloBundle\Document\User:
+ # Acme/HelloBundle/Resources/config/doctrine/metadata/mongodb/Acme.HelloBundle.Document.User.dcm.yml
+ Acme\HelloBundle\Document\User:
  type: document
  collection: user
  fields:
@@ -98,13 +98,13 @@ yaml.
 
  .. code-block:: xml
 
- <!-- Sensio/HelloBundle/Resources/config/doctrine/metadata/mongodb/Sensio.HelloBundle.Document.User.dcm.xml -->
+ <!-- Acme/HelloBundle/Resources/config/doctrine/metadata/mongodb/Acme.HelloBundle.Document.User.dcm.xml -->
  <doctrine-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-mapping"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mapping
  http://doctrine-project.org/schemas/orm/doctrine-mapping.xsd">
 
- <document name="Sensio\HelloBundle\Document\User" collection="user">
+ <document name="Acme\HelloBundle\Document\User" collection="user">
  <field name="id" id="true" />
  <field name="name" type="string" length="255" />
  </document>
@@ -126,7 +126,7 @@ Now, use your document and manage its persistent state with Doctrine:
 
 .. code-block:: php
 
- use Sensio\HelloBundle\Document\User;
+ use Acme\HelloBundle\Document\User;
 
  class UserController extends Controller
  {

book/doctrine/orm/configuration.rst

@@ -80,8 +80,8 @@ can control. The following configuration options exist for a mapping:
  share. This prefix should never conflict with prefixes of other defined
  mappings otherwise some of your entities cannot be found by Doctrine. This
  option defaults to the bundle namespace + ``Entity``, for example for an
- application bundle called "HelloBundle" prefix would be
- ``Sensio\HelloBundle\Entity``.
+ application bundle called ``AcmeHelloBundle`` prefix would be
+ ``Acme\HelloBundle\Entity``.
 - ``alias`` Doctrine offers a way to alias entity namespaces to simpler,
  shorter names to be used in DQL queries or for Repository access. When using a
  bundle the alias defaults to the bundle name.
@@ -95,7 +95,7 @@ To avoid having to configure lots of information for your mappings you should
 follow these conventions:
 
 1. Put all your entities in a directory ``Entity/`` inside your bundle. For
- example ``Sensio/HelloBundle/Entity/``.
+ example ``Acme/HelloBundle/Entity/``.
 2. If you are using xml, yml or php mapping put all your configuration files
  into the "Resources/config/doctrine/metadata/doctrine/orm/" directory
  suffixed with dcm.xml, dcm.yml or dcm.php respectively.

book/doctrine/orm/form.rst

@@ -17,7 +17,7 @@ choices from which an entity can be selected.
 
  $field = new EntityChoiceField('users', array(
  'em' => $em,
- 'class' => 'Sensio\\HelloBundle\\Entity\\User',
+ 'class' => 'Acme\\HelloBundle\\Entity\\User',
  'property' => 'username',
  'query_builder' => $qb,
  ));

book/doctrine/orm/overview.rst

@@ -59,8 +59,8 @@ any PHP class:
 
 .. code-block:: php
 
- // Sensio/HelloBundle/Entity/User.php
- namespace Sensio\HelloBundle\Entity;
+ // Acme/HelloBundle/Entity/User.php
+ namespace Acme\HelloBundle\Entity;
 
  class User
  {
@@ -97,8 +97,8 @@ write mapping information with annotations, XML, or YAML:
 
  .. code-block:: php-annotations
 
- // Sensio/HelloBundle/Entity/User.php
- namespace Sensio\HelloBundle\Entity;
+ // Acme/HelloBundle/Entity/User.php
+ namespace Acme\HelloBundle\Entity;
 
  /**
  * @orm:Entity
@@ -120,8 +120,8 @@ write mapping information with annotations, XML, or YAML:
 
  .. code-block:: yaml
 
- # Sensio/HelloBundle/Resources/config/doctrine/metadata/orm/Sensio.HelloBundle.Entity.User.dcm.yml
- Sensio\HelloBundle\Entity\User:
+ # Acme/HelloBundle/Resources/config/doctrine/metadata/orm/Acme.HelloBundle.Entity.User.dcm.yml
+ Acme\HelloBundle\Entity\User:
  type: entity
  table: user
  id:
@@ -136,13 +136,13 @@ write mapping information with annotations, XML, or YAML:
 
  .. code-block:: xml
 
- <!-- Sensio/HelloBundle/Resources/config/doctrine/metadata/orm/Sensio.HelloBundle.Entity.User.dcm.xml -->
+ <!-- Acme/HelloBundle/Resources/config/doctrine/metadata/orm/Acme.HelloBundle.Entity.User.dcm.xml -->
  <doctrine-mapping xmlns="http://doctrine-project.org/schemas/orm/doctrine-mapping"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://doctrine-project.org/schemas/orm/doctrine-mapping
  http://doctrine-project.org/schemas/orm/doctrine-mapping.xsd">
 
- <entity name="Sensio\HelloBundle\Entity\User" table="user">
+ <entity name="Acme\HelloBundle\Entity\User" table="user">
  <id name="id" type="integer" column="id">
  <generator strategy="AUTO"/>
  </id>
@@ -174,10 +174,10 @@ Eventually, use your entity and manage its persistent state with Doctrine:
 
 .. code-block:: php
 
- // Sensio/HelloBundle/Controller/UserController.php
- namespace Sensio\HelloBundle\Controller;
+ // Acme/HelloBundle/Controller/UserController.php
+ namespace Acme\HelloBundle\Controller;
 
- use Sensio\HelloBundle\Entity\User;
+ use Acme\HelloBundle\Entity\User;
 
  class UserController extends Controller
  {
@@ -222,7 +222,7 @@ entity:
 
 .. code-block:: php
 
- namespace Sensio\HelloBundle\Entity;
+ namespace Acme\HelloBundle\Entity;
 
  /** @orm:Entity */
  class User