[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3898) Add a flag to disable Nullability.checkNullability() and the exception raised in this case
Francisco Peredo (JIRA)
noreply at atlassian.com
Fri Nov 13 13:36:08 EST 2009
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34578#action_34578 ]
Francisco Peredo commented on HHH-3898:
---------------------------------------
I wonder.. does this means that now both "optional=true and nullable=false" are treated as schema hints... and all object-level validation is left for JSR-303 based annotations?
> Add a flag to disable Nullability.checkNullability() and the exception raised in this case
> ------------------------------------------------------------------------------------------
>
> Key: HHH-3898
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3898
> Project: Hibernate Core
> Issue Type: New Feature
> Components: core
> Reporter: Emmanuel Bernard
> Fix For: 3.5.0.Beta-1
>
>
> Useful when Bean Validation is on as otherwise the checkNullability is applied before BV has time to kick in and messes up the expected exception
> The default must be true as capt obvious rightly pointed out ;)
--
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