[JBoss JIRA] Created: (GTNPORTAL-1431) UIPortlet management of events, PRPs and mode information is sub-optimal
by Chris Laprun (JIRA)
UIPortlet management of events, PRPs and mode information is sub-optimal
------------------------------------------------------------------------
Key: GTNPORTAL-1431
URL: https://jira.jboss.org/browse/GTNPORTAL-1431
Project: GateIn Portal
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: PC integration
Affects Versions: 3.1.0-GA
Reporter: Chris Laprun
Assignee: Matt Wringe
Priority: Minor
Fix For: 3.2.0-GA
Attachments: uiportlet.patch
Attached is a patch that removes unneeded code and cleans-up processing. However, some of the things that were done didn't quite make sense (in particular management of the "config" mode, see inline comments in the patch) so I'd like someone who knows more about the UIPortlet codebase than me to check my modifications. Note that in testing WSRP2 I didn't see any problems with that patch.
--
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-1388) Determine navigation target before entering webui layer
by Julien Viet (JIRA)
Determine navigation target before entering webui layer
-------------------------------------------------------
Key: GTNPORTAL-1388
URL: https://jira.jboss.org/browse/GTNPORTAL-1388
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Julien Viet
Assignee: Trong Tran
Fix For: 3.2.0-GA
The PortalRequestContext when it is created should fully determine the navigation target decomposed into:
- target site type
- target site name
- target navigation path, the value being a normalized path that starts with a /
Examples:
/private/classic -> "portal" site type, "classic" site name and "/" target navigation path
/private/classic/home -> "portal" site type, "classic" site name and "/home" target navigation path
/public/classic/ -> "portal" site type, "classic" site name and "/" target navigation path
/private/classic/Tab_0 -> "user" site type, "root" site name (for user root") and /Tab_0 navigation path
/private/classic/administration/registry -> "group" site type, "/platform/administrators" site name and "/administration/registry" navigation path
So those values are determined before the request happens and then can be used with the webui code to generate potential navigation events
--
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