| A RenderProcessor is a handler that implements business logic
for a specific render type. In each "render" invocation, ControllerPortlet
will select associated RenderProcessor object and will invoke process
on it. Note RenderProcessor specification is optional unlike ActionProcessor.
RenderProcessors must be programmed in a thread-safe manner, because the
controller will share the same instance for multiple simultaneous
requests. This means you should design with the following items in mind:
- Instance and static variables MUST NOT be used to store information
related to the state of a particular request. They MAY be used to
share global resources across requests for the same action.
- Access to other resources (JavaBeans, session variables, etc.) MUST
be synchronized if those resources require protection. (Generally,
however, resource classes should be designed to provide their own
protection where necessary.
When an RenderProcessor instance is first created, the controller
portlet calls init method with an XML element defining initialization
parameters for the RenderProcessor.
When the controller portlet is to destroyed, it calls destroy method
on all registered RenderProcessors. This method can be used to clean up all resources
used by the RenderProcessor.
author: Padmanabh Dabke author: © 2004 Nabh Information Systems, Inc. All Rights Reserved. |