[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-4902) Handle JPA 2 requirement of setting id attribute to non-null with its equivalent of foreign-generator
Steve Ebersole (JIRA)
noreply at atlassian.com
Wed Feb 10 12:40:30 EST 2010
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Ebersole closed HHH-4902.
-------------------------------
Resolution: Fixed
> Handle JPA 2 requirement of setting id attribute to non-null with its equivalent of foreign-generator
> -----------------------------------------------------------------------------------------------------
>
> Key: HHH-4902
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4902
> Project: Hibernate Core
> Issue Type: Bug
> Components: core
> Reporter: Steve Ebersole
> Assignee: Steve Ebersole
> Fix For: 3.5.0-Next
>
> Time Spent: 4 hours, 9 minutes
> Remaining Estimate: 0 minutes
>
> JPA 2 defines an equivalent of the Hibernate foreign generator. However the spec implies (via a badly worded footnote) that users can manually set a value for that id attribute. However the spec is very clear that it is the association which drives the persisted id value, not the id attribute.
> So basically, the user can manually set the id value but it is completely expected to be ignored.
> Unfortunately that messes up the Hibernate notion of unsaved-value (how it distinguishes transient entities from detached entities). So we need to account for this in the persist listeners.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list