Using Zend Framework and Doctrine with independend modular structures?

We are working on a solution to this at the company I work at right now We are following the Zend modular directory structure currently, and we have our models folder in each module directory, with a base directory like this: application |--------modules |------------content |----------------models |--------------------Base |------------------------Content. Php |--------------------Content. Php Our models autoload, but we haven't integrated the code generation into the zf cli, so we currently generate the models and then copy them into the module directory manually Sorry I don't have the exact answer you need, but you may also be interested in this proposal in the Zend Community.

We are working on a solution to this at the company I work at right now. We are following the Zend modular directory structure currently, and we have our models folder in each module directory, with a base directory like this: |----application |--------modules |------------content |----------------models |--------------------Base |------------------------Content. Php |--------------------Content.

Php Our models autoload, but we haven't integrated the code generation into the zf cli, so we currently generate the models and then copy them into the module directory manually. Sorry I don't have the exact answer you need, but you may also be interested in this proposal in the Zend Community.

Thanks Travis, the problem here is that with this it's unclean to use a model in module A from within module B and that's the frequently the case for us. In order to NOT invent a completely non ZF solution we stick with the "one model folder on top level"-solution and live with many files in one folder ... – stefax Feb 6 '10 at 10:35.

I didn't try it but maybe this would solve a part of the problem doctrine-project.org/documentation/manua....

I keep mine in one directory. As the saying goes, developer time is expensive, and CPU time is cheap, so optimize for the developer. Also, KISS, and YAGNI.

Don't optimize until you need to optimize. Until then, trust auto loader. For what it's worth, the site I use this on is fairly busy and performance has never been an issue.

Yep, that's how we decided to do it in the end. The model directory of our system contains now lots of files (around 200 or more) so navigating through and looking for specific models in the IDE is sometimes annoying, but on the other hand nobody has to think about which sub directory to be used for a certain model (because sometimes several sub directories would be appropriate) ... – stefax Jun 19 '10 at 12:46.

To me after all, Modules make less sense when they are not interchangeable.

1 Yes, I agree. That's the cleanest solution and you should do it like that, above all, when you are starting. Back then, when I had the problem from above, I migrated an old system and we didn't have the resources to implement it like this with independent interchangeable modules but kept close to the old structures.

– stefax Jul 15 at 8:21.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.