May 2009 - jboss-identity-issues - Jboss List Archives

[JBoss JIRA] Created: (JBID-63) Add JCR-based SPI Implementation.

by Jeff Yu (JIRA)

Add JCR-based SPI Implementation. --------------------------------- Key: JBID-63 URL: https://jira.jboss.org/jira/browse/JBID-63 Project: JBoss Identity Issue Type: Feature Request Components: IDM Affects Versions: 1.0.0.alpha1 Reporter: Jeff Yu Assignee: Anil Saldhana -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBID-100) Relationship type - Inherit

by Boleslaw Dawidowicz (JIRA)

Relationship type - Inherit ---------------------------- Key: JBID-100 URL: https://jira.jboss.org/jira/browse/JBID-100 Project: JBoss Identity Issue Type: Feature Request Components: IDM Reporter: Boleslaw Dawidowicz Assignee: Boleslaw Dawidowicz Fix For: 1.0.0.GA Add a notion of additional relationship type into the API. User/Group can "inherit" all attributes from another Group. There is no need to change SPI layer for this and it could be managed in a separate manager interface in the SPI (AdvencedRelationshipManager). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBID-101) Relationship type - Extension

by Boleslaw Dawidowicz (JIRA)

Relationship type - Extension ----------------------------- Key: JBID-101 URL: https://jira.jboss.org/jira/browse/JBID-101 Project: JBoss Identity Issue Type: Feature Request Components: IDM Reporter: Boleslaw Dawidowicz Assignee: Boleslaw Dawidowicz Fix For: 1.0.0.GA Add a notion of additional relationship type into the API. User/Group can "extends" another Group which mean that it will belong to every association defined for such group. There is no need to change SPI layer for this and it could be managed in a separate manager interface in the SPI (AdvencedRelationshipManager). It should be also possible to discover if user/group is associated with other group in a "real" way or "virtual" way (because it extends other associated group) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBID-46) Refactor the persistence.xml and database connection configuration

by Jeff Yu (JIRA)

Refactor the persistence.xml and database connection configuration ------------------------------------------------------------------ Key: JBID-46 URL: https://jira.jboss.org/jira/browse/JBID-46 Project: JBoss Identity Issue Type: Task Components: IDM Affects Versions: 1.0.0.alpha1 Reporter: Jeff Yu Assignee: Boleslaw Dawidowicz In the db scenario, I have found that we need to have the persistence.xml in the META-INF/ folder, and in the persistence.xml, we have listed a set of implementation classes. I am thinking that can we hidden those implementation classes to users somehow. such as we can have a default persistence.xml(or other name) that contains the inner implementation class in the idm-hibernate module. while for the users, they just need to configure the database connection, and we need to put the database connection properties outside. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBID-74) org.hibernate.exception.ConstraintViolationException in updatePassword method.

by Jeff Yu (JIRA)

org.hibernate.exception.ConstraintViolationException in updatePassword method. ------------------------------------------------------------------------------ Key: JBID-74 URL: https://jira.jboss.org/jira/browse/JBID-74 Project: JBoss Identity Issue Type: Bug Components: IDM Affects Versions: 1.0.0.alpha2 Reporter: Jeff Yu Assignee: Boleslaw Dawidowicz I was trying to invoke the 'updatePassword' to update the existed password, and then it throws following exception. I've added following two lines in the 'idm-maven2-example/DBTestCase', identitySession.getAttributesManager().updatePassword(eva, "oldPassword"); identitySession.getAttributesManager().updatePassword(eva, "newPassword"); org.hibernate.exception.ConstraintViolationException: could not insert: [org.jboss.identity.idm.impl.model.hibernate.HibernateIdentityObjectCredential] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:94) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.id.insert.AbstractSelectingDelegate.performInsert(AbstractSelectingDelegate.java:64) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2186) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2666) at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:71) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:321) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:204) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:130) at org.hibernate.event.def.DefaultPersistEventListener.entityIsTransient(DefaultPersistEventListener.java:154) at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:110) at org.hibernate.event.def.DefaultPersistEventListener.onPersist(DefaultPersistEventListener.java:61) at org.hibernate.impl.SessionImpl.firePersist(SessionImpl.java:645) at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:619) at org.hibernate.impl.SessionImpl.persist(SessionImpl.java:623) 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:585) at org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:342) at $Proxy30.persist(Unknown Source) at org.jboss.identity.idm.impl.store.hibernate.HibernateIdentityStoreImpl.updateCredential(HibernateIdentityStoreImpl.java:1731) at org.jboss.identity.idm.impl.repository.WrapperIdentityStoreRepository.updateCredential(WrapperIdentityStoreRepository.java:263) at org.jboss.identity.idm.impl.api.session.managers.AttributesManagerImpl.updatePassword(AttributesManagerImpl.java:316) at org.jboss.identity.idm.example.DBTestCase.testJBossIdentity(DBTestCase.java:90) 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:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) 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:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_CT_60 in statement [insert into identity_obj_credential (id, BINARY, IDENTITY_ID, TEXT, IDENTITY_TYPE) values (null, ?, ?, ?, ?)] at org.hsqldb.jdbc.Util.throwError(Unknown Source) at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source) at org.hibernate.id.insert.AbstractSelectingDelegate.performInsert(AbstractSelectingDelegate.java:57) ... 41 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-identity-issues May 2009