I'm -0 to going to servlet 3.0. I think it's a bad idea, but I'm not currently using Wicket at my "day job", so I wouldn't want to stand in the way of progress. I like the idea of having an optional module that depends on 3.0, though, with the core being 2.5-compatible.
On Fri, Apr 13, 2012 at 9:13 AM, Peter Ertl <pe...@gmx.org> wrote: > +1 atmosphere alone is reason enough, no reason to stay on < 3.0 forever and > there are enough servers out there supporting it > > > Am 13.04.2012 um 14:32 schrieb Emond Papegaaij: > >> Hi all, >> >> It was already mentioned by Martijn some time ago as a suggestion for the >> roadmap for Wicket 6, but it was never decided. The question is: should we >> move to servlet-api 3.0 or stay at 2.5. Servlet 3.0 has been around for over >> 2 >> years now and is supported by most (all?) servlet containers. It allows us to >> use things like the new annotations and asynchronous servlets. >> >> I'm +1 for moving to servlet 3.0 and already have some work done on the >> sandbox/atmosphere branch to get it working. >> >> Best regards, >> Emond >
