<div class="gmail_quote">On Sat, Mar 27, 2010 at 3:28 AM, Nicklas Karlsson <span dir="ltr"><<a href="mailto:nickarls@gmail.com">nickarls@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I think AfterBeanDiscovery is enough (which is already in the spec) for the autoenablement extension, right?<div><br></div><div>We could cast the BeanManager parameter to BeanManagerImpl and enable (and perhaps sort) all org.seam.* interceptors etc that the BM is aware of. Since there is a limited number of CDI implementations, we could also cast to other implementations after checking (non-imported, reflection) which one we are dealing with.</div>
<div><br></div><div>We could also throw in a</div><div><br></div><div>@AutoEnable(before="org.jboss.seam.foo.Interceptor") </div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><br></div><div>annotation if want to control the order manually or if we want to offer others to use this feature (in a seam context)</div>
<div><br></div></blockquote><div>True, we could go down that road.</div><div><br></div><div>-Dan</div><div><br></div></div>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br>
<br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>