[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-4307) Optional one-to-one association with join table cannot exist
Miroslav Havram (JIRA)
noreply at atlassian.com
Tue Mar 23 09:58:32 EDT 2010
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35924#action_35924 ]
Miroslav Havram commented on HHH-4307:
--------------------------------------
It had worked in versions 3.5.0-Beta-1 and 3.5.0-Beta-2 because hibernate.check_nullability by default evaluated to false in BeanValidationActivator.
Starting with version 3.5.0-CR-1 and changes in BeanValidationActivator, hibernate.check_nullability now evaluates by default to true - which activates nullability check (class Nullability) which fails in this case.
> Optional one-to-one association with join table cannot exist
> ------------------------------------------------------------
>
> Key: HHH-4307
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4307
> Project: Hibernate Core
> Issue Type: Bug
> Components: annotations
> Environment: Hibernate Core 3.3.2.GA
> JDK 1.6u14
> Reporter: Miroslav Havram
> Attachments: ann847.zip
>
>
> In the case of the optional one-to-one association with the join table, it is not possible to have independant instances of entities.
> Entity at the inverse end of the association cannot be persisted without being first linked to the entity on the other (non-inverse) end of the association.
--
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