[
https://jira.jboss.org/browse/GTNPORTAL-1388?page=com.atlassian.jira.plug...
]
Julien Viet updated GTNPORTAL-1388:
-----------------------------------
Description:
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
For event type URL, those values should be empty.
was:
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
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
For event type URL, those values should be empty.
--
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