[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-4358) Having to use @ForceDiscriminator kind of breaks JPA compatibility

Having to use @ForceDiscriminator kind of breaks JPA compatibility ------------------------------------------------------------------ Key: HHH-4358 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4358 Project: Hibernate Core Issue Type: Improvement Components: annotations Environment: JPA Reporter: Steve Ebersole Assignee: Steve Ebersole Labels: jpa2 Fix For: 4.0.1 According to http://opensource.atlassian.com/projects/hibernate/browse/ANN-36 @ForceDiscriminator was created as a quick workaround to a problem. Yes, it solves the problem, but it creates a new problem: the source code which previously had only JPA annotations, now need to be annotated by a Hibernate annotation, causing that the the source code is now unable to use just any JPA provider. Major portability issue! Everyone who likes Open Source, hates Lock-Ins! My proposal: change the default to a more sane force=true, so that @ForceDiscriminator will not be needed for general JPA projects. (And create a @DisableDiscriminator Hibernate annotation, for those who like to brake their code). If changing default behavior is risky, don't fix this on older versions, but lets change this from 3.5.0-Beta2.