<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>This looks like a normal use-case to me.</div><div><br></div><div>e.g. bean / class has more generic annotation binding,</div><div>where you are more fine-grained on the actual method.</div><div><br></div><div>Hence, imo, it should be supported.</div><div><br></div><div>-Ales</div><div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div bgcolor="#FFFFFF" text="#000000">According to the spec, BeanManager.resolveInterceptors() should
throw IAE if two instances of the same interceptor binding type are
given.<br>
<br>
o.j.weld.tests.interceptors.tb.GenericDAO is annotated @Tx(0) and
its method find() is annotated @Tx(1). The annotation's only member
is <b>Nonbinding</b>.<br>
<br>
- So @Tx(0) and @Tx(1) are considered to be the _same_ binding? <br>
- The spec allows (doesn't disallow) methods to be annotated with
the same binding type as the class, right?<br>
- However, calling resolveInterceptors with these two should throw
IAE? Currently it does not. <br>
<br>
I've made fixes for WELD-999 and now resolveInterceptors does in
fact throw IAE in this case. But I guess I now have to remove
duplicate bindings before calling resolveInterceptors in cases where
the method of a bean is annotated with the same binding type as the
bean itself.<br>
<br>
Am I wrong in assuming that @Tx(0) and @Tx(1) are the same binding?<br>
<br>
Regards<br>
Marko<br>
<br>
<br>
</div>
_______________________________________________<br>weld-dev mailing list<br><a href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/weld-dev</blockquote></div><br></body></html>