[gatein-issues] [JBoss JIRA] (GTNPORTAL-1318) Provide a way to disable 'classic'

[Boleslaw Dawidowicz (JIRA)]

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

Boleslaw Dawidowicz closed GTNPORTAL-1318.
------------------------------------------

    Fix Version/s:     (was: 3.4.0.Final)
       Resolution: Out of Date


Should be covered as part of new Admin UI work
                
> Provide a way to disable 'classic'
> ----------------------------------
>
>                 Key: GTNPORTAL-1318
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-1318
>             Project: GateIn Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.1.0-CR01
>            Reporter: Patrice Lamarque
>            Assignee: Khoi Nguyen
>              Labels: patch_proposed, review_julien, sprint_37
>         Attachments: GTNPORTAL-1318.patch, GTNPORTAL-1318_AND_TestCase.patch
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> The 'classic' portal is builtin in gatein.
> Extension writers will typically want to define their own portal different of 'classic'. They may want to make their own portal the default too.
> Today, the only way to to this is to edit the portal.war and modify the builtin configuration for classic (UserPortalConfigService).
> We need a way to indicate the portal to not attempt to load 'classic', but use another definition instead.

--
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