[JBoss JIRA] Created: (GTNPORTAL-629) Provide a public and documented way to access portlet contextual information (title, description, ....)
by Tugdual Grall (JIRA)
Provide a public and documented way to access portlet contextual information (title, description, ....)
-------------------------------------------------------------------------------------------------------
Key: GTNPORTAL-629
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-629
Project: GateIn Portal
Issue Type: Feature Request
Components: PC integration
Reporter: Tugdual Grall
Priority: Optional
In GateIn it is possible to edit some contextual information
- title, description, size, ...
- permissions, ...
it would be interesting to provide a simple way for the gateIn developer to access (read YES / write?) those information. (public render parameter, but should be implicit, since it does not look good to force the user to change an XML file to access information that is present in the code)
--
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-619) Define a model object for site in GateIn
by Minh Hoang TO (JIRA)
Define a model object for site in GateIn
----------------------------------------
Key: GTNPORTAL-619
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-619
Project: GateIn Portal
Issue Type: Task
Reporter: Minh Hoang TO
Up to now, we have:
1. PortalConfig wrapps information on skin/layout/permissions ( view/edit) of a site
2. UserPortalConfig wrapps all navigations of a user and one PortalConfig
>From my point of view, when we map the model with UI component, it is logical to have
PortalConfig <---> UIPortal
UserPortalConfig <---> UIPortalApplication
With the feature of portal/group/user layout, we have already PortalConfg corresponding to different site. Anyway, as the PortalConfig does not contain any information on navigation. PortalConfig has been not equivalent to UIPortal. We could see the assymetric mapping methods in PortalDataMapper class
- From model to UIPortal, UserPortalConfig object is required
- Whereas from UIPortal to model, only PortalConfig object is required
Following the implement of multiple UIPortal, we must have a model object equivalent to it. Me and Trong discussed on SiteConfig ( as a lack of time, i merely added the mock of this class into project) which wrapps information on skin/layout/permission (UI permission) and navigation ( now UIPortal manages one and only one PageNavigation)
My suggestion is to implement SiteConfig and make those changes:
1. Add a lazy cache of SiteConfig into UserPortalConfig
2. Maps UIPortal to SiteConfig in PortalDataMapper
3. Add necessary persistent methods in MOP
4. Update relevant code
--
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-647) GadgetDashboard : Can create a tab with a public page
by Benjamin Paillereau (JIRA)
GadgetDashboard : Can create a tab with a public page
-----------------------------------------------------
Key: GTNPORTAL-647
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-647
Project: GateIn Portal
Issue Type: Bug
Affects Versions: 3.0.0-Beta05-CP01
Reporter: Benjamin Paillereau
For example, we have a page in the site named "news"
If I go on my Dashboard, i can create a tab named "news"
=> we show the "news" site page inside the dashboard
=> the next time i want to go go back on my dashboard, i am redirected automatically to the "news" site page, not the user one.
1/ It's normal for a user to create any tab with any name so we can't filter page names per user
Solution : user's page should be in a private path (/portal/public/classic/users/root/my-page
It should be the same for Group pages as we can end up with two pages with the same page name.
--
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