Comments on: Bootstrapping the Doctrine 2.0 Autoloader in Zend Framework

By: Skip

Skip — Thu, 05 Aug 2010 05:08:49 +0000

I have been creating the EntityManager in Bootstrap, and putting it in the Zend_Registry. This is a fatally flawed approach. As soon as you do some explicit transaction demarcation, you will discover that the entity manager is closed on the first PDOException. Therefore, all subsequent operations fail, until you create a new EntityManager. So bootstrap is wrong. A factory pattern is missing here. I am thinking about putting an EntityManager factory in the registry, from bootstrap, and then calling factory.create() from each controller. That at least allows the factory to encapsulate the configuration options and event manager, leaving the controllers to call a simple one-liner with no arguments.

By: Brenton Alker

Brenton Alker — Wed, 28 Apr 2010 00:05:02 +0000

@Jonathon No, I would definitely not be creating the EntityManager in the controllers. I wouldn’t even use it in the controller – it’s part of the model layer.

More likely, I would create it once and inject it into the service layer. How that could be done is an entire post on its own. The registry is one option, others could be a central service broker, or a full Dependecy Injection/Inversion of Control container.

By: Jonathon

Jonathon — Fri, 26 Feb 2010 22:00:01 +0000

Do you have to explicitly create the EntityManager throughout your code (ex. in your controllers)? That seems a little wrong (especially if you have to provide the configuration information each time). Maybe create the instance in the Bootstrap as well and store in Zend_Registry. Thoughts?

Also, I’m wondering what the “recommended” directory structure is going to be as well.

By: bandirsen

bandirsen — Thu, 14 Jan 2010 09:29:59 +0000

Thanks for sharing. this is information a piece that I looking for.

Looking for your next tips on this integration, such as, how to integrating doctrine 2 cache and zend_cache