<br><br><div class="gmail_quote">On Mon, Jan 11, 2010 at 1:41 PM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div class="im">On Sun, Jan 10, 2010 at 9:39 AM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com" target="_blank">pmuir@redhat.com</a>></span> wrote:<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="im"><br>
On 8 Jan 2010, at 17:38, Dan Allen wrote:<br>
<br>
> On Fri, Jan 8, 2010 at 11:30 AM, Roger Kitain <<a href="mailto:Roger.Kitain@sun.com" target="_blank">Roger.Kitain@sun.com</a>> wrote:<br>
> It would be a nice feature to be able to have CDI injection in Phase<br>
> Listeners also, as any Servlet/JSF/CDI integration is always welcome<br>
> where applicable<br>
><br>
><br></div>
> 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.<br>
</div></blockquote><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
<br>
</div>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.<br>
</blockquote></div><div><br>+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.<font color="#888888"></font></div>
</div></blockquote><div><br>Should I file a spec issue?<br><br>-Dan <br></div></div><br>-- <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>