Yeah that was my first idea too, but the problem is that i use a common
bootstrap for all my applications which just loads the default stuff and my
default module can vary which is then an e-commerce- or cms system therefor
i need to bootstrap the module itself as this bootstrap will contain more
precise boostrapping information like reading a configuration file.
I was also pondering about creating a multi system that provided both
e-commerce- and cms-system functionality, at the installation the user
selected which he wanted to use and is able to switch when needed (altough
his customers won't like this :D)
Well in the first versions of Zend framework you also couldn't prefix the
default controllers know you can by using prefixDefaultModule maybe they'll
add something for that to one day :)
dmitrybelyakov wrote:
>
>
>
> ignace wrote:
>>
>> Why can't i have a Bootstrap in my default module? The code says:
>>
>> if ($module === $default) {
>> continue;
>> }
>>
>
> Hi,
>
> I think that's because your default module actually 'is' your application.
> You may use your application Bootstrap instead.
>
>
--
View this message in context:
http://www.nabble.com/Zend_Application_Module_Bootstrap---bootstrapping-the-default-module-tp23838994p23846973.html
Sent from the Zend Framework mailing list archive at Nabble.com.
