[JBoss JIRA] (GTNPORTAL-2811) The portlet modes are sometimes displayed selected in latest versions of FF and Chrome
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2811?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2811:
----------------------------------
Original Estimate: 5 hours
Remaining Estimate: 5 hours
> The portlet modes are sometimes displayed selected in latest versions of FF and Chrome
> --------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2811
> URL: https://issues.jboss.org/browse/GTNPORTAL-2811
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Interface
> Affects Versions: 3.2.0-GA, 3.5.0.Final
> Environment: GateIn-3.5.0.Final-tomcat7/GateIn-3.2.0.Final-tomcat6
> Java 1.6.0_37
> Firefox 16.0.2/17.0.1/18.0.1 and Chrome 24.0.1312.56
> Reporter: Nicolas Filotto
> Priority: Minor
> Labels: portal-s70
> Attachments: Portlet-Modes.jpg
>
> Original Estimate: 5 hours
> Remaining Estimate: 5 hours
>
> It seems that there is a display issue on latest versions of FF and Chrome when we show the portlet modes, indeed sometimes the labels are selected by default as you can see in the screenshot and sometimes it appears normally. After a deeper investigation it seems to be due to the fact that FF believes that we want to select the content by left clicking on the arrow, one way to fix it is to use the trick described here http://stackoverflow.com/questions/69430/is-there-a-way-to-make-text-unse.... By simply adding the css attributes of the class {{unselectable}} in the div of class {{ControlIcon}}, I could fix the issue on chrome and FF (did not test on other browsers). In other words, I modified the file webapps/portal/groovy/portal/webui/application/UIPortlet.gtmpl to replace
> {code}
> <div class="ControlIcon ArrowDownIcon" title="<%=_ctx.appRes("UIPortlet.tooltip.PortletMode");%>" style="position: relative;">
> {code}
> with
> {code}
> <div class="ControlIcon ArrowDownIcon" title="<%=_ctx.appRes("UIPortlet.tooltip.PortletMode");%>" style="position: relative;-moz-user-select: -moz-none;-khtml-user-select: none;-webkit-user-select: none;-ms-user-select: none;user-select: none;" unselectable="on">
> {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, 11 months
[JBoss JIRA] (GTNPORTAL-2807) The page is not saved when edit node's page in group navigation
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2807?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2807:
----------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> The page is not saved when edit node's page in group navigation
> ---------------------------------------------------------------
>
> Key: GTNPORTAL-2807
> URL: https://issues.jboss.org/browse/GTNPORTAL-2807
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.0.Final
> Environment: jboss-jpp-6.0.0.ER05
> GateIn 3.5
> FF 16
> Reporter: Thu Nguyen
> Assignee: Vu Viet Phuong
> Priority: Minor
> Labels: portal-s70
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Here are steps to reproduce
> 1. Signin as root
> 2. Go to Application Registry
> 3. Create a page by winzard, called "Test"
> 4. Drag and drop "Application registry" portlet to this page
> 5. Save and close
> 6. Go to Group site, click on "edit navigation" of Administrators group
> 7. Click on Edit Node'page of "Test" node
> 8. Drag and drop "Dashboard" portlet to this page
> 9. Save and close
> 10.Click on Save on "Navigation management" popup
> 11. Open the page "Test"
> 12. Actual result: Don't show DashBoard portlet => NOK
> Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group.
> 13. click on "Edit page"
> 14. Actual result: Don't show Dashboard portlet => NOK
> Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group.
--
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, 11 months
[JBoss JIRA] (GTNPORTAL-2807) The page is not saved when edit node's page in group navigation
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2807?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2807:
----------------------------------
Assignee: Trong Tran (was: Vu Viet Phuong)
> The page is not saved when edit node's page in group navigation
> ---------------------------------------------------------------
>
> Key: GTNPORTAL-2807
> URL: https://issues.jboss.org/browse/GTNPORTAL-2807
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.5.0.Final
> Environment: jboss-jpp-6.0.0.ER05
> GateIn 3.5
> FF 16
> Reporter: Thu Nguyen
> Assignee: Trong Tran
> Priority: Minor
> Labels: portal-s70
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Here are steps to reproduce
> 1. Signin as root
> 2. Go to Application Registry
> 3. Create a page by winzard, called "Test"
> 4. Drag and drop "Application registry" portlet to this page
> 5. Save and close
> 6. Go to Group site, click on "edit navigation" of Administrators group
> 7. Click on Edit Node'page of "Test" node
> 8. Drag and drop "Dashboard" portlet to this page
> 9. Save and close
> 10.Click on Save on "Navigation management" popup
> 11. Open the page "Test"
> 12. Actual result: Don't show DashBoard portlet => NOK
> Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group.
> 13. click on "Edit page"
> 14. Actual result: Don't show Dashboard portlet => NOK
> Expected Result: Show Dashboard portlet => It must be saved when edit Node's page on Navigation group.
--
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, 11 months
[JBoss JIRA] (GTNPORTAL-2799) Changing Portlet Icon doesn't work
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2799?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2799:
----------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
Assignee: Vu Viet Phuong
> Changing Portlet Icon doesn't work
> ----------------------------------
>
> Key: GTNPORTAL-2799
> URL: https://issues.jboss.org/browse/GTNPORTAL-2799
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: WebUI
> Affects Versions: 3.5.0.Final
> Reporter: Trong Tran
> Assignee: Vu Viet Phuong
> Priority: Trivial
> Labels: portal-s70
> Attachments: Portal Navigation_1358312135866, Portal Navigation_1358312135866.png, Screen Shot 2013-01-16 at 11.56.05 AM.png
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Go to the Portlet Edit form to change the Icon, then save ==> it doesn't work (see attached images)
--
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, 11 months
[JBoss JIRA] (GTNPORTAL-2722) Improve design of DownloadResource
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2722?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2722:
----------------------------------
Original Estimate: 3 days, 4 hours (was: 3 days)
Remaining Estimate: 3 days, 4 hours (was: 3 days)
Labels: portal-s70 (was: portal-s701d5)
> Improve design of DownloadResource
> ----------------------------------
>
> Key: GTNPORTAL-2722
> URL: https://issues.jboss.org/browse/GTNPORTAL-2722
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Minh Hoang TO
> Assignee: Minh Hoang TO
> Labels: portal-s70
> Original Estimate: 3 days, 4 hours
> Remaining Estimate: 3 days, 4 hours
>
> For the moment, DownloadResource is designed as a wrapper of InputStream.
> {code:java}
> public abstract class DownloadResource
> {
> public abstract InputStream getInputStream() throws IOException;
> }
> {code}
> This design is bad as the code of DownloadService has to care about IO handling on DownloadResource. That work should be done on DownloadResource creator 's side.
> It is better with
> {code:java}
> public abstract class DownloadResource
> {
> public abstract void write(OutputStream out) throws IOException;
> }
> {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, 11 months
[JBoss JIRA] (GTNPORTAL-2722) Improve design of DownloadResource
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2722?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2722:
----------------------------------
Original Estimate: 3 days
Remaining Estimate: 3 days
Labels: portal-s701d5 (was: portal-s70)
Assignee: Minh Hoang TO
> Improve design of DownloadResource
> ----------------------------------
>
> Key: GTNPORTAL-2722
> URL: https://issues.jboss.org/browse/GTNPORTAL-2722
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Minh Hoang TO
> Assignee: Minh Hoang TO
> Labels: portal-s701d5
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> For the moment, DownloadResource is designed as a wrapper of InputStream.
> {code:java}
> public abstract class DownloadResource
> {
> public abstract InputStream getInputStream() throws IOException;
> }
> {code}
> This design is bad as the code of DownloadService has to care about IO handling on DownloadResource. That work should be done on DownloadResource creator 's side.
> It is better with
> {code:java}
> public abstract class DownloadResource
> {
> public abstract void write(OutputStream out) throws IOException;
> }
> {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, 11 months
[JBoss JIRA] (GTNPORTAL-2711) Database/jcr is not initialized before first call
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2711?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2711:
----------------------------------
Labels: done portal-s70 (was: portal-s70)
> Database/jcr is not initialized before first call
> -------------------------------------------------
>
> Key: GTNPORTAL-2711
> URL: https://issues.jboss.org/browse/GTNPORTAL-2711
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Stian Thorgersen
> Assignee: Minh Hoang TO
> Labels: done, portal-s70
> Fix For: 3.6.0.Beta02
>
>
> I believe some data structures are not initialized in chromattic/jcr until first used. If multiple threads do this at the same time it causes an ItemExistsException to be thrown.
> To reproduce this issue I've slightly modified TestGadgetTokenInfoService in gadgets/core available here https://github.com/stianst/gatein-portal/tree/GTNPORTAL-2711. It may not fail the first time, so run it a few times if it doesn't.
> Stack trace:
> {code}
> org.chromattic.api.UndeclaredRepositoryException: javax.jcr.ItemExistsException: [portal-test] ADD NODE. Item already exists. Condition: parent ID, name, index. []:1[]gadgettokens:1, ID: db7e626b7f0001013865a7c41b
> aa4a6e, ParentID: 00exo0jcr0root0uuid0000000000000. Cause >>>> integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violation: unique constraint or
> index violation: JCR_IDX_IPORTALTEST_PARENT: [portal-test] ADD NODE. Item already exists. Condition: parent ID, name, index. []:1[]gadgettokens:1, ID: db7e626b7f0001013865a7c41baa4a6e, ParentID: 00exo0jcr0root0uu
> id0000000000000. Cause >>>> integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTE
> ST_PARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT
> at org.chromattic.core.DomainSession.save(DomainSession.java:181)
> at org.chromattic.core.api.ChromatticSessionImpl.save(ChromatticSessionImpl.java:246)
> at org.exoplatform.commons.chromattic.AbstractContext.close(AbstractContext.java:129)
> at org.exoplatform.commons.chromattic.LocalContext.close(LocalContext.java:56)
> at org.exoplatform.commons.chromattic.ChromatticLifeCycle.closeContext(ChromatticLifeCycle.java:306)
> at org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:49)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService.createToken(GadgetTokenInfoService.java:50)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.createTokens(TestGadgetTokenInfoService.java:69)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testGetToken(TestGadgetTokenInfoService.java:88)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:91)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Caused by: javax.jcr.ItemExistsException: [portal-test] ADD NODE. Item already exists. Condition: parent ID, name, index. []:1[]gadgettokens:1, ID: db7e626b7f0001013865a7c41baa4a6e, ParentID: 00exo0jcr0root0uuid00
> 00000000000. Cause >>>> integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_P
> ARENT: [portal-test] ADD NODE. Item already exists. Condition: parent ID, name, index. []:1[]gadgettokens:1, ID: db7e626b7f0001013865a7c41baa4a6e, ParentID: 00exo0jcr0root0uuid0000000000000. Cause >>>> integrity c
> onstraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violati
> on: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT
> at org.exoplatform.services.jcr.impl.core.SessionDataManager.commit(SessionDataManager.java:1565)
> at org.exoplatform.services.jcr.impl.core.ItemImpl.save(ItemImpl.java:706)
> at org.exoplatform.services.jcr.impl.core.SessionImpl.save(SessionImpl.java:1080)
> at org.exoplatform.commons.chromattic.PortalSessionLifeCycle.save(PortalSessionLifeCycle.java:56)
> at org.chromattic.core.jcr.SessionWrapperImpl.save(SessionWrapperImpl.java:274)
> at org.chromattic.core.DomainSessionImpl._save(DomainSessionImpl.java:640)
> at org.chromattic.core.DomainSession.save(DomainSession.java:178)
> ... 34 more
> Caused by: javax.jcr.ItemExistsException: [portal-test] ADD NODE. Item already exists. Condition: parent ID, name, index. []:1[]gadgettokens:1, ID: db7e626b7f0001013865a7c41baa4a6e, ParentID: 00exo0jcr0root0uuid00
> 00000000000. Cause >>>> integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_P
> ARENT: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT
> at org.exoplatform.services.jcr.impl.storage.jdbc.SQLExceptionHandler.handleAddException(SQLExceptionHandler.java:141)
> at org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection.add(JDBCStorageConnection.java:746)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.WorkspacePersistentDataManager.doAdd(WorkspacePersistentDataManager.java:1009)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.WorkspacePersistentDataManager$ChangesLogPersister.save(WorkspacePersistentDataManager.java:662)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.WorkspacePersistentDataManager.save(WorkspacePersistentDataManager.java:333)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.doSave(CacheableWorkspaceDataManager.java:1102)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.access$800(CacheableWorkspaceDataManager.java:93)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager$9.run(CacheableWorkspaceDataManager.java:1045)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager$9.run(CacheableWorkspaceDataManager.java:1042)
> at org.exoplatform.commons.utils.SecurityHelper.doPrivilegedExceptionAction(SecurityHelper.java:310)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.save(CacheableWorkspaceDataManager.java:1041)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.save(CacheableWorkspaceDataManager.java:1007)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.ShareableSupportedWorkspaceDataManager.save(ShareableSupportedWorkspaceDataManager.java:176)
> at org.exoplatform.services.jcr.impl.dataflow.persistent.VersionableWorkspaceDataManager.save(VersionableWorkspaceDataManager.java:334)
> at org.exoplatform.services.jcr.impl.dataflow.session.TransactionableDataManager.save(TransactionableDataManager.java:471)
> at org.exoplatform.services.jcr.impl.core.SessionDataManager.commit(SessionDataManager.java:1549)
> ... 40 more
> Caused by: java.sql.SQLException: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT
> at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
> at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(Unknown Source)
> at org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(Unknown Source)
> at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
> at org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.db.MultiDbJDBCConnection.addNodeRecord(MultiDbJDBCConnection.java:253)
> at org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection.add(JDBCStorageConnection.java:732)
> ... 54 more
> Caused by: org.hsqldb.HsqlException: integrity constraint violation: unique constraint or index violation: JCR_IDX_IPORTALTEST_PARENT
> at org.hsqldb.error.Error.error(Unknown Source)
> at org.hsqldb.index.IndexAVLMemory.insert(Unknown Source)
> at org.hsqldb.persist.RowStoreAVL.indexRow(Unknown Source)
> at org.hsqldb.Table.insertSingleRow(Unknown Source)
> at org.hsqldb.StatementDML.insertSingleRow(Unknown Source)
> at org.hsqldb.StatementInsert.getResult(Unknown Source)
> at org.hsqldb.StatementDMQL.execute(Unknown Source)
> at org.hsqldb.Session.executeCompiledStatement(Unknown Source)
> at org.hsqldb.Session.execute(Unknown Source)
> ... 59 more
> {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, 11 months
[JBoss JIRA] (GTNPORTAL-2710) Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2710?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2710:
----------------------------------
Original Estimate: 4 hours
Remaining Estimate: 4 hours
> Context not removed from ChromatticLifeCycle#currenctContext if an exception is thrown in AbstractContext#close
> ---------------------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2710
> URL: https://issues.jboss.org/browse/GTNPORTAL-2710
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Stian Thorgersen
> Assignee: Minh Hoang TO
> Labels: portal-s70
> Fix For: 3.6.0.Beta02
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> If ChromatticLifeCycle#closeContext is called with save=true and a failure occurs the context is not removed from ChromatticLifeCycle#currenctContext. This is caused by AbstractContext#close only calling lifeCycle.currentContext.set(null); if no exception is thrown.
> This can be reproduced by running test specified in GTNPORTAL-2711. When this test is run the first test fails with the failure specified in that JIRA issue. However, the rest of the tests fails with the failure in this issue.
> Stack trace:
> {code}
> org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: This kind of operation is forbidden after a session.logout().
> at org.chromattic.core.DomainSession.findByPath(DomainSession.java:199)
> at org.chromattic.core.api.ChromatticSessionImpl.findByPath(ChromatticSessionImpl.java:228)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.getGadgetTokenContainer(GadgetTokenInfoService.java:149)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:55)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$1.execute(GadgetTokenInfoService.java:1)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService$TokenTask.execute(GadgetTokenInfoService.java:165)
> at org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:54)
> at org.exoplatform.portal.gadget.core.GadgetTokenInfoService.createToken(GadgetTokenInfoService.java:59)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.createTokens(TestGadgetTokenInfoService.java:69)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testSize(TestGadgetTokenInfoService.java:117)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> at junit.framework.TestCase.runBare(TestCase.java:134)
> at org.exoplatform.component.test.AbstractGateInTest.runBare(AbstractGateInTest.java:91)
> at junit.framework.TestResult$1.protect(TestResult.java:110)
> at junit.framework.TestResult.runProtected(TestResult.java:128)
> at junit.framework.TestResult.run(TestResult.java:113)
> at junit.framework.TestCase.run(TestCase.java:124)
> at junit.framework.TestSuite.runTest(TestSuite.java:243)
> at junit.framework.TestSuite.run(TestSuite.java:238)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: javax.jcr.RepositoryException: This kind of operation is forbidden after a session.logout().
> at org.exoplatform.services.jcr.impl.core.SessionImpl.checkLive(SessionImpl.java:917)
> at org.exoplatform.services.jcr.impl.core.SessionImpl.getRootNode(SessionImpl.java:760)
> at org.chromattic.core.DomainSessionImpl._getRoot(DomainSessionImpl.java:809)
> at org.chromattic.core.DomainSessionImpl._findByPath(DomainSessionImpl.java:115)
> at org.chromattic.core.DomainSession.findByPath(DomainSession.java:196)
> ... 29 more
> {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, 11 months