ZEND-MVC Intro

Last Update:2016-07-22 Source: Internet

Author: User

Tags autoload autoloader event listener

Developer on Alibaba Coud: Build your first app with APIs, SDKs, and tutorials on the Alibaba Cloud. Read more ＞

ZEND-MVC IntroThe Zend MVC layer is built on servicemanager, eventmanager, http, stdlib, and several components. The related components are described in more detail in other Articles.In addition to the above 4 components, MVC exposes several sub-components:router, controllers, Service, and View. The following is a brief introduction:1, Router: matching the request to the relevant controller (also known as scheduling, Dispatch)2, Controller: is a series of abstract classes, responsibility: event connectivity, Behavior scheduling, Controller Plug-ins.3. Service: provide a series of servicemanager factories to provide a definition for the default application workflow.4, view: provide default renderer, view Script parsing, Helper registration and so On. In addition, listeners are provided for the MVC WORKFLOW. Provides the following Features: automated template name resolution, Automated view model creation and injection, and More.The Zend\mvc\application object when it leads to the door to Mvc. The main responsibilities are: directing resources, routing requests, accepting and scheduling matching controllers during Routing. When the appeal is complete, the view is rendered, the request is completed, and the answer is Returned.Application's infrastructure:<pre>1application_root/2config/3 application.config.php4autoload/5 Global. PHP6 local.php7 //etc.8data/9module/Tenvendor/ one public/ a . htaccess - index.php -init_autoloader.php</pre>The following are the relevant Roles:1. Public/index.php: arrange all user requests to your website and get configuration information from Config/application.config.php. On return, Run application using the Run () method to process the request & return Answer.2. Config/:modulemanager uses the configuration file under this directory to load modules and merge these Configurations.3. vendor/: any third-party module or library file that your application relies on should be in this directory. generally, This directory is managed by composer.4, module/: This directory may contain one or more modules, these modules determine the function of your Application.Basic Module Structure:A module can basically contain anything: PHP code, library code, View scripts, public assets such as: pictures, CSS, JavaScript. The only requirement (or even optional): a module acts as a PHP namespace that contains a module class. This class will eventually be used by Modulemanager to perform some tasks.The recommended module structure is as Follows:<pre>1module_root<name-after-module-namespace>/2 module.php3 autoload_classmap.php4 autoload_function.php5 autoload_register.php6config/7 module.config.php8 public/9images/Tencss/ onejs/ asrc/ -<module_namespace>/ -<code file> thetest/ - Phpunit.xml - bootstrap.php -<module_namespace>/ +<test Code files> -view/ +<dir-named-after-module-namespace>/ a<dir-named-after-a-conftroller>/ at<.phtml files></pre>Since a module serves as a namespace, the module root should be the Namespace. This namespace can also contain a prefix for a vendor. For example, the core of a module is the user function, the module is provided by zend, then the module can be named Zenduser.The appeal structure is actually a PSR-0-compliant structure. You can also use the PSR-4 structure, as long as you properly set the Autoload.The module.php is placed directly under the root of the module, and its namespace should be the namespace that the module assumes:<pre><pre>1 namespace zenduser; 2 class Module 3 {4 }</pre></pre>Note: the location of the module class:If you define autoloader or use the composer autoloading feature, you can put module.php in the same place. The current recommendation is to use composer to define Autoloading.If you define the init () method, The method is triggered by the Modulemanager listener when the module class is loaded, and is passed to an Modulemanager instance. This allows you to perform a task similar to setting up a module-specific event listener. But be careful: the init () method is called whenever there is a request for each module on each page. therefore, This method only performs some lightweight tasks (such as registering listeners). Similar Onbootstrap () methods that accept Mvcevent instances should also perform only a few lightweight tasks when they are defined.Three autoload_*.php files are not Required. If you do not use composer to provide autoload, it is recommended to use these three Files. <table style="height: 80px; width: 523px;" border="1"> <tbody> <tr> <td>FILE</td> <td>Description</td> </tr> <tr> <td>autoload_classmap.php</td> <td>Returns an associative array of class mappings (name/filename), with the value filename parsed by the __dir__ magic Constant.</td> </tr> <tr> <td>autoload_function.php</td> <td>Returns a PHP callback function that can be passed into the Spl_autoload_register () Function. In general, these callback functions take advantage of the mappings returned by autoload_classmap.php.</td> </tr> <tr> <td>autoload_register.php</td> <td>Register the PHP callback Function. (these callback functions are typically returned by autoload_function.php, using Spl_autoload_register () to register).</td> </tr> </tbody> </table>These three files actually provide a mechanism for automatically loading the classes inside the module, providing a way to use the modules without the need for modulemanager.The config directory should contain a module-qualified Configuration. These files can be in any zend-config supported Format. We recommend naming the master configuration module.config.<format> (for example, php-based configuration: module.config.php). In general you will create profiles for router and servicemanager.The SRC directory should conform to PSR-0 or PSR-4 standards.The test directory should contain your testing units, which, in general, can be written using phpunit.The public directory should be used to store what you want to expose (more than tablets, css,javascript, etc.)The view directory contains the views script associated with your controller.Boot a application:Application has 7 base dependencies:1, configuration;2, ServiceManager example;3, EventManager Instance (by default, The service name is obtained from the ServiceManager eventmanager);4, Sharedeventmanager Instances (also obtained from the servicemanager, this instance will be injectedEventManager instances);5, Modulemanager Example (get the way ibid.);6, the request instance (obtain the way ibid.);7, reponse Instances (get the same way).The dependency resolution code is as Follows:<pre>1 usezend\eventmanager\eventmanager;2 usezend\eventmanager\sharedmanager;3 usezend\http\phpenvironment;4 usezend\modulemanager\modulemanager;5 usezend\mvc\application;6 usezend\servicemanager\servicemanager;7 8 $config=include' Config/application.config.php ';9 $serviceManager=NewServiceManager ();Ten $serviceManger->setservice (' Sharedeventmanger ',NewSharedeventmanager (); one $serviceManager->setservice (' Modulemanager ',NewModulemanager ($config)); a $serviceManager->setservice (' Request ',Newphpenvironment\request ()); - $serviceManager->setservice (' reponse ',NewPhpenvironment\reponse ()); - $serviceManager->setfactory (' EventManager ',function($serviceManager) { the $eventManager=NewEventManager (); - $eventManager->setsharedmanager ($serviceMnager->get (' Sharedeventmanager '); - return $eventManager; - }); + $serviceManager->setshared (' EventManager ',false); - $application=NewApplication ($config,$serviceManager);</pre>Once you have solved the dependency, you have two additional options:1. The steps to boot the Application;bootstrap () method are as Follows:Connect the default route (zend\mvc\routelistener);Connected Middleware Scheduling Listener (zend\mvc\middlewarelistener);Connect the default dispatch listener (zend\mvc\dispatchlistener);Connecting the Viewmanager listener (zend\mvc\view\viewmanager);Create mvcevent, and inject with application,request and response. At this point it also acquires the router (zend\mvc\router\http\treeroutestack) and connects to the event;Triggers the "bootstrap" event.These are just the default steps, and you can also choose the steps you want to perform by inheriting Application.2, If you do not want to guide application, there is an alternative choice. Use the configured application, and then call the run () method. Calling this method will perform the following actionsTriggering a routed event;then, according to the implementation of the event scheduling;Triggering the Render eventWhen finished, the finish event is triggered and the answer instance is Returned. The Dispatch.error event will occur whenever an error occurs.In order to guide application, there seems to be a lot of work to do, but in fact you do not need to cover so many services, directly with the default ServiceManager configuration can Be.<pre> usezend\loader\autoloaderfactory; usezend\mvc\service\servicemangerconfig; usezend\servicemanager\servicemanger;//Setup Autoloaderautoloaderfactory::Factory ();//get application Stack configuratin$configuration=include' Config/application.php '; Setup Service Manager $serviceManager = new ServiceManager (new servicemanagerconfig ()); $serviceManager->setservice (' applicationconfig ', $configuration); Load Modules--which would provides services, configuration, and more $serviceManager->get (' Modulemanager ')->loadmodules (); Bootstrap and Run application $application = $serviceManager->get (' application '); $application->bootstrap (); $application->run ();</pre>You can even make this easier: we use the Init () method inside the Application. This is a static method that initializes the application instance Quickly.<pre> usezend\loader\autoloaderfactory; usezend\mvc\application; usezend\mvc\service\servicemanagerconfig; usezend\servicemanager\servicemanager;//Setup Autoloaderautoloaderfactory::Factory ();//get application stack configuration$configuration=include' Config/application.config.php ';//the init () method does something very similar with the previous Example.Application::init ($configuration)->run ();</pre>Init () performs the following steps:Get configuration information for application, get the key word from servicemanager, create a ServiceManager instance using the default service and the configuration you just madeCreate a service named Applicationconfig using the configuration arrayGet the Modulemanager service, and then load the moduleBootstrap () application and returns the instanceNote: about Applicationconfig services: If you use the init method, you will not be able to specify a service with the same name in your service management Configuration. This name is reserved for receiving arrays from APPLICATION.CONFIG.PHP. The following services can only be rewritten in application.config.php:ModulemanagerSharedeventmanagerEventManagerZend\eventmanager\eventmanagerinterfaceOther services will be configured after the module is loaded, so it can be rewritten inside the Module.To guide a modular applicationWhen we create a modular application, we assume that the configuration file originates from the module itself. How do we get information and aggregate them?The answer is through Modulemanager. This component allows you to specify the module that application will Use. Then he will locate each module and initialize it. Module classes can be embedded in different listeners to provide configuration, services, listeners, and so on for Application.Configuring Module ManagerThe first step is to configure the module manager. Notifies the module manager which modules can be loaded and provides configuration for module Listeners. In application.config.php we have the following code:<pre>1<?PHP2 3 //config/application.php4 return Array[5' Modules ' =Array[6],7 8' Module_listener_options ' = [9' Module_paths ' = [Ten'./module ', one'./vendor ', a ] - ] -];</pre>Each module class that wants application to know the configuration information should define a getconfig () method. The method should return an array or an object that can be traversed (such as a zend\config\config instance)code example<pre><pre>1 namespace zenduser; 2 class Module 3 {4 public function GetConfig () 5 {6 returninclude __dir__. '/config/module.config.php '7 }8 }</pre></pre>ZEND-MVC Intro

This article is an English version of an article which is originally in the Chinese language on aliyun.com and is provided for information purposes only. This website makes no representation or warranty of any kind, either expressed or implied, as to the accuracy, completeness ownership or reliability of the article or any translations thereof. If you have any concerns or complaints relating to the article, please send an email, providing a detailed description of the concern or complaint, to info-contact@alibabacloud.com. A staff member will contact you within 5 working days. Once verified, infringing content will be removed immediately.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

Get Started for Free

Sales Support

1 on 1 presale consultation

Chat Contact Sales
After-Sales Support

24/7 Technical Support 6 Free Tickets per Quarter Faster Response

Open a Ticket
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.

Learn More