[ https://issues.apache.org/jira/browse/SYNCOPE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò updated SYNCOPE-437: ------------------------------------------- Comment: was deleted (was: FAILURE: Integrated in Syncope-trunk #501 (See [https://builds.apache.org/job/Syncope-trunk/501/]) [SYNCOPE-437] Reworked the patch a bit for trunk, then applied, thanks (ilgrosso: rev 1541487) * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/Notification.java * /syncope/trunk/core/src/main/resources/META-INF/orm.xml * /syncope/trunk/core/src/main/resources/META-INF/orm.xml.oracle * /syncope/trunk/core/src/main/resources/META-INF/orm.xml.sqlserver * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/NotificationTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/NotificationTestITCase.java * /syncope/trunk/core/src/test/resources/content.xml ) > Wrong ID generation for new Notification instances > -------------------------------------------------- > > Key: SYNCOPE-437 > URL: https://issues.apache.org/jira/browse/SYNCOPE-437 > Project: Syncope > Issue Type: Bug > Components: core > Affects Versions: 1.1.4 > Reporter: Andrea Patricelli > Assignee: Andrea Patricelli > Fix For: 1.1.5, 1.2.0 > > Attachments: SYNCOPE-437.patch > > > When creating a new instance of Notification, IDs of created instances start > from 1 and not from 100 as expected; this is due to the AUTO generation of > IDs for Notification entity. > This may lead to possible primary key violation errors; in particular if > importing from content.xml notification instances as happens in "dev" > profile. -- This message was sent by Atlassian JIRA (v6.1#6144)