Bug 793622 (JBEPP-702)

Summary:	Move LocalePolicy configuration outside of JAR file
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	mposolda
Component:	Portal	Assignee:	mposolda
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.1.0.CR01	CC:	epp-bugs, jmorgan, mposolda, mstrukel
Target Milestone:	---
Target Release:	5.2.1.GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-702
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-30 18:30:19 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:
Embargoed:

Description mposolda 2010-12-03 16:38:16 UTC

project_key: JBEPP

I think it will be good to move configuration of LocalePolicy outside of JAR file exo.portal.component.portal-VERSION.jar into some location outside JAR file. For example into gatein.ear/02portal.war/WEB-INF/conf/common-configuration.xml where is also configuration of other locale services like LocaleCofigService, ResourceBundleService etc.

I thing it;s not user friendly for customers if they need to change configuration, which is in JAR file. Especially if this configuration is described in EPP reference guide in chapter 8 - Localization configuration (part 8.1.4 )

Comment 1 mposolda 2010-12-03 16:41:13 UTC

Link: Added: This issue depends GTNPORTAL-1718

Comment 2 mposolda 2010-12-03 16:42:43 UTC

Link: Added: This issue is related to JBQA-4009

Comment 3 mposolda 2010-12-03 16:51:08 UTC

oups, I just noticed that it's already mentioned in reference guide that JAR file should not be changed. But I still think that configuration can be added to some config. file under 02portal.war and customers can easily change it here without copying the configuration from jar file.

Comment 4 Thomas Heute 2010-12-06 09:58:51 UTC

More than that the whole configuration logic should be aligned.

We'll need to decide if we put all default configuration in JARs (Less likely to be modified) and allow for overriding and if we ship also a copy of the configuration files in locations that are easy to access. Or if we just make it in an easy to modify location.

Comment 5 Jared MORGAN 2011-11-17 03:31:41 UTC

Release Notes Docs Status: Added: Needs More Info
Primary SME: Added: theute

Comment 6 hfnukal@redhat.com 2012-01-13 09:43:31 UTC

Labels: Added: EPP_5_2_1_Candidate

Comment 7 mposolda 2012-01-30 18:30:19 UTC

Release Notes Docs Status: Removed: Needs More Info Added: Not Required
Release Notes Text: Added: This issue is outdated . LocalePolicy configuration has been already moved from JAR file to WAR file: gatein.ear/02portal.war/WEB-INF/conf/portal/web-configuration.xml . I think that this does not need to be documented in release notes. 

I created new documentation JIRA JBEPP-1495, because in reference guide is still bad location.

Comment 8 mposolda 2012-01-30 18:30:47 UTC

Link: Added: This issue is related to JBEPP-1495

Comment 9 Thomas Heute 2012-02-09 10:08:45 UTC

Labels: Removed: EPP_5_2_1_Candidate

Comment 10 mposolda 2012-03-22 19:38:20 UTC

Release notes not needed (I don't see "-" flag for technical notes)