<div><div>method-validation should be easy</div><div>(you just have to change the ProcessAnnotatedType during bootstrapping (of the cdi container) via a portable cdi extension</div><div>-> there is no need for a bv-implementation to cache/... something here).</div>
<div><br></div><div>constructor-validation (esp. handling detected violations) is the difficult part.</div><div><br></div><div>regards,</div><div>gerhard</div></div><div><br></div><br><br><div class="gmail_quote">2013/2/7 Michael Nascimento <span dir="ltr"><<a href="mailto:misterm@gmail.com" target="_blank">misterm@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Binding the inceptor to the annotation is simply a matter of enhancing<br>
its metadata via an extension. Supporting the information declared via<br>
xml is also possible via a CDI extension. Both solutions will be<br>
executed while the CDI container is booting, so there is no need for<br>
caching.<br>
<br>
If we had a dynamic API, that allowed this to be changed during<br>
runtime, then you would need something different.<br>
<br>
Regards,<br>
Michael<br>
<div class="HOEnZb"><div class="h5"><br>
On Mon, Feb 4, 2013 at 4:08 PM, Emmanuel Bernard <<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a>> wrote:<br>
> While reviewing the interceptor specification, I realized that<br>
> interceptors lifecycle is bound to the object lifecycle they intercept.<br>
> In other words, it is not trivial to keep caches around for example<br>
> caches that now if a method should be intercepted or not.<br>
><br>
> Is that a problem for the expected CDI interceptor implementations?<br>
> I am asking to make sure we are not making a mistake by not considering<br>
> @ValidateExecutable in BV engines.<br>
><br>
> An interceptor should either:<br>
><br>
> - explicitly be set only on the methods that should be intercepted and<br>
> not more<br>
> - always recompute @ValidatedExecutable for every new instance of the<br>
> targeted object<br>
> - use some third party CDI bean responsible for the caching<br>
><br>
> In other words are we good?<br>
> _______________________________________________<br>
> beanvalidation-dev mailing list<br>
> <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
_______________________________________________<br>
beanvalidation-dev mailing list<br>
<a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
</div></div></blockquote></div><br>