Issue Type: Bug Created: 2009-05-07T04:39:38.000+0000 Last Updated: 2009-06-10T08:25:21.000+0000 Status: Resolved Fix version(s): - 1.8.1 (12/May/09)
Reporter: Adam Jensen (jazzslider) Assignee: Matthew Weier O'Phinney (matthew) Tags: - Zend_Application
Related issues: Attachments:
When using Zend_Application's Modules resource to allow for module-specific bootstrapping, all of the parent bootstrap's configuration options are passed to the module bootstraps, except for its plugin paths.
This appears to be because the pluginPaths key is removed from the options array prior to the options being stored in Zend_Application_Bootstrap_BootstrapAbstract.php (see esp. line 121).
The net result of this is that the parent bootstrap's plugin loader has all the appropriate paths, but these paths never get passed on appropriately to the module bootstrappers. Because of this, applications using custom plugin resource classes will experience a fatal exception when the module bootstrappers are loaded in: e.g.,
Zend_Loader_PluginLoader_Exception: Plugin by name 'Customresourcename' was not found in the registry; used paths: Zend_Application_Resource_: Zend/Application/Resource/ in /path/to/zf/library/Zend/Loader/PluginLoader.php on line 390
This has been tested against revision 15373 of the trunk.
Posted by Matthew Weier O'Phinney (matthew) on 2009-05-11T03:53:47.000+0000
Fixed in trunk and 1.8 release branch
Posted by Edward Surov (zooh) on 2009-06-03T06:38:53.000+0000
Still a problem in rev. 15555 of Zend_Application_Bootstrap_BootstrapAbstract. Can be solved by copying pluginPaths from application instance in the constructor.
Posted by Edward Surov (zooh) on 2009-06-10T08:25:20.000+0000
Oops, sorry, there's no problem. But you should write about using Zend_Application_Module_Bootstrap for module bootstraps in documentation :)
Have you found an issue?
See the Overview section for more details.