<div class="gmail_quote">On Thu, Dec 17, 2009 at 12:05 PM, Lincoln Baxter, III <span dir="ltr"><<a href="mailto:lincolnbaxter@gmail.com">lincolnbaxter@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;">
<p>Thanks for posting this Dan. Its been on my to do list, but as usual, you've summed up the points thoroughly and clearly. I am 100% on board with acknowledging / deprecating the jsf built-in managed bean facility in favor of a platform feature. IMO, jsf is crippled without a full DI container</p>
</blockquote><div>Right. And the nice, neutral message for JSF 2 is "For your programming model, use CDI (platform managed beans) or provide your own alternative bean container, such as Spring. We are in the business of creating a UI component model."<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>