[gatein-dev] [GateIn] Roll back revision 744 on identity & bug in jcr-core.

[Dimitri BAELI]

Hello,
   Julien asked me to rollback the revision 744

> Revision: 744
>
- upgrade to PicketLink IDM (former JBoss Identity) 1.0.0.CR1
> - remove separate IDM hibernate config
>

1/ Many tests were failing since this test : see
http://builder.exoplatform.org/hudson/job/gatein-portal-trunk-ci/399/
2/ Julien does not accept that commits are done with failing tests
3/ A bug in core https://jira.jboss.org/jira/browse/EXOJCR-259 is hidding
some informations to understand the failures
4/ The bug to solve should be this stack (according to Julien after is
hacked the core component to reveal the real issue -- see
EXOJCR-259<https://jira.jboss.org/jira/browse/EXOJCR-259>for a patch
in exo-core, or contact Julien)
org.hibernate.HibernateException: No CurrentSessionContext configured!
 at
org.hibernate.impl.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:572)
 at
org.picketlink.idm.impl.store.hibernate.HibernateIdentityStoreSessionImpl.startTransaction(HibernateIdentityStoreSessionImpl.java:77)
 at
org.picketlink.idm.impl.repository.RepositoryIdentityStoreSessionImpl.startTransaction(RepositoryIdentityStoreSessionImpl.java:117)
 at
org.picketlink.idm.impl.api.session.SimpleTransactionImpl.start(SimpleTransactionImpl.java:43)
 at
org.picketlink.idm.impl.api.session.IdentitySessionImpl.beginTransaction(IdentitySessionImpl.java:203)
 at
org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.startRequest(PicketLinkIDMOrganizationServiceImpl.java:136)
 at
org.exoplatform.services.organization.auth.OrganizationAuthenticatorImpl.begin(OrganizationAuthenticatorImpl.java:143)
 at
org.exoplatform.services.organization.auth.OrganizationAuthenticatorImpl.createIdentity(OrganizationAuthenticatorImpl.java:93)
 at
org.exoplatform.portal.config.TestUserPortalConfigService$UnitTest.execute(TestUserPortalConfigService.java:858)
 at
org.exoplatform.portal.config.TestUserPortalConfigService.testCreateUserPortalConfig(TestUserPortalConfigService.java:279)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at junit.framework.TestCase.runTest(TestCase.java:164)
 at org.exoplatform.test.BasicTestCase.runTest(BasicTestCase.java:68)
 at junit.framework.TestCase.runBare(TestCase.java:130)
 at junit.framework.TestResult$1.protect(TestResult.java:106)
 at junit.framework.TestResult.runProtected(TestResult.java:124)
 at junit.framework.TestResult.run(TestResult.java:109)
 at junit.framework.TestCase.run(TestCase.java:120)
 at junit.framework.TestSuite.runTest(TestSuite.java:230)
 at junit.framework.TestSuite.run(TestSuite.java:225)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
 at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
 at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
 at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
 at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)

Please assume that the GateIn project should have no failing tests when you
are commiting (work has been done to hide the known failing ones).
This is really important for the GateIn Beta03 release at the end of the
week.
We are requesting a new release of the JCR for that fix (if possible).

Thank you,
Dimitri BAELI - eXo Platform SAS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/gatein-dev/attachments/20091124/33dde177/attachment.html