Refactoring of SharedRenderParameterProvider and EventProvider registration
steps to support hot-deployment.
------------------------------------------------------------------------------------------------------------
Key: PLUTO-284
URL: http://issues.apache.org/jira/browse/PLUTO-284
Project: Pluto
Issue Type: Sub-task
Components: portal driver
Affects Versions: 1.1-286-COMPATIBILITY
Reporter: Tuomas Kiviaho
Priority: Minor
The current implementation leads to inconsistency of state when portlet.xml is
changed between (pluto aware) hot-deployments, because supported processing
events are registered and cached at render phase, but their existence is never
rechecked. Pages are required to be rendered in order for the providers to have
the knowledge of events and parameters.
Render section of PlutoPortalDriver contains event and shared render parameter
registrations that could be refactored to use PortletContextManager's portlet
registry listeners or registrations could be postponed to be done on the fly as
is done with SupportedModesService. Both suggestions require merging of recent
changes in trunk to this branch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
