May 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3495) Membership Pagination don't work

by Boubaker Khanfir (JIRA)

Boubaker Khanfir created GTNPORTAL-3495: ------------------------------------------- Summary: Membership Pagination don't work Key: GTNPORTAL-3495 URL: https://issues.jboss.org/browse/GTNPORTAL-3495 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Boubaker Khanfir I attach a new unit test for a bug that I met in PL IDM 1.4.4. Test case description: 1/ add about 10 users in an LDAP group 2/ use SearchCriteria to paginate on the Members of this group => Problem: pagination doesn't work Why does it fails: Because in this method "org.picketlink.idm.impl.store.ldap.LDAPIdentityStoreImpl.resolveRelationships(IdentityStoreInvocationContext, IdentityObject, IdentityObjectRelationshipType, boolean, boolean, String, IdentityObjectSearchCriteria)" the attribute "IdentityObjectSearchCriteria" isn't used for pagination. To workaround this bug I had to use (skipPaginationInMembershipQuery=true). If the UI is buggy without this parameter to "true", I think it has to be *by default "true" in Config class* and may be even delete this option to not use pagination in Membership at all. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNMOP-54) Tests in WorkspaceTestCase are order dependent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNMOP-54?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on GTNMOP-54: ----------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1091114|https://bugzilla.redhat.com/show_bug.cgi?id=1091114] from ASSIGNED to POST > Tests in WorkspaceTestCase are order dependent > ---------------------------------------------- > > Key: GTNMOP-54 > URL: https://issues.jboss.org/browse/GTNMOP-54 > Project: GateIn Model Object for Portal > Issue Type: Bug > Reporter: Peter Palaga > Assignee: Peter Palaga > > Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1091114 > Description of problem: > Community MOP Core project (https://github.com/gatein/gatein-mop/tree/1.3.1.Final/core) has test dependency junit-4.10.jar (managed from gatein-dep-1.4.0.Final). > Prod MOP Core (http://git.app.eng.bos.redhat.com/git/gatein/gatein-mop.git/tree/core?id=...) has test dependency junit-4.11-redhat-1.jar. > There are junit 4.11 release notes: https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.md#t... > Test execution order has changed between junit 4.10 and 4.11. I get test failures in org.gatein.mop.core.api.workspace.WorkspaceTestCase. It depends on order of execution of org.gatein.mop.core.api.workspace.WorkspaceTestCase.testRemoveReferencedTemplate. When the test is runned, all following tests, where a site "portal" is added (.addSite(ObjectType.PORTAL_SITE, "portal")), fails. In junit 4.10 the test is runned in the end of the test file so the tests passed but in 4.11 5 tests fails with ERROR org.chromattic.core.DomainSession - Attempt to insert context EntityContext[state=ObjectStatus[status=TRANSIENT],mapper=EntityMapper[class=class org.gatein.mop.core.api.workspace.PortalSite,typeName=mop:portalsite]] as an existing child with name mop:portal child of node /mop:workspace/mop:portalsites > Version-Release number of selected component (if applicable): > community MOP: 1.3.1.Final with junit 4.10 > prod MOP: 1.3.1.Final-redhat-1 with junit 4.11-redhat-1 > Additional info: > When I declare junit version to 4.11 in community project I get the errors. > When I declare junit version to 4.10-redhat-2 in prod project all tests passed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNMOP-54) Tests in WorkspaceTestCase are order dependent

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNMOP-54?page=com.atlassian.jira.plugin.... ] Peter Palaga commented on GTNMOP-54: ------------------------------------ PR sent https://github.com/gatein/gatein-mop/pull/2 > Tests in WorkspaceTestCase are order dependent > ---------------------------------------------- > > Key: GTNMOP-54 > URL: https://issues.jboss.org/browse/GTNMOP-54 > Project: GateIn Model Object for Portal > Issue Type: Bug > Reporter: Peter Palaga > Assignee: Peter Palaga > > Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1091114 > Description of problem: > Community MOP Core project (https://github.com/gatein/gatein-mop/tree/1.3.1.Final/core) has test dependency junit-4.10.jar (managed from gatein-dep-1.4.0.Final). > Prod MOP Core (http://git.app.eng.bos.redhat.com/git/gatein/gatein-mop.git/tree/core?id=...) has test dependency junit-4.11-redhat-1.jar. > There are junit 4.11 release notes: https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.md#t... > Test execution order has changed between junit 4.10 and 4.11. I get test failures in org.gatein.mop.core.api.workspace.WorkspaceTestCase. It depends on order of execution of org.gatein.mop.core.api.workspace.WorkspaceTestCase.testRemoveReferencedTemplate. When the test is runned, all following tests, where a site "portal" is added (.addSite(ObjectType.PORTAL_SITE, "portal")), fails. In junit 4.10 the test is runned in the end of the test file so the tests passed but in 4.11 5 tests fails with ERROR org.chromattic.core.DomainSession - Attempt to insert context EntityContext[state=ObjectStatus[status=TRANSIENT],mapper=EntityMapper[class=class org.gatein.mop.core.api.workspace.PortalSite,typeName=mop:portalsite]] as an existing child with name mop:portal child of node /mop:workspace/mop:portalsites > Version-Release number of selected component (if applicable): > community MOP: 1.3.1.Final with junit 4.10 > prod MOP: 1.3.1.Final-redhat-1 with junit 4.11-redhat-1 > Additional info: > When I declare junit version to 4.11 in community project I get the errors. > When I declare junit version to 4.10-redhat-2 in prod project all tests passed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3365) Exception swallow in UserDaoImpl.persistUserInfo()

by Lucas Ponce (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3365?page=com.atlassian.jira.pl... ] Lucas Ponce updated GTNPORTAL-3365: ----------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/gatein/gatein-portal/pull/765, https://github.com/gatein/gatein-portal/pull/864 (was: https://github.com/gatein/gatein-portal/pull/765) New PR to resolve small conflicts with master branch. > Exception swallow in UserDaoImpl.persistUserInfo() > -------------------------------------------------- > > Key: GTNPORTAL-3365 > URL: https://issues.jboss.org/browse/GTNPORTAL-3365 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 3.6.3.Final > Reporter: Vu Viet Phuong > Assignee: Vu Viet Phuong > Fix For: 3.6.4.Final, 3.9.0.Final > > Original Estimate: 4 hours > Time Spent: 6 hours > Remaining Estimate: 0 minutes > > Under "{{org.exoplatform.services.organization.idm}}, > focus on : > {code:title=UserDAOImp.java|borderStyle=solid} > public void persistUserInfo(User user, IdentitySession session) throws Exception > { > orgService.flush(); > AttributesManager am = session.getAttributesManager(); > ArrayList attributes = new ArrayList(); > /* ... */ > if (user.getPassword() != null) > { > if (orgService.getConfiguration().isPasswordAsAttribute()) > { > attributes.add(new SimpleAttribute(USER_PASSWORD, user.getPassword())); > } > else > { > try > { > am.updatePassword(session.getPersistenceManager().findUser(user.getUserName()), user.getPassword()); > } > catch (IdentityException e) > { > log.info("Cannot update password: " + user.getUserName() + "; ", e); > } > } > } > Attribute[] attrs = new Attribute[attributes.size()]; > attrs = (Attribute[])attributes.toArray(attrs); > try > { > am.updateAttributes(user.getUserName(), attrs); > } > catch (IdentityException e) > { > log.info("Cannot update attributes for user: " + user.getUserName() + "; ", e); > } > } > {code} > > The method {{saveUser(User, boolean) _throws Exception_}} > calls > {{persistUserInfo(User user, IdentitySession session) _throws Exception_}}. > > Whereas, deeper in the code, you can easily notice that exceptions are caught in this level and traced by a {{log.info}}: > * first time in the password level > * second time when updating all of the attributes. > (!) Users want to be notified when an error occurs during user registration. > As well as being aware of the type of the caught exception. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2581) RichFaces is not defined after adding a RF portlet to a page

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2581?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2581: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1080249|https://bugzilla.redhat.com/show_bug.cgi?id=1080249] from POST to MODIFIED > RichFaces is not defined after adding a RF portlet to a page > ------------------------------------------------------------ > > Key: GTNPORTAL-2581 > URL: https://issues.jboss.org/browse/GTNPORTAL-2581 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: GateIn 3.4.0.Final > Reporter: Peter Palaga > Attachments: jsf2-rf4-hello-world-portlet.war > > > (1) Start a fresh GateIn 3.4.0.Final: > cd tmp > wget http://downloads.jboss.org/gatein/Releases/Portal/3.4.0.Final/GateIn-3.4.... > unzip GateIn-3.4.0.Final-jbossas7.zip > cd GateIn-3.4.0.Final-jbossas7/bin > ./standalone.sh > (2) Install gatein-bom-3.4 > git clone https://github.com/ppalaga/gatein-bom.github > cd gatein-bom > mvn install -Dgpg.skip=true > (3) Pack and deploy jsf2-rf4-hello-world-portlet: > cd tmp > git clone https://github.com/ppalaga/gatein-portal-quickstart.git > cd gatein-portal-quickstart/jsf2-rf4-hello-world-portlet > mvn package jboss-as:deploy > (4) In web browser: > * login as root http://127.0.0.1:8080/portal/login?username=root&password=gtn&initialURI=... > (5) In web browser: > * Group > Administration > Application Registry > Import Applications > * Site > Classic > Home > * Site Editor > Edit Page > * Drag jsf2-rf4-hello-world-portlet and drop it e.g. under the Home Page portlet > * make the console with server log visible to you > * Open developer tools (F12 in Chrome) and switch to Resources. Have a look at loaded scripts. Note that there are no PBR-related scripts there. > (6) Hit Finish (Diskette Icon) in Page Editor dialog > (7) UNEXPECTED: After hitting Finish, there comes a modal message in the browser window saying "RichFaces is not defined". > * Note that while this message is being displayed, there is no change in the scripts compared to before (5). > * Note that nothing happened in the server log. > > (8) Hit OK in the "RichFaces is not defined" alert. > * Note that one or more PBR-related scripts were loaded. Some of them have error markers in them > * Sometimes one or more org.exoplatform.portal.config.NoSuchDataExceptions appear in the server log > > The problem seems to be related to the fact that the inline JavaScript needed to render the rich:select component is evaluated before the needed js resources were loaded. After reloading the whole page or accessing the page from another session jsf2-rf4-hello-world-portlet works as expected. > For further observations, define one more step: > (9) > * Site > Classic > Home > * Site Editor > Edit Page > * remove jsf2-rf4-hello-world-portlet from the page > * Hit Finish (Diskette Icon) in Page Editor dialog > When in the state after (8), one performs (9) and then again (5) and (6), "RichFaces is not defined" does not appear. > "RichFaces is not defined" appears only when one signs out from the portal and signs in again between (9) and (5) of the previous scenario. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3484) Commit changes for a page before send response

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3484?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3484: ------------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 3.8.2.Final 3.9.0.Final Resolution: Done > Commit changes for a page before send response > ---------------------------------------------- > > Key: GTNPORTAL-3484 > URL: https://issues.jboss.org/browse/GTNPORTAL-3484 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.2.Final, 3.9.0.Final > > > In current design a call to RequestLifeCycle.end() is performed at the end of the request meanwhile a markup can be send it before with portlets ID not yet commited. > This can cause some StaleModelException cases under heavy load or database congestion. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3484) Commit changes for a page before send response

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3484?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3484: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1080249|https://bugzilla.redhat.com/show_bug.cgi?id=1080249] from POST to MODIFIED > Commit changes for a page before send response > ---------------------------------------------- > > Key: GTNPORTAL-3484 > URL: https://issues.jboss.org/browse/GTNPORTAL-3484 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.2.Final, 3.9.0.Final > > > In current design a call to RequestLifeCycle.end() is performed at the end of the request meanwhile a markup can be send it before with portlets ID not yet commited. > This can cause some StaleModelException cases under heavy load or database congestion. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3475) NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3475?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3475: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1096190|https://bugzilla.redhat.com/show_bug.cgi?id=1096190] from POST to MODIFIED > NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip() > --------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3475 > URL: https://issues.jboss.org/browse/GTNPORTAL-3475 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.2.Final, 3.9.0.Final > > Attachments: GTNPORTAL-3475.log > > > Looks like a concurrent modification of the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because: > i. It is not always reproducible, the NPE occurs roughly once per 10 attempts. > ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause. > Steps to reproduce: > (1) Start clean Portal instance for the first time > (2) Go to Application Registry > (3) Import Applications > Not OK: There is an NPE logged (the whole log is attached): > {code:none} > Caused by: java.lang.NullPointerException > at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55] > at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20) at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT] > at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT] > {code} > Expected: No NPE -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3475) NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip()

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3475?page=com.atlassian.jira.pl... ] Peter Palaga updated GTNPORTAL-3475: ------------------------------------ Status: Resolved (was: Pull Request Sent) Assignee: Peter Palaga Fix Version/s: 3.8.2.Final 3.9.0.Final Resolution: Done > NPE in LinkedList$ListItr.next when iterating over UIGroupMembershipSelect.getListMemberhip() > --------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3475 > URL: https://issues.jboss.org/browse/GTNPORTAL-3475 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.2.Final, 3.9.0.Final > > Attachments: GTNPORTAL-3475.log > > > Looks like a concurrent modification of the {{LinkedList}} refered to by {{UIGroupMembershipSelect.listMemberhip}}, because: > i. It is not always reproducible, the NPE occurs roughly once per 10 attempts. > ii. It happens on line {{next = next.next}} of the JRE's {{LinkedList.ListItr}} where it is hard to thing of anything else than concurrent modification as a cause. > Steps to reproduce: > (1) Start clean Portal instance for the first time > (2) Go to Application Registry > (3) Import Applications > Not OK: There is an NPE logged (the whole log is attached): > {code:none} > Caused by: java.lang.NullPointerException > at java.util.LinkedList$ListItr.next(LinkedList.java:891) [rt.jar:1.7.0_55] > at UIGroupMembershipSelector.run(UIGroupMembershipSelector.gtmpl:20) at org.exoplatform.groovyscript.GroovyScript.render(GroovyScript.java:99) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT] > at org.exoplatform.groovyscript.GroovyTemplate.render(GroovyTemplate.java:115) [exo.portal.component.scripting-3.8.0.Beta02-SNAPSHOT.jar:3.8.0.Beta02-SNAPSHOT] > {code} > Expected: No NPE -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3385) Support full-ha and ha profiles in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3385?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3385: ---------------------------------------------------- mgottval <mgottval(a)redhat.com> changed the Status of [bug 1056533|https://bugzilla.redhat.com/show_bug.cgi?id=1056533] from ON_QA to VERIFIED > Support full-ha and ha profiles in domain mode > ---------------------------------------------- > > Key: GTNPORTAL-3385 > URL: https://issues.jboss.org/browse/GTNPORTAL-3385 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.7.0.Final, 3.6.5.Final > > > Add support for full-ha and ha profiles in domain mode for GateIn distribution based on JBoss. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues May 2014