\org_openpsa_products_handler_product_latest

Execution handler subclass, to be used with the request switch
in midcom_baseclasses_components_request.

Use the various event handlers to customize startup.

The basic idea is that you have separate instances of this type for the various
operations in your main viewer class. This avoids cluttering up the viewer class
and gives you better maintainability due to smaller code files.

Under normal operation within the same component you don't need to think about any
specialties, the member variables are just references to the main request class
(also known as "viewer class").

Noteworthy is the ability to export handlers for usage in other components in
both libraries and full components. To make the exported handler work correctly,
you need to set $this->_component to the corresponding value of the exporting
component. In this case, the startup code will take the main l10n instance, the
component data storage and the configuration from the exporting component.
The configuration in this case is merged from the global defaults (constructed
during component/library startup) and the configuration parameters set on the topic
where it is invoked.

Note, that the export "mode" is only invoked if and only if the component of
the handler is different of the component of the main request class.

Type

Tags

Methods

initialize()

Initializes the request handler class, called by the component interface after
instantiation.

Be aware that it is possible that a handler can come from a different component
(or library) than the master class. Take this into account when getting the
component data storage, configuration and l10n instances. Configuration is merged
during runtime based on the system defaults and all parameters attached to the
topic we're currently operating on.