[gatein-issues] [JBoss JIRA] Created: (GTNPORTAL-1610) Cache portal config for the scope of the request

Marek Posolda (JIRA) jira-events at lists.jboss.org
Fri Oct 29 06:55:54 EDT 2010


Cache portal config for the scope of the request
------------------------------------------------

                 Key: GTNPORTAL-1610
                 URL: https://jira.jboss.org/browse/GTNPORTAL-1610
             Project: GateIn Portal
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Performance
    Affects Versions: 3.1.0-GA
         Environment: EPP 5.1.0 ER3
            Reporter: Marek Posolda
            Assignee: Julien Viet


I found another thing for logged user case performance, which can be improved. Issue is that method UserPortalConfigService.getUserPortalConfig() is called two times during HTTP request of logged user. And this method is expensive, because it performs other calls to IDM and DataStorage. So it should be possible to call it only once per HTTP request.

Now it's called from:

1. LocalizationLifecycle.onStartRequest()

2. PortalStateManager.restoreUIRootComponent() . After this call is obtained UserPortalConfig saved as attribute into PortalRequestContext.

It should be possible to save it into PortalRequestContext after LocalizationLifecycle.onStartRequest(), so that PortalStateManager.restoreUIRootComponent() can read it from PortalRequestContext. Or create another Lifecycle class for this purpose (Something similar to UserProfileLifecycle, which is doing similar thing for obtain UserProfile) ? 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the gatein-issues mailing list