[eluser]wiredesignz[/eluser]
You've done a huge amount of work here and I'm sure it's greatly appreciated by the community.
From my experience using MVC I've concluded that it's not such a good idea to use any data objects in the controller directly.
Doing this then requires all of your application business logic to be in the controller also when it should really be in your models.
The model should encapsulate the Doctrine objects rather than being replaced by them. Even your diagram (in Part 1) shows business logic being in models but your code examples don't.
Maybe at some point you could give examples of how a model might encapsulate the Doctrine data objects. Thanks.
