[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-4358) Having to use @ForceDiscriminator kind of breaks JPA compatibility
Steve Ebersole (JIRA)
noreply at atlassian.com
Thu Dec 15 09:30:19 EST 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44598#comment-44598 ]
Steve Ebersole commented on HHH-4358:
-------------------------------------
Sorry Karsten, must have missed your pull request. Mind linking that again?
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list