-
Notifications
You must be signed in to change notification settings - Fork 73
Closed
Labels
3.2.0acceptedAccepted certification requestAccepted certification requestchallengeTCK challengeTCK challenge
Description
The following list of tests is failing on Hibernate ORM, because the TCK assumes it can define two generators with the same name. Once in DataTypes2 and then also in DataTypes3:
ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest1ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest2ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest3ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest4ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest5ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest6ee.jakarta.tck.persistence.core.types.generator.Client2.generatorTypeSequenceTestee.jakarta.tck.persistence.core.types.generator.Client3.sequenceGeneratorOnEntityTestee.jakarta.tck.persistence.core.types.generator.Client4.sequenceGeneratorOnPropertyTest
The javadoc of e.g. @SequenceGenerator clearly says that names are global and hence multiple definitions are problematic:
The scope of the generator name is global to the persistence unit (across all generator types).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
3.2.0acceptedAccepted certification requestAccepted certification requestchallengeTCK challengeTCK challenge