The new annotations don't add much for framework developers, they just replace the web.xml file, in a hard-to-maintain fashion.
Asynchronous servlets, in the other hand, are a nice addition to the platform, but unless the atmosphere module absolutely requires special support from wicket-core, and cannot be implemented by hooks, I think it's better to keep core 2.5-compatible, and make the atmosphere module dependent on 3.0. At work, we have just upgraded some services to Tomcat 7, and we still have many JBoss 4.2.3 servers around. I think that is the case for many, many shops out there. If there's no real need to require servlet 3.0, I don't think it would be a good idea to do it. On Fri, Apr 13, 2012 at 9:32 AM, Emond Papegaaij <emond.papega...@topicus.nl> wrote: > 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
