Zend_Application_Resource_Cachemanager may be utilised to configure a set of Zend_Cache option bundles for use when lazy loading caches using Zend_Cache_Manager

As the Cache Manager is a lazy loading mechanism, the options are translated to option templates used to instantiate a cache object on request.

Zend_Application_Resource_Db will initialize a Zend_Db adapter based on the options passed to it. By default, it also sets the adapter as the default adapter for use with Zend_Db_Table. If you want to use mutliple databases simultaneously, you can use the Multidb Resource Plugin.

The following configuration keys are recognized:

• adapter: Zend_Db adapter type.

• params: associative array of configuration parameters to use when retrieving the adapter instance.

• isDefaultTableAdapter: whether or not to establish this adapter as the default table adapter.

• defaultMetadataCache: the name of the cache template or an instance of Zend_Cache_Core to use as metadata cache for Zend_Db_Table.

Note: Retrieving the Adapter instance
If you choose not to make the adapter instantiated with this resource the default table adapter, how do you retrieve the adapter instance?
As with any resource plugin, you can fetch the DB resource plugin from your bootstrap:

1. $resource = $bootstrap->getPluginResource('db');

Once you have the resource object, you can fetch the DB adapter using the getDbAdapter() method:

1. $db = $resource->getDbAdapter();

Zend_Application_Resource_Dojo can be used to configure the Zend_Dojo viewhelpers.

Probably the most common resource you will load with Zend_Application will be the Front Controller resource, which provides the ability to configure Zend_Controller_Front. This resource provides the ability to set arbitrary front controller parameters, specify plugins to initialize, and much more.

Once initialized, the resource assigns the $frontController property of the bootstrap to the Zend_Controller_Front instance.

Available configuration keys include the following, and are case insensitive:

• controllerDirectory: either a string value specifying a single controller directory, or an array of module to controller directory pairs.

• moduleControllerDirectoryName: a string value indicating the subdirectory under a module that contains controllers.

• moduleDirectory: directory under which modules may be found.

• defaultControllerName: base name of the default controller (normally "index").

• defaultAction: base name of the default action (normally "index").

• defaultModule: base name of the default module (normally "default").

• baseUrl: explicit base URL to the application (normally auto-detected).

• plugins: array of front controller plugin class names. The resource will instantiate each class (with no constructor arguments) and then register the instance with the front controller. If you want to register a plugin with a particular stack index, you need to provide an array with two keys class and stackIndex.

• params: array of key to value pairs to register with the front controller.

• returnresponse: whether or not to return the response object after dispatching the front controller. Value should be a boolean; by default, this is disabled.

• dispatcher: allows overriding the default dispatcher. Has two subkeys, class (the classname of new dispatcher) and params, an array of parameters to pass to the dispatcher constructor.

  Example #4 Overriding the dispatcher

  1. [production]
  2. resources.frontController.dispatcher.class = "My_Custom_Dispatcher"
  3. resources.frontController.dispatcher.params.foo = "bar"
  4. resources.frontController.dispatcher.params.baz = "grok"

If an unrecognized key is provided, it is registered as a front controller parameter by passing it to setParam().

Zend_Application_Resource_Layout can be used to configure Zend_Layout. Configuration options are per the Zend_Layout options.

Zend_Application_Resource_Locale can be used to set an application-wide locale which is then used in all classes and components which work with localization or internationalization. By default the locale is saved in a Zend_Registry entry with key 'Zend_Locale'.

There are basically three usecases for the Locale Resource Plugin. Each of them should be used depending on the applications need.

Zend_Application_Resource_Log to instantiate a Zend_Log instance with an arbitrary number of log writers. Configuration will be passed to the Zend_Log::factory() method, allowing you to specify combinations of log writers and filters. The log instance may then be retrieved from the bootstrap later in order to log events.

Zend_Application_Resource_Mail can be used to instantiate a transport for Zend_Mail or set the default name and address, as well as the default replyto- name and address.

When instantiating a transport, it's registered automatically to Zend_Mail. Though, by setting the transport.register directive to FALSE, this behaviour does no more occur.

Zend_Application_Resource_Modules is used to initialize your application modules. If your module has a Bootstrap.php file in its root, and it contains a class named Module_Bootstrap (where "Module" is the module name), then it will use that class to bootstrap the module.

By default, an instance of Zend_Application_Module_Autoloader will be created for the module, using the module name and directory to initialize it.

Since the Modules resource does not take any arguments by default, in order to enable it via configuration, you need to create it as an empty array. In INI style configuration, this looks like:

In XML style configuration, this looks like:

Using a standard PHP array, simply create it as an empty array:

Note: Front Controller Resource Dependency
The Modules resource has a dependency on the Front Controller resource. You can, of course, provide your own replacement for that resource via a custom Front Controller resource class or a class initializer method -- so long as the resource plugin class ends in "Frontcontroller" or the initializer method is named "_initFrontController" (case insensitive).

Zend_Application_Resource_Multidb is used to initialize multiple Database connections. You can use the same options as you can with the Db Resource Plugin. However, for specifying a default connection, you can also use the 'default' directive.

Zend_Application_Resource_Navigation can be used to configure a Zend_Navigation instance. Configuration options are per the Zend_Navigation options.

Once done configuring the navigation instance, it assigns the instance to Zend_View_Helper_Navigation by default -- from which you may retrieve it later.

Zend_Application_Resource_Router can be used to configure the router as it is registered with the Front Controller. Configuration options are per the Zend_Controller_Router_Route options.

Zend_Application_Resource_Session allows you to configure Zend_Session as well as optionally initialize a session SaveHandler.

To set a session save handler, simply pass the saveHandler (case insensitive) option key to the resource. The value of this option may be one of the following:

• String : A string indicating a class implementing Zend_Session_SaveHandler_Interface that should be instantiated.

• Array : An array with the keys "class" and, optionally, "options", indicating a class implementing Zend_Session_SaveHandler_Interface that should be instantiated and an array of options to provide to its constructor.

• Zend_Session_SaveHandler_Interface: an object implementing this interface.

Any other option keys passed will be passed to Zend_Session::setOptions() to configure Zend_Session.

Note: Bootstrap your database first!
If you are configuring the Zend_Session_SaveHandler_DbTable session save handler, you must first configure your database connection for it to work. Do this by either using the Db resource -- and make sure the "resources.db" key comes prior to the "resources.session" key -- or by writing your own resource that initializes the database, and specifically sets the default Zend_Db_Table adapter.

Zend_Application_Resource_Translate will initialize a Zend_Translate adapter based on the options passed to it.

The following configuration keys are recognized:

• adapter : Zend_Translate adapter type. The default adapter is array if not specified.

• data : path to translation.

• locale : defining the locale to be used in translation. By default, the locale can be detected automatically or forcing with a Zend_Locale instance store in Zend_Registry with a single locale.

• options : the options are different for each adapter. See the section Options for adapters for more details.

• registry : the custom key to store the Zend_Translate instance in the registry. By default, the key is Zend_Translate.

• cache : the name of the cache template or an instance of Zend_Cache_Core to use as cache for Zend_Translate_Adapter. The goal is to accelerate the loading specialy for the XML based files.

Zend_Application_Resource_View can be used to configure a Zend_View instance. Configuration options are per the Zend_View options.

Once done configuring the view instance, it creates an instance of Zend_Controller_Action_Helper_ViewRenderer and registers the ViewRenderer with Zend_Controller_Action_HelperBroker -- from which you may retrieve it later.