Hi, Working on integration tests improvement (1), I discovered that almost all persistence beans have TABLE generated Id strategy defined in orm.xml: user, role, membership, mapping, connInstance, attr. Anyway AUTO generated Id strategy is defined for following of the persistence beans: AbstractDerAttr, AbstractVirAttr, Notification, UserRequest. Is there good reason to keep it differently?
Actually I am struggling with strange effect in NotificationTestITCase: create() and issueSYNCOPE83() work successfully ONLY if delete() removes Notification with id=101. If delete() is marked with @Ignore - create() and issueSYNCOPE83() throw DataIntegrityViolation exception. Even more strange: if previously running tests: AuthenticationTestITCase, ConfigurationtestITCase, ConnInstanceTestITCase, DerivedSchemaTestITCase are deactivated, problem is not reproducible anymore - create() and issueSYNCOPE83() work successfully without delete(). I guess the problem is caused Id generation, will investigate it a little bit more. Have anyone other ideas what could be the reason? Cheers, Andrei. (1) https://issues.apache.org/jira/browse/SYNCOPE-268
