Bug 793981 (JBEPP-1054)

Summary: Remove gadget wrapper portlet from default applications
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Michal Vanco <mvanco>
Component: PortalAssignee: hfnukal <hfnukal>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.1.CR01CC: epp-bugs, mcupak, mvecera, mwringe
Target Milestone: ---   
Target Release: 5.2.0.ER06   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1054
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-03 06:27:43 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michal Vanco 2011-08-09 07:49:41 UTC 
project_key: JBEPP

Remove definition of Gadget wrapper portlet (dashboard/GadgetPortlet) from file:
web/portal/src/main/webapp/WEB-INF/conf/portal/application-registry-configuration.xml

This portlet is never used as standalone portlet (there is horoscope gadget set by default which doesn't work), portlet is used only when any gadget is added on portal page - url is stored in preferences and there is no other way to change url of gadget.

As there is no real usage of standalone portlet, I propose removing portlet definition from default applications available at categories.
Another option is to add portlet preference for URL in portlet.xml, then it would be possible to change it in Edit mode/Preferences tab.

UIGadgetPortlet class should properly handle URLs and well as local:// locations of gadgets.
Comment 1 Matt Wringe 2011-08-25 19:27:12 UTC 
this is more complex than just a cosmetic change of removing a portlet definition from appearing in the application categories.

First of all, any application which can be placed on a page has to correspond to an application which is owned by a category (sometimes referred to as a managed application). We cannot directly add a portlet from PC to a page, it has to be wrapped and configured in a managed application.

Second, this defines the security level of the GadgetPortlet, so there will be issues with who can access this portlet if its removed.

So to properly remove the GadgetPortlet from the application registry, its going to require rewriting how gadgets get wrapped inside portlets and placed on a page. This might not be something we want to add right now since its a bit more than just a bug fix. Since its a minor annoyance, it should just be properly documented what it does in the docs.
Comment 2 Matt Wringe 2011-09-19 19:39:32 UTC 
Link: Added: This issue is related to GTNPORTAL-2110
Comment 3 Matt Wringe 2011-09-19 19:39:33 UTC 
GTNPORTAL-2110 is the jira for tracking the issues with the horoscope gadget from being displayed properly.
Comment 4 hfnukal@redhat.com 2011-11-02 18:38:11 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Comment 5 Thomas Heute 2011-11-03 06:27:19 UTC 
Link: Added: This issue is related to JBEPP-1337
Comment 6 Thomas Heute 2011-11-03 06:27:59 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Not Required