Bug 793912 (JBEPP-983)

Summary: Different portlet names for remote portlets added in "Portlet" menu
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Michal Vanco <mvanco>
Component: PortalAssignee: claprun <claprun>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.1.1.DEV01CC: mvecera, theute
Target Milestone: ---   
Target Release: 5.2.0.DEV02   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-983
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
EPP5.1.1 DEV02
Last Closed: 2011-08-08 09:05:22 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:
Attachments:
Description Flags
GTNPORTAL-1941.patch none

Description Michal Vanco 2011-06-21 11:37:09 UTC
project_key: JBEPP

See details at GTNPORTAL-1941

Comment 1 Michal Vanco 2011-06-21 11:37:26 UTC
Link: Added: This issue is related to GTNPORTAL-1941


Comment 3 Chris Laprun 2011-08-05 07:55:26 UTC
Successfully tested in API branch, was unable to get trunk to run properly to check that it worked fine there as well. :(

Comment 4 Chris Laprun 2011-08-05 07:55:26 UTC
Attachment: Added: GTNPORTAL-1941.patch


Comment 5 Thomas Heute 2011-09-22 06:48:12 UTC
Release Notes Docs Status: Added: Not Yet Documented


Comment 6 Chris Laprun 2011-09-22 09:24:59 UTC
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: An inconsistency in how portlets are handled across different part of the administration interface resulted in an error when remote portlets were added to a category from the "Portlet" tab of the Application Registry. The inconsistency has now be resolved and it should be now possible to properly display remote portlets regardless of how they were added to categories.