December 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3345) Improve user search filter

by Tuyen Nguyen The (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3345?page=com.atlassian.jira.pl... ] Work on GTNPORTAL-3345 started by Tuyen Nguyen The. > Improve user search filter > -------------------------- > > Key: GTNPORTAL-3345 > URL: https://issues.jboss.org/browse/GTNPORTAL-3345 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Trong Tran > Assignee: Tuyen Nguyen The > Fix For: 3.7.0.Final > > Attachments: Screen Shot 2013-12-10 at 11.20.36 AM.png > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > Improve user search in Organization Portlet to allow filter by "Status" of {All, Enabled, Disabled} > See attached image -- 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

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2930) Portal keep session alive property values are confusing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2930?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2930: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 952274|https://bugzilla.redhat.com/show_bug.cgi?id=952274] from ASSIGNED to ON_QA > Portal keep session alive property values are confusing > ------------------------------------------------------- > > Key: GTNPORTAL-2930 > URL: https://issues.jboss.org/browse/GTNPORTAL-2930 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.0.Beta01 > Reporter: Dominik Pospisil > Assignee: Tuyen Nguyen The > Original Estimate: 4 hours > Time Spent: 4 hours > Remaining Estimate: 0 minutes > > According to documentation, portal "keep seesion alive" property values meaning are as follows: > never - The session will never timeout, even if an application requests it. > On-demand - The session will timeout if an application requests it > Always - The session will time out after a set period > This is quite confusing. E.g. keep session alive never actually means to keep session alive forever. > Keep session alive always means to let the session timeout automatically. > If the documentation is correct, the name of the property or property values should be changed. -- 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

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3304) White background in Edit Mode dialogs

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3304?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3304: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 794328|https://bugzilla.redhat.com/show_bug.cgi?id=794328] from MODIFIED to ON_QA > White background in Edit Mode dialogs > ------------------------------------- > > Key: GTNPORTAL-3304 > URL: https://issues.jboss.org/browse/GTNPORTAL-3304 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.6.4.Final, 3.7.0.Final > > -- 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

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3341) Cannot delete users with OracleDB because of "ORA-02292: integrity constraint (XXXXX) violated"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3341?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3341: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1039924|https://bugzilla.redhat.com/show_bug.cgi?id=1039924] from MODIFIED to ON_QA > Cannot delete users with OracleDB because of "ORA-02292: integrity constraint (XXXXX) violated" > ----------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-3341 > URL: https://issues.jboss.org/browse/GTNPORTAL-3341 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Identity integration > Affects Versions: 3.6.3.Final > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.4.Final, 3.7.0.Final > > > Description of problem: > Cannot delete users with OracleDB (reproducible at least on version 11gR2) because of "ORA-02292: integrity constraint (XXXXX) violated - child record found"[1]. The child record is in the JBID_IO_ATTR table[2]. > [1] > 2013-12-05 15:40:25,846 DEBUG [org.hibernate.util.JDBCExceptionReporter] (http-127.0.0.1-8080-1) Could not execute JDBC batch update [delete from jbid_io where ID=?] > java.sql.BatchUpdateException: ORA-02292: integrity constraint (ORAUSER.FK4DC61D7E992317F0) violated - child record found > at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10345) > at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:230) > at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.executeBatch(CachedPreparedStatement.java:476) > at org.jboss.resource.adapter.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:774) > at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:70) > at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:268) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:265) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:171) > at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:321) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:50) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1030) > at sun.reflect.GeneratedMethodAccessor346.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:343) > at com.sun.proxy.$Proxy266.flush(Unknown Source) > at org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreImpl.removeIdentityObject(HibernateIdentityStoreImpl.java:622) > at org.picketlink.idm.impl.repository.WrapperIdentityStoreRepository.removeIdentityObject(WrapperIdentityStoreRepository.java:158) > at org.picketlink.idm.impl.api.session.managers.PersistenceManagerImpl.removeUser(PersistenceManagerImpl.java:231) > at org.exoplatform.services.organization.idm.UserDAOImpl.removeUser(UserDAOImpl.java:268) > [2] > JBID_IO_ATTR: > ATTRIBUTE_ID 423 > IDENTITY_OBJECT_ID 413 > NAME user.language > ATTRIBUTE_TYPE text > BIN_VALUE_ID NULL > How reproducible: 100 % > Steps to Reproduce: > 1. Change gatein-idm and gatein-jcr to use OracleDB. > 2. Start EPP > 3. Login as root > 4. Create a user > 5. Delete the user > Actual results: > Cannot delete the user. > Expected results: > The user is deleted. > Additional info: > Some user attributes are deleted, so this process is not transactional. -- 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

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2072) NoSuchDataException is thrown after importing pages through export/import tool.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2072?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2072: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1038029|https://bugzilla.redhat.com/show_bug.cgi?id=1038029] from MODIFIED to ON_QA > NoSuchDataException is thrown after importing pages through export/import tool. > ------------------------------------------------------------------------------- > > Key: GTNPORTAL-2072 > URL: https://issues.jboss.org/browse/GTNPORTAL-2072 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.2.0-Beta01 > Reporter: Nick Scavelli > Assignee: Vu Viet Phuong > Labels: import > Fix For: 3.6.4.Final, 3.7.0.Final > > Original Estimate: 1 day > Time Spent: 2 days, 6 hours > Remaining Estimate: 0 minutes > > Below exception is thrown after importing pages through management tools (see steps to reproduce section). I think this is a stale storageId coming from the UI when the data has changed outside the UI. Typically logging out solves the issue, but this isn't optimal. Changes to data should not be only achievable through the UI. The changes are being sent through DataStorage, so there should be someway to sync this data up. > Stacktrace: > {noformat} > Caused by: org.exoplatform.portal.config.NoSuchDataException: Can not find 1c42bec77f0000011076449207f5d085 > at org.exoplatform.portal.pom.config.POMSession.findCustomizationById(POMSession.java:214) > at org.exoplatform.portal.pom.config.tasks.PreferencesTask$Load.run(PreferencesTask.java:91) > at org.exoplatform.portal.pom.config.POMSession.execute(POMSession.java:405) > at org.exoplatform.portal.pom.config.ExecutorDispatcher.execute(ExecutorDispatcher.java:60) > at org.exoplatform.portal.pom.config.TaskExecutionDecorator.execute(TaskExecutionDecorator.java:38) > at org.exoplatform.portal.pom.config.cache.DataCache.read(DataCache.java:169) > at org.exoplatform.portal.pom.config.cache.DataCache.execute(DataCache.java:61) > at org.exoplatform.portal.pom.config.TaskExecutionDecorator.execute(TaskExecutionDecorator.java:38) > at org.exoplatform.portal.pom.config.cache.PortalNamesCache.execute(PortalNamesCache.java:77) > at org.exoplatform.portal.pom.config.POMSessionManager.execute(POMSessionManager.java:251) > at org.exoplatform.portal.pom.config.POMDataStorage.load(POMDataStorage.java:176) > at org.exoplatform.portal.config.DataStorageImpl.load(DataStorageImpl.java:111) > at org.exoplatform.portal.webui.application.ModelAdapter$1.getPortletContext(ModelAdapter.java:89) > at org.exoplatform.portal.webui.application.UIPortlet.getPortletContext(UIPortlet.java:993) > at org.exoplatform.portal.webui.application.UIPortlet.create(UIPortlet.java:829) > at org.exoplatform.portal.webui.application.UIPortletLifecycle.processRender(UIPortletLifecycle.java:212) > {noformat} -- 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

