Move to servlet-api 3.0 for Wicket 6
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
Re: Move to servlet-api 3.0 for Wicket 6
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
Re: Move to servlet-api 3.0 for Wicket 6
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
Re: Move to servlet-api 3.0 for Wicket 6
I am -1 to require Servlet 3.0 for -core. Currently Wicket core doesn't even need anything from 2.5. 2.4 covers all our needs. Requiring Servlet 3.0 for Wicket 6 will leave some users at 1.4.x/1.5.x and we all can agree there is no much man power in supporting old branches at the moment. Anyone ever tried doing anything with AsyncContext within a Wicket Page ? I see some benefit in IResource but creating custom IResource for that doesn't require -core to depend on 3.0. My 2c On Fri, Apr 13, 2012 at 4:13 PM, 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 -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
Re: Move to servlet-api 3.0 for Wicket 6
-1 to jump on Servlet 3.0. Tomcat 6 is still be widely used as deployment server and if we required version 3.0 we would prevent a lot of people from migrating to Wicket 6. I am -1 to require Servlet 3.0 for -core. Currently Wicket core doesn't even need anything from 2.5. 2.4 covers all our needs. Requiring Servlet 3.0 for Wicket 6 will leave some users at 1.4.x/1.5.x and we all can agree there is no much man power in supporting old branches at the moment. Anyone ever tried doing anything with AsyncContext within a Wicket Page ? I see some benefit in IResource but creating custom IResource for that doesn't require -core to depend on 3.0. My 2c On Fri, Apr 13, 2012 at 4:13 PM, Peter Ertlpe...@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
Re: Move to servlet-api 3.0 for Wicket 6
Using 3.0 in a module might prove to be quite difficult. The main problem is that they changed the artifactId from servlet-api to javax.servlet-api. This makes it impossible to simple set a dependency management, you need to exclude the dependencies on servlet 2.5. But even if you manage to do this in maven, Eclipse still screws up your classpath and you will end up with duplicate classes. Personally I dont see why a framework released in 2012 still needs to support servlet containers versions of over 5 years old. If you are able to upgrade Wicket, you should also be able to upgrade other parts of your deployment. IMHO Wicket should move forward with the rest of the world. Best regards, Emond On Friday 13 April 2012 16:23:16 Martin Grigorov wrote: I am -1 to require Servlet 3.0 for -core. Currently Wicket core doesn't even need anything from 2.5. 2.4 covers all our needs. Requiring Servlet 3.0 for Wicket 6 will leave some users at 1.4.x/1.5.x and we all can agree there is no much man power in supporting old branches at the moment. Anyone ever tried doing anything with AsyncContext within a Wicket Page ? I see some benefit in IResource but creating custom IResource for that doesn't require -core to depend on 3.0. My 2c On Fri, Apr 13, 2012 at 4:13 PM, 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
Re: Move to servlet-api 3.0 for Wicket 6
Explain to me then what Wicket it self really needs from the new API? So what are we going to change? On Apr 13, 2012 2:32 PM, 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
Re: Move to servlet-api 3.0 for Wicket 6
The most important feature IMO is async servlets, which is used by Atmosphere. It allows you to suspend requests without relying on container specific implementations, like continuations in Jetty. Currently the atmosphere example, part of wicket-examples in sandbox/atmosphere uses the async attribute. Without it, it will probably work on most containers, but only because Atmosphere detects the container and has modules for most popular containers. I can live with Servlet 2.5, but I don't see why we should keep supporting these ancient API's. I'd like to move on. On Friday 13 April 2012 21:37:22 Johan Compagner wrote: Explain to me then what Wicket it self really needs from the new API? So what are we going to change? On Apr 13, 2012 2:32 PM, 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
Re: Move to servlet-api 3.0 for Wicket 6
Using 3.0 in a module might prove to be quite difficult. The main problem is that they changed the artifactId from servlet-api to javax.servlet-api. This makes it impossible to simple set a dependency management, you need to exclude the dependencies on servlet 2.5. I think you need to do this only if you will actually develop the atmosphere module, or will try to access some Servlet 3.0 new methods directly in the application. Not sure, though. But even if you manage to do this in maven, Eclipse still screws up your classpath and you will end up with duplicate classes. Not if you exclude servlet-api from jetty's dependencies. Personally I dont see why a framework released in 2012 still needs to support servlet containers versions of over 5 years old. If you are able to upgrade Wicket, you should also be able to upgrade other parts of your deployment. IMHO Wicket should move forward with the rest of the world. Because supporting them costs virtually nothing? Because many of the framework users are still using 5 years old servlet containers? The infrastructure guys will happily deploy a new application with new jars (they probably don't even know what a jar file is), but won't take the hassle of upgrading all installed servers (and buying new licenses, and making new support contracts, and re-training all IT department) just because I want to use a new version of a third-party library. And well, the very first server with Java EE 6 support was Glassfish v3, in 2010. Tomcat and JBoss added that support only about a year ago. So, even if you are using a 1 year old server version, chances are you are still limited to Servlet 2.5! It's still too early to jump to the newest shiny thing.
