This command line tool asks Doctrine to introspect the database and generate

the XML metadata files under the ``src/Acme/BlogBundle/Resources/config/doctrine``

folder of your bundle.

folder of your bundle. This generates two files: ``BlogPost.orm.xml`` and

``BlogComment.orm.xml``.

..tip::

It's also possible to generate metadata class in YAML format by changing the

first argument to `yml`.

first argument to ``yml``.

The generated ``BlogPost.orm.xml`` metadata file looks as follows:

..code-block::xml

Then you should insert proper namespace in ``name`` attribute of ``entity`` element like this:

Update the namespace in the ``name`` attribute of the ``entity`` element like

this:

..code-block::xml

..note::

If you have ``oneToMany`` relationships between your entities,

you will need to edit the generated ``xml`` or ``yml`` files to add

a section on the specific entities for ``oneToMany`` defining the

``inversedBy`` and the ``mappedBy`` pieces.

Once the metadata files are generated, you can ask Doctrine to build related entity classes by executing the following two commands.

Once the metadata files are generated, you can ask Doctrine to build related

entity classes by executing the following two commands.

..code-block::bash

The first command generates entity classes with an annotations mapping. But if you want to use yml or xml mapping instead of annotations, you should execute the second command only.

The newly created ``BlogComment`` entity class looks as follow:

The first command generates entity classes with an annotations mapping. But

if you want to use yml or xml mapping instead of annotations, you should

execute the second command only.

..tip::

..code-block::php

If you want to use annotations, you can safely delete the XML files after

running these two commands.

Consequently, you can find a private ``$post`` property mapped with a ``BlogPost``

entity in the ``BlogComment`` entity class.

The last command generated all getters and setters for your two ``BlogPost`` and

``BlogComment`` entity class properties. The generated entities are now ready to be

used. Have fun!

..note::

If you want to have a ``oneToMany`` relationship, you will need to add

it manually into the entity or to the generated ``xml`` or ``yml`` files.

Add a section on the specific entities for ``oneToMany`` defining the

``inversedBy`` and the ``mappedBy`` pieces.

The generated entities are now ready to be used. Have fun!

.. _`Doctrine tools documentation`:http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/tools.html#reverse-engineering