Bug 794377 (JBEPP-1422)

Summary:	Provide a way to disable 'classic' - GTNPORTAL-1318
Product:	[JBoss] JBoss Enterprise Portal Platform 6	Reporter:	Shaun Appleton <sappleto>
Component:	Portal	Assignee:	Default User <jbpapp-maint>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	epp-bugs, mweiler, theute
Target Milestone:	---
Target Release:	6.0.x
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-1422
Whiteboard:	EPP_6_0_0_Candidate
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	794378 (view as bug list)		Environment:
Last Closed:	2012-09-03 11:38:25 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Shaun Appleton 2011-11-30 12:54:39 UTC

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


*** This bug has been marked as a duplicate of bug 794378 ***