| just to clarify, while the illegal argument exception goes away, we still get a warning for duplicate generator name and currently like vlad mentioned there is no workaround other than push the @Id into the subclasses. The following issue introduced a flag hibernate.jpa.compliance.global_id_generators allows you to choose whether to enforce the JPA spec(throw the illegal argument exception on boot). But it does not change the underlying behaviour of allowing two identifier generators with the same name and different configurations.... https://hibernate.atlassian.net/browse/HHH-12454 |
