You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ate Douma (JIRA)" <je...@portals.apache.org> on 2009/03/30 02:12:50 UTC
[jira] Created: (JS2-945) Provide PortletApplication and
PortletDefinition ResourceBundle lookup and caching from the PortletFactory
Provide PortletApplication and PortletDefinition ResourceBundle lookup and caching from the PortletFactory
----------------------------------------------------------------------------------------------------------
Key: JS2-945
URL: https://issues.apache.org/jira/browse/JS2-945
Project: Jetspeed 2
Issue Type: Improvement
Components: Container, Portlet Registry
Affects Versions: 2.2
Reporter: Ate Douma
Assignee: Ate Douma
Fix For: 2.2
Currently PortletDefinitionImpl provides the lookup and caching of its ResourceBundles itself.
But as this is classloader specific and thereby dependent on the PortletApplication instance, the caching of ResourceBundles should not be done on the PortletDefinitionImpl itself but by the PortletFactory which registers and manages the PortletApplication classloaders.
Furthermore, if we want to move to JPA based persistence, PortletDefinition instances are recreated on the fly (even if coming from the cache), so its clearly not a good location to maintain caches of whatever kind.
Finally, the Portlet 2.0 spec added ResourceBundle support on PortletApplication level as well.
The OM has been updated for that, but not yet the persistence (database) model.
The lookup and caching of these ResourceBundles will also be provided by the PortletFactory (which class name now becomes a little outdated ...)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Resolved: (JS2-945) Provide PortletApplication and
PortletDefinition ResourceBundle lookup and caching from the PortletFactory
Posted by "Ate Douma (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma resolved JS2-945.
---------------------------
Resolution: Fixed
> Provide PortletApplication and PortletDefinition ResourceBundle lookup and caching from the PortletFactory
> ----------------------------------------------------------------------------------------------------------
>
> Key: JS2-945
> URL: https://issues.apache.org/jira/browse/JS2-945
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Container, Portlet Registry
> Affects Versions: 2.2
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.2
>
>
> Currently PortletDefinitionImpl provides the lookup and caching of its ResourceBundles itself.
> But as this is classloader specific and thereby dependent on the PortletApplication instance, the caching of ResourceBundles should not be done on the PortletDefinitionImpl itself but by the PortletFactory which registers and manages the PortletApplication classloaders.
> Furthermore, if we want to move to JPA based persistence, PortletDefinition instances are recreated on the fly (even if coming from the cache), so its clearly not a good location to maintain caches of whatever kind.
> Finally, the Portlet 2.0 spec added ResourceBundle support on PortletApplication level as well.
> The OM has been updated for that, but not yet the persistence (database) model.
> The lookup and caching of these ResourceBundles will also be provided by the PortletFactory (which class name now becomes a little outdated ...)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org