On Wed, Sep 7, 2011 at 08:47, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
This API offers quite a different view onto CDI than BeanManager, and from the comments we've received on CDI 1.0 [1] I believe it is an API that people are going to find more useful, leaving BeanManager for more "power" use cases. This was my reason to split it out, but I'm open to other suggestions?<br>
</blockquote><div><br></div><div>That's the other benefit. It puts BeanManager back where it belongs, which is a low-level API. Before we call CDI 1.1 final, I hope we can survey the popular uses of BeanManager and see if any of those are similar to this case where a better API could be provided to avoid the need for BeanManager to be overly used. (It's possible this could knock out 80-90% of the cases).</div>
<div><br></div><div>-Dan</div><div><br></div></div>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>