Skip to content

TCK should not try declare generator with same name multiple times #714

@beikov

Description

@beikov

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.generatorTypeTest1
  • ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest2
  • ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest3
  • ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest4
  • ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest5
  • ee.jakarta.tck.persistence.core.types.generator.Client1.generatorTypeTest6
  • ee.jakarta.tck.persistence.core.types.generator.Client2.generatorTypeSequenceTest
  • ee.jakarta.tck.persistence.core.types.generator.Client3.sequenceGeneratorOnEntityTest
  • ee.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).

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions