Is there a use case for Wicket *core* that requires an upgrade to servlet-api 2.5?
On Mon, Apr 14, 2008 at 3:43 PM, Zheng, Xiahong <[EMAIL PROTECTED]> wrote: > Websphere 6.1 is Java 5 and Servlet 2.4 or J2EE1.4. > > > > -----Original Message----- > From: C." Bergström [mailto:[EMAIL PROTECTED] > Sent: Monday, April 14, 2008 3:37 PM > To: [email protected] > Subject: [Discuss ]update servlet-api dependency to 2.5 > > So to prompt a discussion if there needs to be one.. > > Is it only TC 5.5? What % of the user base is on TC 5 vs TC 6 or Jetty > 6 or any other relatively modern app container that supports generics.. > > I'm going to leave my vote and opinion out of this. (I'm biased) Just > as each business needs to weigh the how much they live on the 'bleeding > edge'. Wicket 1.3 can be considered like servlet 2.3.. It's stable.. > production ready and the most important bugs will be back ported. The > same people pushing to use 1.4 for 'good' reasons in many cases could > influence to some degree an app container upgrade. > > (Yes I realize Cisco, Ask.com and others who are maybe using Wicket are > in a much more challenging infrastructure position, but..) > > Really what's the difference? Just the ability to influence an app > container upgrade? > > ./C > >
