[JBoss JIRA] Created: (GTNWSRP-16) Visibility of remote portlets in App.registry
by Michal Vanco (JIRA)
Visibility of remote portlets in App.registry
---------------------------------------------
Key: GTNWSRP-16
URL: https://jira.jboss.org/jira/browse/GTNWSRP-16
Project: GateIn WSRP
Issue Type: Bug
Components: Admin GUI
Affects Versions: 1.0.0
Reporter: Michal Vanco
Assignee: Chris Laprun
When I create new consumer, I can see remote portlet in App.registry
(Portlets/Remote), when I click Auto Import, category with remote
portlet is created.
When I deactivate consumer, I can't see the portlet in App.category
(Portlets/Remote), but when I click Auto import, category with remote
portlet is still there. Is it ok? Shouldn't it dissapper if it is not
present?
I am also able to add this remote portlet to page and it works.
After I delete consumer, I can still see the caterory with portlet in
App.registry, when click Auto import, in log is:
ERROR [STDERR] org.gatein.pc.api.NoSuchPortletException: No such portlet
self./jboss-image-portlet-sample-remotable-GateIn.jboss-image-portlet-sample
And when I add this portlet to page I can see
"This portlet encountered an error and could not be displayed"
and in log is:
org.gatein.pc.api.NoSuchPortletException: No such portlet self./jboss-image-portlet-sample-remotable-GateIn.jboss-image-portlet-sample
I think that when I deactivate/delete consumer, I shouldn't be able to see its portlets anywhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] Created: (GTNPORTAL-1528) parameterized users/groups/memberships permissions setting for EPP 5.
by Gary Hu (JIRA)
parameterized users/groups/memberships permissions setting for EPP 5.
---------------------------------------------------------------------
Key: GTNPORTAL-1528
URL: https://jira.jboss.org/browse/GTNPORTAL-1528
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Gary Hu
In EPP 5, there are many places that need to specify the permission settings for different users, groups and memberships. For example, the admin group setting *:/platform/administrators is referenced by gatein and eXo WCM in many places.
It would be a neater approach if we could use some parameterized setting so that if we need to make a change we just need to modify one place. It's much easier for the user to find/replace the settings.
Here is the proposal. We can define some key/value type properties and add them to the $EPP5_HOME/server/$PROFILE/conf/gatein/configuration.properties file:
gatein.user.owner=root
gatein.group.admin=*:/platform/administrators
gatein.group.user=*:/platform/users
gatein.group.guest=*:/platform/guests
gatein.group.webcontributor=*:/platform/web-contributors
gatein.membership.author=author
gatein.membership.publisher=publisher
gatein.membership.manager=manager
gatein.membership.member=member
And the various gatein and sitepublisher files would then reference them doing something like this: ${gatein.group.admin}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] Created: (GTNPORTAL-1123) portal skins shouldn't need to include screenshots of the other skins
by Matt Wringe (JIRA)
portal skins shouldn't need to include screenshots of the other skins
---------------------------------------------------------------------
Key: GTNPORTAL-1123
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1123
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Matt Wringe
When you switch portal skins you can be shown a preview screenshot of the portal skin to see which one you want to select.
The problem is that for this preview to be shown the current portal skin must contain the image of all the other skins as part of its own css. In order for this to work currently it means when a new skin is created, someone needs to go through all the other skins to add the new skin screenshot image and reference for the new skin. It doesn't make any sense for a portal skin to have references to other skins screenshots.
A portal skin should specify the preview screenshot itself, and the skin switcher should use this to show the screenshot.
[ps: it might also be good to show an image not found image rather than just leave the preview area blank]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months