[JBoss JIRA] (GTNWCM-20) Create gatein-wcm-ui-distribution and gatein-wcm-ui-integration modules
by Lucas Ponce (JIRA)
[ https://issues.jboss.org/browse/GTNWCM-20?page=com.atlassian.jira.plugin.... ]
Lucas Ponce updated GTNWCM-20:
------------------------------
Affects Version/s: 1.0
> Create gatein-wcm-ui-distribution and gatein-wcm-ui-integration modules
> -----------------------------------------------------------------------
>
> Key: GTNWCM-20
> URL: https://issues.jboss.org/browse/GTNWCM-20
> Project: GateIn WCM
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0
> Environment: Background: gatein-wcm will contain portlets, thus having some kind of dependency on GateIn. To get gatein-wcm working (and test) one would have to: unzip EAP, unzip ModeShape, unzip Gatein, unzip WCM, unzip WCM UI - the order is not definitive.
> * gatein-wcm-ui-distribution will prepare a ZIP containing gatein-wcm
> * gatein-wcm-ui-integration modules will test all the above ZIPs together
> Reporter: Peter Palaga
> Assignee: Peter Palaga
>
--
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, 2 months
[JBoss JIRA] (GTNPORTAL-3320) Set Root password feature not work with "gtn" password
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3320?page=com.atlassian.jira.pl... ]
Peter Palaga updated GTNPORTAL-3320:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Rejected
Closing as GTNPORTAL-3315 renders this unnecessary. Please reopen this issue and the linked pull request if you disagree.
> Set Root password feature not work with "gtn" password
> ------------------------------------------------------
>
> Key: GTNPORTAL-3320
> URL: https://issues.jboss.org/browse/GTNPORTAL-3320
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: - Tomcat 7.0.47
> Reporter: Hai Nguyen
> Assignee: Tuyen Nguyen The
> Original Estimate: 4 hours
> Time Spent: 5 hours
> Remaining Estimate: 0 minutes
>
> Step to reproduce:
> - Comment out "gatein.portal.setup.initialpassword.root" in gate/conf/configuration.properties
> - Access to /portal then redirected to /portal/setupaction
> - Setup password for Root by "gtn"
> - Login with root
> - The request always is waiting and could not finish => NOK
--
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, 2 months
[JBoss JIRA] (GTNPORTAL-3285) Logic of deleting user is not proper
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3285?page=com.atlassian.jira.pl... ]
Peter Palaga commented on GTNPORTAL-3285:
-----------------------------------------
I am not sure what the last sentence of the previous comment means for the linked pull request. It means that the PR is unnecessary, right? Could you please comment and close the PR if so?
> Logic of deleting user is not proper
> ------------------------------------
>
> Key: GTNPORTAL-3285
> URL: https://issues.jboss.org/browse/GTNPORTAL-3285
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Tuyen Nguyen The
> Assignee: Tuyen Nguyen The
>
> I try to add a listener to not allow delete Platform users. for example:
> {code}
> public class IntranetUserEventListenerImpl extends UserEventListener {
> @Override
> public void preDelete(User user) throws Exception {
> //don't allow delete user
> throw new MessageException(new ApplicationMessage("IntranetUserEventListener.msg.delete-user-read-only-mode-error", null, ApplicationMessage.WARNING));
> }
> {code}
> This listener can help to not allow delete user, but all memberships of user still are deleted.
> Check logic of deleting users (in file https://github.com/exoplatform/gatein-portal/blob/3.5.x-PLF/component/ide...): we can see it deletes all membershis of an user before broadcast event "preDelete"
> {code}
> public User removeUser(String userName, boolean broadcast) throws Exception {
> //...
>
> try {
> // Remove all memberships and profile first
> orgService.getMembershipHandler().removeMembershipByUser(userName, false);
> orgService.getUserProfileHandler().removeUserProfile(userName, false);
> } catch (Exception e) {
> handleException("Cannot cleanup user relationships: " + userName + "; ", e);
> }
> User exoUser = getPopulatedUser(userName, session);
> if (broadcast) {
> preDelete(exoUser);
> }
> try {
> session.getPersistenceManager().removeUser(foundUser, true);
> } catch (IdentityException e) {
> handleException("Cannot remove user: " + userName + "; ", e);
> }
> //...
> }
> {code}
> Expectation:
> 1) broadcast preDelete(exoUser) should be run before delete anything
> 2) Delete user and its membership should be run in one transaction
--
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, 2 months