Begin forwarded message:
> From: Emmanuel Bernard <emman...@hibernate.org> > Date: 15 janvier 2010 13:58:19 HNEC > To: Guenther Demetz <guenther.dem...@wuerth-phoenix.com> > Subject: Re: [hibernate-dev] 3.5.0-Beta-3 has different behaviour on commit > as 3.5.0-Beta-2, is this intended? > > All should be fixed in trunk now. > http://opensource.atlassian.com/projects/hibernate/browse/HHH-4806 > http://opensource.atlassian.com/projects/hibernate/browse/HHH-4807 > > > On 15 janv. 2010, at 13:41, Guenther Demetz wrote: > >> Emmanuel Bernard schrieb: >>> >>> ... >>> So I imagine you don't use bean validation and the DB raises a constraint >>> failure. >> Yes! >>> >>> >>> I will get that fixed either tonight or tomorrow. >> N.B.: You can fix the bug with just one line change: >> TransactionImpl.java line 84: >> < throw new entityManager.convert( (HibernateException)e ); >> --- >> > wrappedException = entityManager.convert( >> > (HibernateException)e ); >> >> I tested it and my test-suite works. >> >> I like to notice you another behaviour change problem between Hiberante 3.3 >> and 3.5: >> In class BeanValidationActivator version 3.5.beta3 on line 34 you set >> Environment.CHECK_NULLABILITY explicitly to "false" >> even if I not using any BeanValidation (mode is resulting >> ValidationMode.AUTO to me). >> This goes in contrast to CHECK_NULLABILITY api-documentations, which tells >> that is Defaults to true. >> >> /** >> * Enable nullability checking. >> * Raises an exception if a property marked as not-null is null. >> * Default to true. >> */ >> public static final String CHECK_NULLABILITY = >> "hibernate.check_nullability"; >> >> In poor words: users which migrate to Hiberante3.5 and don't use >> BeanValidation must now explicitely set >> hibernate.check_nullability=true >> in order to have the same behavior as before. >> >> best regards >> G.D. >> > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
