On Wed, Aug 22, 2012 at 10:48 PM, Martin Grigorov <[email protected]> wrote: > I still see no reason to require Servlet 3.0. > Wicket runs fine on servlet 3.0 containers and you can use some of the > features from 3.0, but I don't believe that you will add some code to > Wicket that will make big benefit for the users next week. I guess you > will just add an item to the migration page that Wicket requires > Servlet 3.0 and this will scare half of the users out there, as you > did with Wicket 1.5/Servlet 2.5 :-)
The issue is that 6.x will probably live for quite a while, and if we actually want to use stuff that is native to servlet 3, we will have painted ourselves into a corner. I thought that websockets required servlet 3, so when we move them out of experimental phase, IIUC they can only be added into wicket 7 (my quick try showed that servlet 3 breaks some code–didn't investigate too much further). > Stop looking for excuses to build Wicket 6.0.0! Do it! :-) Still shaving a yak (or rather: upgrading most dependencies in parent-pom)! Martijn
