My bad, sorry.
On Thu, Dec 2, 2010 at 11:14 AM, <pmuir(a)redhat.com> wrote:
As I said, jsf will still be entirely optional, it's just we will
no longer support jsf 1.2
On 2 Dec 2010, at 17:11, Clint Popetz <cpopetz(a)gmail.com> wrote:
> On Thu, Dec 2, 2010 at 11:02 AM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
>> On Thu, Dec 2, 2010 at 10:28 AM, Pete Muir <pmuir(a)redhat.com> wrote:
>>> AFACIT this will really force Tomcat etc. users to use JSF2...
>> Yep. I think this is a matter of us leaving the fence and deciding that we
>> are going to advocate the EE 6 technology stack as a baseline. We are
>> recommending a new programming model, after all, so I think it's consistent
>> to select the optimal compliments. I've was thinking along the same lines
>> for Seam Servlet...we should really be assuming we have Servlet 3, or at the
>> very least the Servlet-CDI integration (which Weld Servlet patches in).
>> Otherwise, we sort of look hesitant in our message to adopt EE 6. So I'm all
>> for it.
> (Loves CDI, uses wicket, deploys a large app on a cluster of 30 tomcat
> instances, doesn't want a needless jsf dependency.)
>> Dan Allen
>> Principal Software Engineer, Red Hat | Author of Seam in Action
>> Registered Linux User #231597
>> weld-dev mailing list
> Clint Popetz
> Scalable Web Application Development