[
https://issues.apache.org/jira/browse/PLUTO-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma resolved PLUTO-284.
-----------------------------
Resolution: Incomplete
I cannot reproduce nor determine the exact conditions and goals of this issue
anymore.
The codebase has been completely changed anyway.
As no input was provided on this in a long time and the described goal seems to
be beyond the scope of the portal driver (hot-deployments etc.) I'm closing
this now as incomplete.
> Refactoring of SharedRenderParameterProvider and EventProvider registration
> steps to support hot-deployment.
> ------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-284
> URL: https://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
> Fix For: 1.1-286-COMPATIBILITY
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
