On Sun, Jan 10, 2010 at 9:39 AM, Pete Muir <pmuir(a)redhat.com> wrote:
On 8 Jan 2010, at 17:38, Dan Allen wrote:
> On Fri, Jan 8, 2010 at 11:30 AM, Roger Kitain <Roger.Kitain(a)sun.com>
wrote:
> It would be a nice feature to be able to have CDI injection in Phase
> Listeners also, as any Servlet/JSF/CDI integration is always welcome
> where applicable
>
>
> This is actually a more general requirement (which we may have discussed
in passing). Any user-defined class instance that JSF creates should be
classified as a component in Java EE. But, to accommodate that without tying
JSF directly to the platform (a separation we have always maintained), there
should be a pluggable class instance resolver which could be satisfied with
a CDI implementation, a Spring bean implementation, etc.
I had initially thought we should just specify that JSF is required
to
support this injection, but I can see that specifying an SPI to support
instantiation/lifecycle management of these objects would fit well with the
pluggability goal that JSF has.
+1 To provide further justification, I think this is really going to help
users take advantage of the new extension points in JSF 2 without leaving
them to figure out how to tie those classes back into their programming
model. Otherwise, we my hear a lot of complaints.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen