Bug 794378 - Provide a way to disable 'classic' - GTNPORTAL-1318
Summary: Provide a way to disable 'classic' - GTNPORTAL-1318
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: unspecified
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
: JBEPP-1422 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-30 12:54 UTC by Shaun Appleton
Modified: 2014-02-13 11:58 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: JBEPP-1422
Environment:
Last Closed: 2014-02-13 11:58:11 UTC
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-1422 0 Major Closed Provide a way to disable 'classic' - GTNPORTAL-1318 2014-05-06 11:39:29 UTC

Description Shaun Appleton 2011-11-30 12:54:39 UTC 
++ This bug is a clone of bug 794377 ++

Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000008yJWX
project_key: JBEPP

(form https://issues.jboss.org/browse/GTNPORTAL-1318)
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.

see GTNPORTAL-1318 for further details.
Comment 1 Shaun Appleton 2011-11-30 12:56:35 UTC 
Link: Added: This issue is related to GTNPORTAL-1318
Comment 2 Thomas Heute 2011-12-15 10:26:11 UTC 
Labels: Added: EPP_6_0_0_Candidate
Comment 8 Thomas Heute 2012-09-03 11:38:25 UTC 
*** Bug 794377 has been marked as a duplicate of this bug. ***
Comment 13 Thomas Heute 2014-02-13 11:58:11 UTC 
The proper way would be to do a portal container (not extend /portal with classic site) and disable /portal portal container (doable).
Note You need to log in before you can comment on or make changes to this bug.