We can/should drop t6 but not servlet 2.5
Not sure i get your comment. Servlet 2 or 3 doesnt change anything for us
Le 26 avr. 2015 16:33, Mark Struberg strub...@yahoo.de a écrit :
Hi folks!
I wonder if we still like to support tomcat6 and servlet-2.5. We are
talking about technology which
Perhaps I'm being dense, but tomcat 6 is at spec level servlet 2.5 and
tomcat 7 is at spec level servlet 3.0 right? Requiring Servlet 3.0 lets us
leverage ServletContainerInitializers.
On Sun, Apr 26, 2015 at 10:55 AM, Romain Manni-Bucau rmannibu...@gmail.com
wrote:
We can/should drop t6 but
I hoped to be able to utilize programmatic configuration of servlet listeners.
But there is only a addListener method. For re-ordering I would also need a
remove. Which doesn’t exist…
So back to thinking what I might probably improve…
LieGrue,
strub
Am 26.04.2015 um 21:27 schrieb Thomas
what can be done is to standardize (=force) listener names. Then user can
put them in web.xml and we can check if already there. If there dont do
anything for this listener if not then do our magic. That said it still
doesnt mean breaking 2.5 compatibility since the initalizer would be 100%
+1 if there is any benefit
our last customer with servlet 2.5 switched to TC7 this year
2015-04-26 19:31 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:
Le 26 avr. 2015 17:51, Joseph Bergmark bergm...@apache.org a écrit :
Perhaps I'm being dense, but tomcat 6 is at spec level servlet
Le 26 avr. 2015 17:51, Joseph Bergmark bergm...@apache.org a écrit :
Perhaps I'm being dense, but tomcat 6 is at spec level servlet 2.5 and
tomcat 7 is at spec level servlet 3.0 right? Requiring Servlet 3.0 lets us
leverage ServletContainerInitializers.
Deploying it in a 2.5 container doesnt
