Re: [cdi-dev] Easier access to CDI outside of Java EE, easier access to instances
I was just chatting to Marius, and I would propose we also offer Instance<> for
injection directly into extensions. It won't be usable during lifecycle events, but
can be easily used during application execution. I'll write this up later.
On 8 Sep 2011, at 12:57, Dan Allen wrote:
On Wed, Sep 7, 2011 at 08:47, Pete Muir <pmuir(a)redhat.com>
wrote:
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?
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).
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction