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 "Dennis Dam (JIRA)" <je...@portals.apache.org> on 2008/05/15 16:27:55 UTC
[jira] Created: (JS2-867) Optional portlet session caching of
layout view templates
Optional portlet session caching of layout view templates
---------------------------------------------------------
Key: JS2-867
URL: https://issues.apache.org/jira/browse/JS2-867
Project: Jetspeed 2
Issue Type: Improvement
Components: Layout
Affects Versions: 2.1.3
Reporter: Dennis Dam
Assignee: Dennis Dam
Priority: Minor
Fix For: 2.2
Layout template locations are stored in the portlet session. This has probably been introduced to increase performance of template localization. In some usecases different PSML fragments use the same ID, but with different viewpage preferences. In these cases the different fragments share the same viewpage, namely the viewpage of the first fragment that is rendered.
This patch will make the caching of templates in the portlet session optional through a Jetspeed property. The default behaviour will remain the same: templates are cached in the portlet session.
--
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] Commented: (JS2-867) Optional portlet session caching of
layout view templates
Posted by "Dennis Dam (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597146#action_12597146 ]
Dennis Dam commented on JS2-867:
--------------------------------
this issue will also be fixed in the Jetspeed-2.1.3-postrelease branch
> Optional portlet session caching of layout view templates
> ---------------------------------------------------------
>
> Key: JS2-867
> URL: https://issues.apache.org/jira/browse/JS2-867
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Layout
> Affects Versions: 2.1.3
> Reporter: Dennis Dam
> Assignee: Dennis Dam
> Priority: Minor
> Fix For: 2.2
>
>
> Layout template locations are stored in the portlet session. This has probably been introduced to increase performance of template localization. In some usecases different PSML fragments use the same ID, but with different viewpage preferences. In these cases the different fragments share the same viewpage, namely the viewpage of the first fragment that is rendered.
> This patch will make the caching of templates in the portlet session optional through a Jetspeed property. The default behaviour will remain the same: templates are cached in the portlet session.
--
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-867) Optional portlet session caching of
layout view templates
Posted by "Dennis Dam (JIRA)" <je...@portals.apache.org>.
[ https://issues.apache.org/jira/browse/JS2-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Dam resolved JS2-867.
----------------------------
Resolution: Fixed
fixed in the trunk and the jetspeed-2.1.3-postrelease branch
> Optional portlet session caching of layout view templates
> ---------------------------------------------------------
>
> Key: JS2-867
> URL: https://issues.apache.org/jira/browse/JS2-867
> Project: Jetspeed 2
> Issue Type: Improvement
> Components: Layout
> Affects Versions: 2.1.3
> Reporter: Dennis Dam
> Assignee: Dennis Dam
> Priority: Minor
> Fix For: 2.2
>
>
> Layout template locations are stored in the portlet session. This has probably been introduced to increase performance of template localization. In some usecases different PSML fragments use the same ID, but with different viewpage preferences. In these cases the different fragments share the same viewpage, namely the viewpage of the first fragment that is rendered.
> This patch will make the caching of templates in the portlet session optional through a Jetspeed property. The default behaviour will remain the same: templates are cached in the portlet session.
--
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