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
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
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
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
-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
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
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
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
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
