无法在模块 init() 方法中附加事件

Question

我读到了ZF2的一些最佳实践。在那里，解释了在模块的模块类的 init（）-Method 中附加来自 MVC 的事件：

class Module {
  public function getAutoloaderConfig()  {
      return array(
        'ZendLoaderClassMapAutoloader' => array(
          __DIR__ . '/autoload_classmap.php',
        ),
      );
    }
    public function init(ModuleManager $moduleManager) {
      echo 'init<br>';
      $em = $moduleManager->getEventManager();
      $em->attach(MvcEvent::EVENT_DISPATCH, array($this, 'onDispatch'));
      $em->attach(MvcEvent::EVENT_ROUTE, array($this, 'onRoute'));
    }
    public function onDispatch(MvcEvent $e){
      echo 'onDispatch<br>';
    }
    ...

它导致没有错误，很好。但是事件没有被抓住...

有什么想法吗？我也尝试了共享管理器，但它仅适用于EVENT_DISPATCH...

Answer 1

除非有特定情况，否则最好在 onBootstrap 中注册您的事件。

init是针对"早期事件"。

我找到了一个非常清楚的链接：http://samsonasik.wordpress.com/2013/03/30/zend-framework-2-getting-closer-with-eventmanager/

您可以在ZendModuleManagerListenerDefaultListenerAggregate::attch中找到默认 MVC 事件的顺序：

 public function attach(EventManagerInterface $events)
    {
        $options                     = $this->getOptions();
        $configListener              = $this->getConfigListener();
        $locatorRegistrationListener = new LocatorRegistrationListener($options);
        // High priority, we assume module autoloading (for FooNamespaceModule classes) should be available before anything else
        $this->listeners[] = $events->attach(new ModuleLoaderListener($options));
        $this->listeners[] = $events->attach(ModuleEvent::EVENT_LOAD_MODULE_RESOLVE, new ModuleResolverListener);
        // High priority, because most other loadModule listeners will assume the module's classes are available via autoloading
        $this->listeners[] = $events->attach(ModuleEvent::EVENT_LOAD_MODULE, new AutoloaderListener($options), 9000);
        if ($options->getCheckDependencies()) {
            $this->listeners[] = $events->attach(ModuleEvent::EVENT_LOAD_MODULE, new ModuleDependencyCheckerListener, 8000);
        }
        $this->listeners[] = $events->attach(ModuleEvent::EVENT_LOAD_MODULE, new InitTrigger($options));
        $this->listeners[] = $events->attach(ModuleEvent::EVENT_LOAD_MODULE, new OnBootstrapListener($options));
        $this->listeners[] = $events->attach($locatorRegistrationListener);
        $this->listeners[] = $events->attach($configListener);
        return $this;
    }

Answer 2

使用共享管理器会更好。下面的示例用于在我们获得 xmlHttpRequest 时禁用布局，优先级 -95 是使事情正常工作的关键点。

public function onBootstrap(MvcEvent $e) {
    $eventManager        = $e->getApplication()->getEventManager();
    $moduleRouteListener = new ModuleRouteListener();
    $moduleRouteListener->attach($eventManager);
    // Hybrid view for ajax calls (disable layout for xmlHttpRequests)
    $eventManager->getSharedManager()->attach('ZendMvcControllerAbstractController', MvcEvent::EVENT_DISPATCH, function(MvcEvent $event){
       /**
        * @var Request $request
        */
        $request = $event->getRequest();
        $viewModel = $event->getResult();
       if($request->isXmlHttpRequest()) {
            $viewModel->setTerminal(true);
        }
        return $viewModel;
    }, -95); 
}

Answer 3

请参阅 http://akrabat.com/zend-framework-2/module-specific-bootstrapping-in-zf2/

只找到了这个解决方案：在 Module.php 类的 onBootstrap（）-Method 中附加侦听器：

。

public function onBootstrap(MvcEvent $e){
 echo 'onBootstrap<br>';
 $em =  $e->getApplication()->getEventManager();
 $em->attach(MvcEvent::EVENT_DISPATCH, array($this, 'onDispatch'));
 $em->attach(MvcEvent::EVENT_ROUTE, array($this, 'onRoute'));
}

。