[gatein-issues] [JBoss JIRA] (GTNPORTAL-619) Define a model object for site in GateIn

[Boleslaw Dawidowicz (JIRA)]

     [ https://issues.jboss.org/browse/GTNPORTAL-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boleslaw Dawidowicz updated GTNPORTAL-619:
------------------------------------------

    Fix Version/s: 3.2.0-GA
                       (was: 3.2.0-CR01)

    
> Define a model object for site in GateIn
> ----------------------------------------
>
>                 Key: GTNPORTAL-619
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-619
>             Project: GateIn Portal
>          Issue Type: Feature Request
>            Reporter: Minh Hoang TO
>             Fix For: 3.2.0-GA
>
>
> Up to now, we have:
> 1. PortalConfig wrapps information on skin/layout/permissions ( view/edit) of a site
> 2. UserPortalConfig wrapps all navigations of a user and one PortalConfig
> From my point of view, when we map the model with UI component, it is logical to have
>  PortalConfig  <---> UIPortal
>  UserPortalConfig  <---> UIPortalApplication
> With the feature of portal/group/user layout, we have already PortalConfg corresponding to different site. Anyway, as the PortalConfig does not contain any information on navigation. PortalConfig has been not equivalent to UIPortal. We could see the assymetric mapping methods in PortalDataMapper class
> - From model to UIPortal,  UserPortalConfig object is required
> - Whereas from UIPortal to model, only PortalConfig object is required
>   Following the implement of multiple UIPortal, we must have a model object equivalent to it. Me and Trong discussed on SiteConfig  ( as a lack of time, i merely added the mock of this class into project) which wrapps information on skin/layout/permission (UI permission)  and navigation ( now UIPortal manages one and only one PageNavigation)
>  
>  My suggestion is to implement SiteConfig and make those changes:
>  1. Add a lazy cache of SiteConfig into UserPortalConfig
>  2. Maps UIPortal to SiteConfig in  PortalDataMapper
>  3. Add necessary persistent methods in MOP
>  4. Update relevant code

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira