ZF-8496: Add ability for Zend_Application_Bootstrap_Bootstrap to initialize a module autoloader

Issue Type: Improvement Created: 2009-12-08T09:01:55.000+0000 Last Updated: 2009-12-14T06:42:03.000+0000 Status: Resolved Fix version(s): - 1.10.0 (27/Jan/10)

Reporter: Matthew Weier O'Phinney (matthew) Assignee: Matthew Weier O'Phinney (matthew) Tags: - Zend_Application

Related issues: - ZF-8540



Zend_Application_Bootstrap_Bootstrap should initialize a module autoloader by default, using a sane default namespace ("Application").


Posted by Matthew Weier O'Phinney (matthew) on 2009-12-08T09:31:15.000+0000

Changes committed to trunk

Posted by Dolf Schimmel (Freeaqingme) (freak) on 2009-12-08T12:13:56.000+0000

{quote} note to self: also add a switch to disable the module autoloader...{quote}

Now I wont feel ashamed if I forget to remember that for you ;) (notes to oneself in pm's tend to be forgotten. - Or maybe I should raise my expectations? ;))

Posted by Matthew Weier O'Phinney (matthew) on 2009-12-10T14:03:03.000+0000

Resolved in trunk. Behavior is opt-in for existing projects, enabled by default for new projects, and documented in the Bootstrap docs.

Posted by Cristian Bichis (avantis) on 2009-12-11T01:24:51.000+0000

I don't quite understand the changes needed to existing applications to work with this revision.

After i updated one application to 19571 the modules resources stopped loading.

By example i had a Text_Model_Text class which is not loading anymore, and of course all the classes from modules are failing loading.

Before of this i was using:

resources.modules[] = ""

And Bootstrapper as:

class Text_Bootstrap extends Zend_Application_Module_Bootstrap {


for each module...

Posted by Matthew Weier O'Phinney (matthew) on 2009-12-11T06:50:15.000+0000

Can you elaborate?

The only thing this is supposed to do is allow specifying a module autoloader for the application-level bootstrap; this is done by simply adding a key to your configuration:

<pre class="highlight">
appnamespace = "Application"

Module bootstraps should be unaffected; am I to understand that your module bootstraps are no longer initializing module autoloaders? (I'm a bit unclear as to what you're asking...)

Posted by Cristian Bichis (avantis) on 2009-12-11T07:36:48.000+0000

Yes, your'e right: module autoloaders doesn't seems to work anymore...

Posted by Bert Hausmans (berthausmans) on 2009-12-14T04:17:10.000+0000

Same problem here. After I add the line "appnamespace = "Application" to the application configuration, the Module Autoloaders still didn't work.

Posted by Matthew Weier O'Phinney (matthew) on 2009-12-14T06:21:14.000+0000

Fixed in trunk.

Posted by Cristian Bichis (avantis) on 2009-12-14T06:42:03.000+0000

Yes, works fine now. Thanks.

Have you found an issue?

See the Overview section for more details.


© 2006-2018 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.