-- Jeroen Keppens <[email protected]> wrote (on Tuesday, 26 May 2009, 07:15 AM -0700): > keith Pope-4 wrote: > > 2009/5/8 Rick Buitenman <[email protected]>: > > ... > > Yes, the module bootstrap resource will loop and call each module > > bootstrap, though it skips the default module. > > ... > > Is there a specific reason for this?
There was, though the rationale has changed since the original iteration. The original version was targetting a structure where the default module is directly under application/, and all *other* modules are under another directory. Clearly, this is not how everyone is doing modular structures, however, so we're running into issues. I plan to address these no later than 1.9. > You can of course say that the main bootstrap should contain the default > behaviour, but I noticed that the main bootstrap file can't be extending > Zend_Application_Module_Bootstrap (or at least didn't get it to work). It *can*, but you need to name the bootstrap class "Default_Bootstrap" for it to work. > I ended up writing resource loading for my default module's models in the > _initAutoload of the main bootstrap, but it would have been nicer/cleaner if > it could be handled the same way as the other non-default modules. -- Matthew Weier O'Phinney Project Lead | [email protected] Zend Framework | http://framework.zend.com/
