Di is just a tool to configure stuff. It's not a magic ball that can foresee what you want. You have to *tell* it what you want.
On a sidenote: it's a good idea to keep your models pretty dumb and put the logic into an appropriate service. This isn't the *only* way but it sure keeps things clean. Then you would make sure you setup Di so that the service has everything it needs and the service would use the model directly. Sorry if my answer is rather vague but it was hard to understand what you wanted to do from your post. ----- Kyle Spraggs www.blitzaroo.com blogs @ www.spiffyjr.me follow me @ www.twitter.com/kspraggs -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/ZF2-DI-into-Models-not-directly-within-a-controller-tp4113674p4123548.html Sent from the Zend Framework mailing list archive at Nabble.com. -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