1
0
0 / 0

[JBoss JIRA] (GTNMGMT-25) NoSuchDataException when trying to edit navigation after import of classic portal

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNMGMT-25?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on GTNMGMT-25: ------------------------------------------------ Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1038029|https://bugzilla.redhat.com/show_bug.cgi?id=1038029] from MODIFIED to ON_QA > NoSuchDataException when trying to edit navigation after import of classic portal > --------------------------------------------------------------------------------- > > Key: GTNMGMT-25 > URL: https://issues.jboss.org/browse/GTNMGMT-25 > Project: GateIn Management > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 1.0.0-Beta04 > Reporter: Tomas Kyjovsky > Assignee: Nick Scavelli > Attachments: error-rendering-portlets-1.png, error-rendering-portlets-2.png, no-such-data-exception.txt > > > NoSuchDataException appears when rendering Navigation, Breadcrumbs, Footer portlets. After refresh the portlets render fine. -- 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

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3331) Redirect Admin UI: Device property persist when operator is changed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3331?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3331: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1006325|https://bugzilla.redhat.com/show_bug.cgi?id=1006325] from MODIFIED to ON_QA > Redirect Admin UI: Device property persist when operator is changed > ------------------------------------------------------------------- > > Key: GTNPORTAL-3331 > URL: https://issues.jboss.org/browse/GTNPORTAL-3331 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Interface > Affects Versions: 3.6.3.Final > Reporter: Alexandre Mendonça > Assignee: Alexandre Mendonça > Fix For: 3.6.4.Final, 3.7.0.Final > > > When a device property operator is changed, the value for such operator is being kept, resulting in properties with multiple operators which is not intended or desired. -- 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

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3257) REST MOP Import doesn't detect errors on commit

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3257?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3257: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1004213|https://bugzilla.redhat.com/show_bug.cgi?id=1004213] from MODIFIED to ON_QA > REST MOP Import doesn't detect errors on commit > ----------------------------------------------- > > Key: GTNPORTAL-3257 > URL: https://issues.jboss.org/browse/GTNPORTAL-3257 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST API > Affects Versions: 3.6.0.Final > Reporter: Toshiya Kobayashi > Assignee: Nick Scavelli > Fix For: 3.6.4.Final, 3.7.0.Final > > > When you call REST MOP Import: > {noformat} > curl -v -u root:gtn -X PUT -H 'Content-type: application/zip' --upload-file portal_classic_2013-06-10_15-16-53.zip http://localhost:8080/rest/private/managed-components/mop?importMode=over... > {noformat} > It returns 200 OK even if it fails on JCR commit (for example, cache replication timeout). > Because JCR commit happens in RequestLifeCycle.end() after requestHandler.handleRequest() which flushes http response. > https://github.com/exoplatform/ws/blob/master/exo.ws.rest.core/src/main/j... > {code:java} > protected void onService(ExoContainer container, HttpServletRequest httpRequest, HttpServletResponse httpResponse) > throws IOException, ServletException > { > ... > try > { > EnvironmentContext.setCurrent(env); > ServletContainerRequest request = new ServletContainerRequest(httpRequest); > ContainerResponse response = new ContainerResponse(new ServletContainerResponseWriter(httpResponse)); > requestHandler.handleRequest(request, response); > } > ... > finally > { > EnvironmentContext.setCurrent(null); > RequestLifeCycle.end(); > } > } > {code} -- 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

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3342) SecureRandomGenerator instance per container requires too much entropy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3342?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3342: ---------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1036624|https://bugzilla.redhat.com/show_bug.cgi?id=1036624] from ASSIGNED to ON_QA > SecureRandomGenerator instance per container requires too much entropy > ---------------------------------------------------------------------- > > Key: GTNPORTAL-3342 > URL: https://issues.jboss.org/browse/GTNPORTAL-3342 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.6.3.Final > Reporter: Marek Posolda > Assignee: Marek Posolda > Fix For: 3.6.4.Final, 3.7.0.Final > > > Currently every portal container instance uses it's own instance of SecureRandomGenerator for generating password salts. This requires too much entropy if many containers are used (50). > In QA lab environment, registering new generator freezes portal boot for roughly 20-30s (1 min 40s max). -- 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

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3313) Workaround for GTNPORTAL-2700 not necessary after GTNPORTAL-3291

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3313?page=com.atlassian.jira.pl... ] Peter Palaga edited comment on GTNPORTAL-3313 at 12/11/13 8:38 AM: ------------------------------------------------------------------- This patch needed to be applied to 3.6.x too to avoid recurrence of GTNPORTAL-2700 like symptoms. To put it in other words, the fix for GTNPORTAL-2700 stops working after GTNPORTAL-3291 (and causes symptoms similar to those ones reported in GTNPORTAL-2700). was (Author: ppalaga): This patch needed to be applied to 3.6.x too to avoid recurrence of GTNPORTAL-2700 like symptoms. > Workaround for GTNPORTAL-2700 not necessary after GTNPORTAL-3291 > ---------------------------------------------------------------- > > Key: GTNPORTAL-3313 > URL: https://issues.jboss.org/browse/GTNPORTAL-3313 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.6.4.Final, 3.7.0.Final > > > Revert the workaround for GTNPORTAL-2700 as it should not be necessary after GTNPORTAL-3291. -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues December 2013