To get module specific config etc you are probably best to write a
Front Controller Plugin and get the module name once routing has
finished or during the dispatch loop startup. Personally I prefer to
have a global config dir in the root so I dont have to do this.
There are no guides currently that cover modular applications, I must
say that the module/modular name does confuse a lot of people, it does
not mean that ZF supports an easy way to implement a modular
application, you still have to come up with solutions to handle
inter-modular dependencies etc, though I use a server layer to help
with this.
You may also want to check out this proposal which outline the
recommended project structure.
Hope this helps
2008/11/29 Jiří Helmich <jiri@helmich.cz>:
> Hi,
>
>
>
> I'm trying to run a modular application based on ZF MVC, so I've created the
> project structure as it is described in Quick start guide (/application
> copied under /application/modules/{somemodule}). Because of using modules, I
> have several problems with the structure and bootstrapping the application,
> because there is no modular application Quick start guide:
>
>
>
> $frontController->setControllerDirectory(APPLICATION_PATH .
> '/controllers')->addModuleDirectory(APPLICATION_PATH.'/modules');
>
>
>
> Calling setControllerDirectory looses it sense, doesn't it?
>
>
>
> I'd like to set layout directory depending on the modules configugration
> file, but – how can I parse
> application/modules/{somemodule}/config/config.ini in the bootstrap?
>
>
>
> Has anybody any solution for this? Is there any guide for modular app?
>
>
>
> Thanks for any response
>
> Jiri
>
>
--
----------------------------------------------------------------------
[MuTe]
----------------------------------------------------------------------
没有评论:
发表评论