Bug 794455 (JBEPP-1495) - Outdated location of LocalePolicy configuration in docs
Summary: Outdated location of LocalePolicy configuration in docs
Keywords:
Status: CLOSED UPSTREAM
Alias: JBEPP-1495
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Documentation
Version: 5.2.0.Docs.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.1.Docs.GA
Assignee: JPP Docs Team
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-30 18:26 UTC by mposolda
Modified: 2025-02-10 03:15 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:15:24 UTC
Type: Enhancement
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 793622 0 high CLOSED Move LocalePolicy configuration outside of JAR file 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBEPP-1495 0 None Closed Outdated location of LocalePolicy configuration in docs 2012-03-23 00:54:55 UTC

Internal Links: 793622

Description mposolda 2012-01-30 18:26:26 UTC
project_key: JBEPP

LocalePolicy is now configured in gatein.ear/02portal.war/WEB-INF/conf/portal/web-configuration.xml, but docs is saying gatein.ear/lib/exo.portal.webui.portal.jar/conf/configuration.xml which is not correct. Docs needs to be fixed.

See related GTNPORTAL documentation commit https://source.jboss.org/changelog/GateIn?cs=8325 . This needs to be ported into EPP documentation as well. Correct location of file in EPP documentation should be: JBOSS_HOME/server/<PROFILE>/deploy/gatein.ear/02portal.war/WEB-INF/conf/portal/web-configuration.xml .

Comment 1 mposolda 2012-01-30 18:30:47 UTC
Link: Added: This issue relates to JBEPP-702


Comment 2 Jared MORGAN 2012-03-19 04:40:06 UTC
I have made the change as prescribed.

Comment 8 Red Hat Bugzilla 2025-02-10 03:15:24 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.