You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Tuomas Kiviaho (JIRA)" <ji...@apache.org> on 2006/12/18 11:12:21 UTC
[jira] Created: (PLUTO-284) Refactoring of
SharedRenderParameterProvider and EventProvider registration steps to
support hot-deployment.
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
[jira] Updated: (PLUTO-284) Refactoring of
SharedRenderParameterProvider and EventProvider registration steps to
support hot-deployment.
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David DeWolf updated PLUTO-284:
-------------------------------
Fix Version/s: 1.1-286-COMPATIBILITY
> 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.
[jira] Resolved: (PLUTO-284) Refactoring of
SharedRenderParameterProvider and EventProvider registration steps to
support hot-deployment.
Posted by "Ate Douma (JIRA)" <ji...@apache.org>.
[ 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.