This bundle integrates Doctrine PHPCR ODM and PHPCR backends into Symfony2 like:
- Jackalope
- Midgard2 CR
Follow the installation tutorial
The configuration is similar to Doctrine ORM and MongoDB configuration for Symfony2 as its based
on the AbstractDoctrineBundle
aswell:
doctrine_phpcr:
# configure the PHPCR session
session:
backend:
## backend type: jackrabbit, doctrinedbal or midgard
type: jackrabbit
## doctrinedbal only, required
connection: <service name of the doctrine dbal connection>
## jackrabbit only, required
url: http://localhost:8080/server/
## jackrabbit only, optional. see https://github.com/jackalope/jackalope/blob/master/src/Jackalope/RepositoryFactoryJackrabbit.php
default_header: ...
expect: 'Expect: 100-continue'
## tweak options for jackrabbit and doctrinedbal (all jackalope versions)
# optional, below set to the default
# enable if you want to have an exception right away if backend login fails
check_login_on_server: false
# enable if you experience segmentation faults while working with binary data in documents
disable_stream_wrapper: false
# enable if you do not want to use transactions and you neither want the odm to automatically use transactions
# its highly recommended NOT to disable transactions
disable_transactions: false
workspace: default
username: admin
password: admin
# enable the ODM layer. omit the odm section if you only want a phpcr session but no odm
odm:
auto_mapping: true
# whether to automatically create proxy classes or create them manually
auto_generate_proxy_classes: %kernel.debug%
# overwrite the default location for generated proxies
proxy_dir: ...
# overwrite the default php namespace for proxies
proxy_namespace: ...
# set the language fallback order (for translatable documents)
locales:
en:
- en
- de
- fr
de:
- de
- en
- fr
fr:
- fr
- en
- de
You can access the PHPCR services like this:
<?php
namespace Acme\DemoBundle\Controller;
use Symfony\Bundle\FrameworkBundle\Controller\Controller;
class DefaultController extends Controller
{
public function indexAction()
{
// PHPCR session instance
$session = $this->container->get('doctrine_phpcr.default_session');
// PHPCR ODM document manager instance
$documentManager = $this->container->get('doctrine_phpcr.odm.default_document_manager');
}
}
You can tag services to listen to Doctrine phpcr events. It works the same way as for Doctrine ORM. The only differences are
- use the tag name
doctrine_phpcr.event_listener
resp.doctrine_phpcr.event_subscriber
instead ofdoctrine.event_listener
. - expect the argument to be of class Doctrine\ODM\PHPCR\Event\LifecycleEventArgs rather than in the ORM namespace.
You can register for the events as described in the PHPCR-ODM documentation.
services:
my.listener:
class: Acme\SearchBundle\Listener\SearchIndexer
tags:
- { name: doctrine_phpcr.event_listener, event: postPersist }
More information on the doctrine event system integration is in this symfony cookbook entry.
To use the doctrine:phpcr:fixtures:load command, you additionally need the Doctrine data-fixtures and the symfony doctrine fixtures bundle:
The bundle provides a couple of symfony commands. To execute them, from your main project folder run
app/console.php <command> [options] [arguments]
Look for the commands that start with doctrine:phpcr
.
The fixtures classes must implement Doctrine\Common\DataFixtures\FixtureInterface
.
Here is an example of fixture:
<?php
namespace MyBundle\DataFixtures\PHPCR;
use Doctrine\Common\Persistence\ObjectManager;
use Doctrine\Common\DataFixtures\FixtureInterface;
class LoadMyData implements FixtureInterface
{
public function load(ObjectManager $manager)
{
// Create and persist your data here...
}
}