Thanks Thomas, sounds reasonable. Though there is still myfaces-2.1.x which runs perfectly fine with only servlet-2.5
This is really only required for JSF-2.2. Now I personally assume that people start using JSF-2.2 in production around Q3 next year (2013). And until then I hope that all people who really are eager to use JSF-2.2 moved on to servlet-3.0 already ;) Not sure about big banks, etc which still use EE5 containers and upgraded 'manually' (placing myfaces into WARs). But those companies will switch to JSF-2.2 earliest 2014 and I'm not exactly sure what we can expect then. Most probably all users/customers are on EE6 then at least. LieGrue, strub >________________________________ > From: Thomas Andraschko <[email protected]> >To: MyFaces Development <[email protected]>; Mark Struberg ><[email protected]> >Sent: Friday, November 16, 2012 10:37 PM >Subject: Re: servlet-3.0 > > >Hi, > >i think it would be better for many users to still support 2.5 and only >require 3.0 for the htmlInputFileRenderer. >Many users already use other fileuploads like PrimeFaces and don't need this. > >Regards, >Thomas > > >2012/11/16 Mark Struberg <[email protected]> > >Hi folks! >> >>We did lots of tricks to keep core free of servlet-3.0. But sadly we leak it >>in MyFaces-2.2 due to myfaces-shared HtmlInputFileRenderer. >>This function requires the multi MIME Part which is new in servlet-3.0. >> >>That means servlet-2.5 support is only guaranteed if you don't use that >>feature. >> >>How do we treat this? Require servlet-3.0 for mf-2.2 or let it crash and >>write up a note about it? >> >>LieGrue, >>strub >> > > >
