Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1122488

Summary: Rest API - displayNames of spaces navigation nodes are displayed as variables
Product: [JBoss] JBoss Enterprise Portal Platform 6 Reporter: mgottval <mgottval>
Component: PortalAssignee: Peter Palaga <ppalaga>
Status: CLOSED NEXTRELEASE QA Contact: Tomas Kyjovsky <tkyjovsk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bdawidow, epp-bugs, mvecera
Target Milestone: ER05   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Cause: The Portal API implementation is not handling WebUI style localization place holders in displayNames field of a navigation node. Consequence: The placeholders of the form #{my.key} are returned verbatim from Node.getDisplayNames() Workaround (if any): There is no workaround for existing portals. For new portals, one should avoid using #{my.key} placeholders in navigation.xml files. One should rather use multiple <label> elements with xml:lang attribute set, like <label xml:lang="en">My English Label</label> for English. Result: See Consequence.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-31 11:46:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mgottval 2014-07-23 11:29:51 UTC 
When node of existing space navigation is accessed, list of display names have wrong value - variable instead of the value.
e.g.:
link: http://localhost:8080/rest/private/managed-components/api/spaces/platform/administrators/navigation/administration

"displayNames" : [{"value" : "#{administration.title}"}]
Comment 2 Peter Palaga 2014-07-30 15:27:00 UTC 
https://github.com/gatein/gatein-portal/pull/893 sent to upstream
Comment 3 Peter Palaga 2014-07-31 11:46:34 UTC 
Although the fix is ready, and will probably be included in GateIn master soon, we have decided that it is too late and risky to include it in JBoss Portal 6.2. Through GateIn master, the fix will reach JBoss Portal 6.3.