[bv-dev] BVAL-436 disable executable validation altogether

[Emmanuel Bernard]

It feels like override-validated-executables would provide a lit of
executable types validated. I don't think that feature makes sense as
deciding if a specific executable type is validated depends on a class
basis(eg JPA vs JAX-Rs action method.

I thought you had in mind a global flag to disable it entirely. I have
mocked two approaches, please give me your thoughts:

https://gist.github.com/emmanuelbernard/2191bad0c7d8742a8eea

Approach #1 has my preference I believe.

Check out the schema design after both approaches in the gist. I reused
the design JPA uses to exclude classes from being scanned. But I am not
an XML expert and there might be better options.

Likewise BootstrapConfiguration would get a Boolean
getDisableValidationExecution() method that is ignored by Bean
Validation engines proper.

Emmanuel


On Fri 2013-03-08 21:33, Hardy Ferentschik wrote:
> 
> On 8 Jan 2013, at 7:50 PM, Emmanuel Bernard <emmanuel at hibernate.org> wrote:
> 
> > I am sympathetic to the idea but being very late in the game, I want a
> > strong backing by the expert group.
> > Please speak up your feedback (whatever it is).
> > 
> > I anticipate the following impact:
> > 
> > - integration chapter will add the disable rule
> > - add the disable flag to the BootstrapConfiguration
> > - add the disable option to the XSD
> > - oh and find a name and good structure for it. Hardy any idea?
> 
> maybe one could mirror <default-validated-executables/> and call it <override-validated-executables/> !?
> 
> --Hardy
> 
> 
> 
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev