[hibernate-dev] Behaviour of validation mode "auto" in case of error during validator factory bootstrap

[Steve Ebersole]

+1 fof fail-fast in regards to bootstrap problems whenever possible

On Wed, Feb 1, 2017 at 5:12 AM Sanne Grinovero <sanne at hibernate.org> wrote:

> +1 for fail fast
>
> I think we generally aim for that as a good practice - when doable -
> and I suspect people expect it.
>
> On 1 February 2017 at 10:33, Gunnar Morling <gunnar at hibernate.org> wrote:
> > Hi,
> >
> > JPA defines for validation mode "auto" that bean validation must occur
> > if a BV provider is present and that no validation shall occur
> > otherwise.
> >
> > What should happen though if a BV provider such as HV is present but
> > it fails to bootstrap? In case of HV this happens if no expression
> > language implementation can be found.
> >
> > Currently, the user has a very hard time to find out about this, as
> > this exception essentially is suppressed (for mode "callback" the
> > exception is raised).
> >
> > Should we raise a specific exception in HV if it cannot be
> > bootstrapped? In ORM, we could handle that one specifically and raise
> > it also if for validation mode "auto" (would have to happen
> > reflectively, though, as to avoid a hard dependency).
> >
> > I can do this change but first wanted to make sure that this is inline
> > with what you all think should be done.
> >
> > Thanks,
> >
> > --Gunnar
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>