You wouldn't believe how many developers are still bound to old or
lame versions of webcontainers and struggle with their managers for an
upgrade.
I mandate for not upgrading the servlet api requirements unless there
are really compelling reasons (nice to have is not enough).
Besides: What would be the benefit in wicket of having the context
path outside the scope of a request?
You can still use servlet api 2.5 and wicket together without making
it a hard requirement.
Alternatively if you _really_ need 2.5 somewhere in the code you could
use some reflection based code to check for existence of servlet api
2.5 methods before invoking them and otherwise degrade gracefully.
Am 13.04.2008 um 01:55 schrieb James Carman:
On Sat, Apr 12, 2008 at 9:28 AM, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
This is a vote to update our servlet API dependency to 2.5 (since we
require Java 5, there is little use to stay with 2.3 iiuc)
[ ] servletapi 2.5 ftw!
[ ] servletapi 2.4 ftw!
[ ] servletapi 2.3 ftw!
[x] servletapi 2.4 ftw!
I agree with the others on this one. Changing versions just for that
new method doesn't seem like justification enough and we can use JDK5
on Tomcat 5.5 (I am currently).
