[
https://issues.jboss.org/browse/GTNPORTAL-1941?page=com.atlassian.jira.pl...
]
Chris Laprun resolved GTNPORTAL-1941.
-------------------------------------
Resolution: Partially Completed
Unfortunately, it's not easy to unify the portlet names because the UI is built around
assumptions that don't hold true for WSRP portlets and unifying names would require
changes that I'm not willing to make at this point.
Different portlet names for remote portlets added in
"Portlet" menu
-------------------------------------------------------------------
Key: GTNPORTAL-1941
URL:
https://issues.jboss.org/browse/GTNPORTAL-1941
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: WSRP integration
Affects Versions: 3.1.0-GA
Environment: EPP5.1.1 DEV02 or GateIn trunk (11/06/20)
Reporter: Michal Vanco
Assignee: Chris Laprun
Fix For: 3.2.0-M02
There are 3 options how can be remote portlets added in category in App.registry:
1) auto import - id is: selfv2._richFacesPortlet.richFacesPortlet
2) Add application in category (in Categories menu) - id is:
/richFacesPortlet.richFacesPortlet
3) "Click here to add into categories" in "Portlet" menu - Remote
portlets, id is: richFacesPortlet.richFacesPortlet
When you add remote portlet on page 1) and 2) works fine.
But for third option gives you:
org.gatein.pc.api.NoSuchPortletException: No such portlet
/richFacesPortlet.richFacesPortlet.richFacesPortlet
and portlet isn't rendered on page.
Is there some way how to unify portlet names on different places and fix remote portlet
added in Portlet menu?
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira