Metadata Drivers ================ The heart of an object mapper is the mapping information that glues everything together. It instructs the DocumentManager how it should behave when dealing with the different documents. Core Metadata Drivers --------------------- Doctrine provides a few different ways for you to specify your metadata: - **XML files** (XmlDriver) - **Class DocBlock Annotations** (AnnotationDriver) - **YAML files** (YamlDriver) - **PHP Code in files or static functions** (PhpDriver) Something important to note about the above drivers is they are all an intermediate step to the same end result. The mapping information is populated to ``Doctrine\ODM\MongoDB\Mapping\ClassMetadata`` instances. So in the end, Doctrine only ever has to work with the API of the ``ClassMetadata`` class to get mapping information for a document. .. note:: The populated ``ClassMetadata`` instances are also cached so in a production environment the parsing and populating only ever happens once. You can configure the metadata cache implementation using the ``setMetadataCacheImpl()`` method on the ``Doctrine\ODM\MongoDB\Configuration`` class: .. code-block:: php getConfiguration()->setMetadataCacheImpl(new ApcCache()); If you want to use one of the included core metadata drivers you just need to configure it. All the drivers are in the ``Doctrine\ODM\MongoDB\Mapping\Driver`` namespace: .. code-block:: php getConfiguration()->setMetadataDriverImpl($driver); Implementing Metadata Drivers ----------------------------- In addition to the included metadata drivers you can very easily implement your own. All you need to do is define a class which implements the ``Driver`` interface: .. code-block:: php _loadMappingFile($file); // populate ClassMetadataInfo instance from $data } /** * {@inheritdoc} */ protected function _loadMappingFile($file) { // parse contents of $file and return php data structure } } .. note:: When using the ``AbstractFileDriver`` it requires that you only have one document defined per file and the file named after the class described inside where namespace separators are replaced by periods. So if you have a document named ``Documents\User`` and you wanted to write a mapping file for your driver above you would need to name the file ``Documents.User.dcm.ext`` for it to be recognized. Now you can use your ``MyMetadataDriver`` implementation by setting it with the ``setMetadataDriverImpl()`` method: .. code-block:: php getConfiguration()->setMetadataDriverImpl($driver); ClassMetadata ------------- The last piece you need to know and understand about metadata in Doctrine is the API of the ``ClassMetadata`` classes. You need to be familiar with them in order to implement your own drivers but more importantly to retrieve mapping information for a certain document when needed. You have all the methods you need to manually specify the mapping information instead of using some mapping file to populate it from. The base ``ClassMetadataInfo`` class is responsible for only data storage and is not meant for runtime use. It does not require that the class actually exists yet so it is useful for describing some document before it exists and using that information to generate for example the documents themselves. The class ``ClassMetadata`` extends ``ClassMetadataInfo`` and adds some functionality required for runtime usage and requires that the PHP class is present and can be autoloaded. You can read more about the API of the ``ClassMetadata`` classes in the PHP Mapping chapter. Getting ClassMetadata Instances ------------------------------- If you want to get the ``ClassMetadata`` instance for a document in your project to programmatically use some mapping information to generate some HTML or something similar you can retrieve it through the ``ClassMetadataFactory``: .. code-block:: php getMetadataFactory(); $class = $cmf->getMetadataFor('MyDocumentName'); Now you can learn about the document and use the data stored in the ``ClassMetadata`` instance to get all mapped fields for example and iterate over them: .. code-block:: php fieldMappings as $fieldMapping) { echo $fieldMapping['fieldName'] . "\n"; }