(on Wednesday, 06 May 2009, 10:10 PM -0500):
> Been experimenting with Zend_Application lately, especially trying to see what
> kinds of things I can do with module bootstrapping.
>
> In the process (actually, just noticed this after updating to r15371 tonight),
> I discovered that although my module bootstraps (extending
> Zend_Application_Module_Bootstrap) have access to all the rest of the parent
> application's configuration settings, they do not appear to use the same plugin
> paths in their pluginLoader.
>
> 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.
>
> I apologize if this has been mentioned before; I did a quick search of the
> lists and the tracker and didn't find anything has anybody else run into this
> issue? I'd be happy to add it to the tracker if it hasn't been reported
> already.
Please add a request to the tracker -- what you say makes sense.
--
Matthew Weier O'Phinney
Project Lead | matthew@zend.com
Zend Framework | http://framework.zend.com/
没有评论:
发表评论