-- Demian Katz <
[hidden email]> wrote
(on Tuesday, 10 July 2012, 07:48 PM +0000):
> According to the documentation here:
>
>
http://packages.zendframework.com/docs/latest/manual/en/> zend.service-manager.quick-start.html#
> zend.service-manager.quick-start.examples.service-manager-aware
>
>
>
> “By default, the Zend Framework MVC registers an initializer that will inject
> the ServiceManager instance into any class implementing Zend\ServiceManager\
> ServiceManagerAwareInterface. The default controller implementations implement
> this interface, as do a small number of other objects.”
Ug -- should be ServiceLocatorAwareInterface, and setServiceLocator
should typehint on ServiceLocatorInterface. This was changed right after
beta4, but we clearly didn't update the docs with this information.
> However, this does not seem to be true (at least in beta5). I was unable to
> get access to the ServiceManager by implementing ServiceManagerAwareInterface
> in my controller, and searching through the code base, I don’t see any default
> controller implementations using this interface.
>
> Digging deeper into the code, I figured out that implementing
> ServiceLocatorAwareInterface instead of ServiceManagerAwareInterface does give
> my controllers access to the ServiceManager.
>
> So what’s going on? Is the documentation wrong? Is the code in flux? What is
> the distinction between these two interfaces?
The appropriate interface is ServiceLocatorAwareInterface. The reason
being is that this allows providing an alternate ServiceLocatorInterface
implementation -- ServiceManagerAwareInterface requires that you extend
ServiceManager, which kind of defeats the point of having an interface.
This was simply an oversight in beta4, which was corrected right after
release (and included in beta5).
> And on a more general level, what is the best practice for injecting services
> into controllers? My situation (probably a common one) is that my module is
> bootstrapping some resources that the controllers will need to use. I just
> need a simple, lightweight way to access these resources. Using the service
> manager is easy enough (now that I can access it), but if there is a better
> way, I’d love to see some examples.
I typically create factories for these situations. The factories can
either be classes implementing Zend\ServiceManager\FactoryInterface, or
they can be a callback defined in your Module class:
namespace My;
class Module
{
public function getControllerConfiguration()
{
return array('factories' => array(
'My\World' => function ($sm) {
$db = $sm->get('Zend\Db\Adapter\Adapter');
$auth = $sm->get('Zend\Authentication\AuthenticationService');
$controller = new My\Controller\WorldController($db);
$controller->setAuthentication($auth);
return $controller;
},
));
}
}
--
Matthew Weier O'Phinney
Project Lead |
[hidden email]
Zend Framework |
http://framework.zend.com/PGP key:
http://framework.zend.com/zf-matthew-pgp-key.asc
Locked
