Details
-
Sub-task
-
Status: Resolved
-
Minor
-
Resolution: Incomplete
-
1.1-286-COMPATIBILITY
-
None
Description
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.