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 )
Link: Added: This issue depends GTNPORTAL-1718
Link: Added: This issue is related to JBQA-4009
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.
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.
Release Notes Docs Status: Added: Needs More Info Primary SME: Added: theute
Labels: Added: EPP_5_2_1_Candidate
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.
Link: Added: This issue is related to JBEPP-1495
Labels: Removed: EPP_5_2_1_Candidate
Release notes not needed (I don't see "-" flag for technical notes)