[
https://jira.jboss.org/browse/GTNPORTAL-1318?page=com.atlassian.jira.plug...
]
Khoi Nguyen commented on GTNPORTAL-1318:
----------------------------------------
Currently, we could set default portal different of 'classic' but we couldn't
remove 'classic' or other one. With this patch, i define a new plugin for ignore
some portal by external configuration file
Provide a way to disable 'classic'
----------------------------------
Key: GTNPORTAL-1318
URL:
https://jira.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
Fix For: 3.2.0-GA
Attachments: GTNPORTAL-1318.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 contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira