Can you elaborate on why you don't like package level definitions?

My reason for not liking is is that is requires people to navigate their packages to see if the behavior has been redefined. But I like it as most of the time, categories of artifacts like JPA entities or model in general, action services etc are in separate packages so setting a behavior per category becomes very easy. 

On 11 déc. 2012, at 19:32, Gerhard Petracek <gerhard.petracek@gmail.com> wrote:

+1 for 2.b but -1 for a package annotation and/or config.

regards,
gerhard



2012/12/11 Emmanuel Bernard <emmanuel@hibernate.org>
That should hopefully be the last round. Here are the alternatives that
I think are viable http://goo.gl/ubjn3

Please give your feedback.

Emmanuel

On Tue 2012-10-23 18:19, Emmanuel Bernard wrote:
> For method validation, we have so far managed to get away with
> requiring an annotation based metadata to direct how method validation
> behaves.
>
> One question that popped up during the recent write up is whether or not
> getters should be considered regular methods and thus be intercepted and
> validation by CDI or AspectJ interceptors.
>
> I have my own ideas, but I'd like to get your opinion on the subject.
>
> Emmanuel
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev

_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev