[JBoss JIRA] (GTNPORTAL-3349) Wildcard membership doesn't resolved in OrganizationPortlet and Group management
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3349?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3349:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Wildcard membership doesn't resolved in OrganizationPortlet and Group management
> --------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3349
> URL: https://issues.jboss.org/browse/GTNPORTAL-3349
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.7.0.Final
> Reporter: Vu Viet Phuong
> Assignee: Tuyen Nguyen The
> Fix For: 3.7.0.Final
>
> Attachments: addGroupUserForm.png, groupNavigation.png
>
> Original Estimate: 3 hours
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> - In Organization portlet --> Group management. When choose one group, the main panel show list of users belongs to that group, and a form to add more user
> Only user that is admin of that group can see that form (a user that have admin membership OR Wildcard membership)
> But currently, one user that has Wildcard membership doesn't see the form
> - In Group navigation management: Go to Group menu --> Manage group
> This portlet allow to manage group navigation, and only "Makeable" membership user can add group navigation
> And this is the same to above case, user that has Wildcard membership must be allow to add group navigation
> The solution is instead of using groupDAO#findGroupByMembership, we need to use groupDAO#resolveGroupByMembership
> Pls look at attached image to find the form and the add group nav button
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (GTNPORTAL-3348) NPE when saving Portal Layout
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3348?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3348:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> NPE when saving Portal Layout
> -----------------------------
>
> Key: GTNPORTAL-3348
> URL: https://issues.jboss.org/browse/GTNPORTAL-3348
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.7.0.Final
> Reporter: Trong Tran
> Assignee: Tuyen Nguyen The
> Fix For: 3.7.0.Final
>
> Original Estimate: 6 hours
> Time Spent: 6 hours
> Remaining Estimate: 0 minutes
>
> There is NPE when we just do save on Site Layout:
> {code}
> java.lang.NullPointerException
> at org.exoplatform.portal.webui.portal.UIPortalComposer.save(UIPortalComposer.java:222)
> at org.exoplatform.portal.webui.portal.UIPortalComposer.access$000(UIPortalComposer.java:98)
> at org.exoplatform.portal.webui.portal.UIPortalComposer$FinishSiteEditionActionListener.execute(UIPortalComposer.java:427)
> at org.exoplatform.webui.event.Event.broadcast(Event.java:97)
> at org.exoplatform.webui.core.lifecycle.Lifecycle.processAction(Lifecycle.java:51)
> at org.exoplatform.webui.core.UIComponent.processAction(UIComponent.java:119)
> at org.exoplatform.portal.webui.workspace.UIPortalApplicationLifecycle.processAction(UIPortalApplicationLifecycle.java:73)
> at org.exoplatform.portal.webui.workspace.UIPortalApplicationLifecycle.processAction(UIPortalApplicationLifecycle.java:36)
> at org.exoplatform.webui.core.UIComponent.processAction(UIComponent.java:119)
> at org.exoplatform.webui.core.UIApplication.processAction(UIApplication.java:123)
> at org.exoplatform.portal.webui.workspace.UIPortalApplication.processAction(UIPortalApplication.java:779)
> at org.exoplatform.portal.application.PortalRequestHandler.processRequest(PortalRequestHandler.java:210)
> at org.exoplatform.portal.application.PortalRequestHandler.execute(PortalRequestHandler.java:167)
> {code}
> This problem appears when the logged-in user doesn't have UserProfile. I do think there are also other places that we need to fix
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (GTNPORTAL-3349) Wildcard membership doesn't resolved in OrganizationPortlet and Group management
by Tuyen Nguyen The (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3349?focusedWorklogId=12430411&... ]
Tuyen Nguyen The logged work on GTNPORTAL-3349:
-----------------------------------------------
Author: Tuyen Nguyen The
Created on: 15/Dec/13 10:44 PM
Start Date: 12/Dec/13 10:44 PM
Worklog Time Spent: 3 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 3 hours)
Time Spent: 3 hours
Worklog Id: (was: 12430411)
> Wildcard membership doesn't resolved in OrganizationPortlet and Group management
> --------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3349
> URL: https://issues.jboss.org/browse/GTNPORTAL-3349
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.7.0.Final
> Reporter: Vu Viet Phuong
> Assignee: Tuyen Nguyen The
> Fix For: 3.7.0.Final
>
> Attachments: addGroupUserForm.png, groupNavigation.png
>
> Original Estimate: 3 hours
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> - In Organization portlet --> Group management. When choose one group, the main panel show list of users belongs to that group, and a form to add more user
> Only user that is admin of that group can see that form (a user that have admin membership OR Wildcard membership)
> But currently, one user that has Wildcard membership doesn't see the form
> - In Group navigation management: Go to Group menu --> Manage group
> This portlet allow to manage group navigation, and only "Makeable" membership user can add group navigation
> And this is the same to above case, user that has Wildcard membership must be allow to add group navigation
> The solution is instead of using groupDAO#findGroupByMembership, we need to use groupDAO#resolveGroupByMembership
> Pls look at attached image to find the form and the add group nav button
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (GTNPORTAL-3322) Improvements of handling of <priority> in navigation.xml
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3322?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3322:
------------------------------------
Description:
This is followup of GTNPORTAL-2751, GTNPORTAL-3324 and GTNPORTAL-3350.
(1) Introduce {{PageNavigation.UNDEFINED_PRIORITY}} constant and use it instead of {{-1}} literal as {{PageNavigation.priority}} value.
(2) {{UNDEFINED_PRIORITY}} and its usage should be described in comments.
(3) Fix the comparator in [UserPortalImpl|https://github.com/gatein/gatein-portal/blob/master/compon...] as it does not impose a total ordering as required by the Comparator interface: "The implementor must ensure that sgn(compare(x, y)) == -sgn(compare(y, x)) for all x and y." This does not hold when comparing two nodes both having priority -1.
was:
This is followup of GTNPORTAL-2751, GTNPORTAL-3297 and GTNPORTAL-3350.
(1) Introduce {{PageNavigation.UNDEFINED_PRIORITY}} constant and use it instead of {{-1}} literal as {{PageNavigation.priority}} value.
(2) {{UNDEFINED_PRIORITY}} and its usage should be described in comments.
(3) Fix the comparator in [UserPortalImpl|https://github.com/gatein/gatein-portal/blob/master/compon...] as it does not impose a total ordering as required by the Comparator interface: "The implementor must ensure that sgn(compare(x, y)) == -sgn(compare(y, x)) for all x and y." This does not hold when comparing two nodes both having priority -1.
> Improvements of handling of <priority> in navigation.xml
> --------------------------------------------------------
>
> Key: GTNPORTAL-3322
> URL: https://issues.jboss.org/browse/GTNPORTAL-3322
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.7.0.Final
>
>
> This is followup of GTNPORTAL-2751, GTNPORTAL-3324 and GTNPORTAL-3350.
> (1) Introduce {{PageNavigation.UNDEFINED_PRIORITY}} constant and use it instead of {{-1}} literal as {{PageNavigation.priority}} value.
> (2) {{UNDEFINED_PRIORITY}} and its usage should be described in comments.
> (3) Fix the comparator in [UserPortalImpl|https://github.com/gatein/gatein-portal/blob/master/compon...] as it does not impose a total ordering as required by the Comparator interface: "The implementor must ensure that sgn(compare(x, y)) == -sgn(compare(y, x)) for all x and y." This does not hold when comparing two nodes both having priority -1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (GTNPORTAL-3322) Improvements of handling of <priority> in navigation.xml
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3322?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3322:
------------------------------------
Description:
This is followup of GTNPORTAL-2751, GTNPORTAL-3297 and GTNPORTAL-3350.
(1) Introduce {{PageNavigation.UNDEFINED_PRIORITY}} constant and use it instead of {{-1}} literal as {{PageNavigation.priority}} value.
(2) {{UNDEFINED_PRIORITY}} and its usage should be described in comments.
(3) Fix the comparator in [UserPortalImpl|https://github.com/gatein/gatein-portal/blob/master/compon...] as it does not impose a total ordering as required by the Comparator interface: "The implementor must ensure that sgn(compare(x, y)) == -sgn(compare(y, x)) for all x and y." This does not hold when comparing two nodes both having priority -1.
was:Introduce {{PageNavigation.UNDEFINED_PRIORITY}} constant and use it instead of {{-1}} literal as {{PageNavigation.priority}} value. {{UNDEFINED_PRIORITY}} and its usage should be described in comments. This is followup of GTNPORTAL-2751.
> Improvements of handling of <priority> in navigation.xml
> --------------------------------------------------------
>
> Key: GTNPORTAL-3322
> URL: https://issues.jboss.org/browse/GTNPORTAL-3322
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Assignee: Peter Palaga
> Fix For: 3.7.0.Final
>
>
> This is followup of GTNPORTAL-2751, GTNPORTAL-3297 and GTNPORTAL-3350.
> (1) Introduce {{PageNavigation.UNDEFINED_PRIORITY}} constant and use it instead of {{-1}} literal as {{PageNavigation.priority}} value.
> (2) {{UNDEFINED_PRIORITY}} and its usage should be described in comments.
> (3) Fix the comparator in [UserPortalImpl|https://github.com/gatein/gatein-portal/blob/master/compon...] as it does not impose a total ordering as required by the Comparator interface: "The implementor must ensure that sgn(compare(x, y)) == -sgn(compare(y, x)) for all x and y." This does not hold when comparing two nodes both having priority -1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (GTNPORTAL-3351) Could not load user profile for <user> warning
by Peter Palaga (JIRA)
Peter Palaga created GTNPORTAL-3351:
---------------------------------------
Summary: Could not load user profile for <user> warning
Key: GTNPORTAL-3351
URL: https://issues.jboss.org/browse/GTNPORTAL-3351
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.7.0.Final
Reporter: Peter Palaga
Assignee: Marek Posolda
NOT OK: The warning appears in the log when a user (e.g. root) logs in.
{code}
Could not load user profile for <username>
{code}
Expected: no warning.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months