Phly, boy, phly
the weblog and site of Matthew Weier O'Phinney

First, make sure the path to the Doctrine.php file is on your include_path.

Next, Zend_Loader_Autoloader allows you to specify "namespaces" (not actual PHP namespaces, more like class prefixes) it can autoload, both for classes it will autoload, as well as for autoload callbacks you attach to it. Typically, you include the trailing underscore when doing so:

However, because Doctrine has a master class for handling common operations, "Doctrine", we have to omit the trailing underscore so that the Doctrine class itself may be autoloaded. We need to do two different operations: first, add a namespace to Zend_Loader_Autoloader for Doctrine (which will allow us to autoload the Doctrine class itself, as well as the various doctrine subcomponent classes), and then register the Doctrine autoloader (which will be used by Doctrine to load items such as table classes, listeners, etc.):

This takes care of the Doctrine autoloader; now, let's turn to Doctrine models.

First, tell Doctrine that you want to autoload. You do this by telling it to use "conservative" model loading (shorthand for lazyloading or autoloading), and to autoload table classes:

From here, you need to ensure you actually can autoload the models. Normally, you tell Doctrine where to find models, but we're in a Zend Framework application, so let's leverage ZF conventions.

I typically put my model code with my application code:

application
|-- Bootstrap.php
|-- configs
|-- controllers
|-- models                 <- HERE
|-- modules
|   `-- blog
|       |-- Bootstrap.php
|       |-- controllers
|       |-- forms
|       |-- models         <- HERE
|       |-- services
|       `-- views
`-- views

Zend Framework already provides mechanisms for autoloading application resources via Zend_Loader_Autoloader_Resource and Zend_Application_Module_Autoloader. Assuming you've extended Zend_Application_Module_Bootstrap in your module bootstraps, you're basically already set. The trick has to do with your table classes; your table classes must be placed in the same directory as your models, and they must be named exactly the same as your models, with the suffix "Table".

For example, if you had the class Blog_Model_Entry extending Doctrine_Record in the file application/modules/blog/models/Entry.php, the related table class would be Blog_Model_EntryTable in the file application/modules/blog/models/EntryTable.php.

I automate most of this setup via my Bootstrap class, which typically looks as follows:

Within your configuration, you need to add two keys: one for registering the Doctrine namespace with the default autoloader, and another for the dsn:

I also have a script that I use to load all model classes at once in order to do things like generate the schema or test interactions. I'll blog about those at a later date. Hopefully the above information will help one or two of you out there trying to integrate these two codebases!

Updates

• 2009-08-21: added information about registering Doctrine namespace with default autoloader