| Re: [eclipselink-users] Problems with mapping having @Id with @GeneratedValue in @MappedSuperClass but the sequence in subclass |
I can't think of a good workaround other than what you have already mentioned, that is, defining the id on each subclass.
Another solution and perhaps a good suggestion for the JPA expert group would be to allow this through an @AttributeOverride, e.g.
@AttributeOverride(
name="id",
generatedValue=@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "SEQ_STORE_PROJECT")
)
@SequenceGenerator(name = "SEQ_STORE_PROJECT", sequenceName = "project_id_seq", allocationSize = 1)
class Project extends AbstractDomainObject
@AttributeOverride(
name="id",
generatedValue=@GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "SEQ_STORE_USER")
)
@SequenceGenerator(name = "SEQ_STORE_USER", sequenceName = "user_id_seq", allocationSize = 1)
class User extends AbstractDomainObject
This maitains the unique naming across the persistence unit and leverages the existing attribute override functionality.
Please enter a bug against EclipseLink though. Similarly to Hibernate which provided a feature above and beyond the spec, EclipseLink could do the same.