Re: Wicket 6: some hanging fruit before final?

2012-10-29 Thread Martin Grigorov
Minor issues with requiring Servlet 3: https://issues.apache.org/bugzilla/show_bug.cgi?id=54065 On Thu, Aug 23, 2012 at 1:02 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Thu, Aug 23, 2012 at 10:58 AM, Emond Papegaaij emond.papega...@topicus.nl wrote: I've started a vote some time

Re: Wicket 6: some hanging fruit before final?

2012-08-23 Thread Emond Papegaaij
I've started a vote some time ago about this (somewhere in april), and it was decided not to move to servlet 3 for wicket 6. Wicket itself does not (yet) require it, and users are free to use a servlet 3 container. Even if some part of wicket requires servlet 3, you can have that part depend on

Re: Wicket 6: some hanging fruit before final?

2012-08-23 Thread Martijn Dashorst
On Thu, Aug 23, 2012 at 10:58 AM, Emond Papegaaij emond.papega...@topicus.nl wrote: I've started a vote some time ago about this (somewhere in april), and it was decided not to move to servlet 3 for wicket 6. Wicket itself does not (yet) require it, and users are free to use a servlet 3

Wicket 6: some hanging fruit before final?

2012-08-22 Thread Martijn Dashorst
All, As I was preparing to build a final, I noticed that we don't yet have moved to servlet 3 in master. I thought that for the web socket stuff we needed to at least move to 3.0. I do see a commit in the history that adds servlet 3 done by Emond. I also see a commit reverting Jetty from jetty 8

Re: Wicket 6: some hanging fruit before final?

2012-08-22 Thread Martin Grigorov
Hi, Requiring Servlet 3.x as minimum version has never been in the scope of Wicket 6. It is neither in the roadmap page nor there was any mail discussion about this. I think this is some confusion in/between you and Emond. He also mentioned this few months ago in IRC. I see no reason to require

Re: Wicket 6: some hanging fruit before final?

2012-08-22 Thread Martijn Dashorst
http://s.apache.org/wicket-servlet3-discuss It has been proposed a couple of times for the roadmap for 6. There is no confusion between Emond and myself (at least for servlet 3, I won't comment on any confusion on other topics :-)). We both think that servlet 3 is out long enough and supported

Re: Wicket 6: some hanging fruit before final?

2012-08-22 Thread tetsuo
If the code doesn't require it, why add it artificially? Is there any planned feature that may potentially require it? On Wed, Aug 22, 2012 at 5:35 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: http://s.apache.org/wicket-servlet3-discuss It has been proposed a couple of times for

Re: Wicket 6: some hanging fruit before final?

2012-08-22 Thread Martin Grigorov
On Wed, Aug 22, 2012 at 11:35 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: http://s.apache.org/wicket-servlet3-discuss I remember just the talk in IRC :-/ It has been proposed a couple of times for the roadmap for 6. There is no confusion between Emond and myself (at least for

Re: Wicket 6: some hanging fruit before final?

2012-08-22 Thread Martijn Dashorst
On Wed, Aug 22, 2012 at 10:48 PM, Martin Grigorov mgrigo...@apache.org 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