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 Andraschko > <[email protected]>: > > +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 <[email protected]>: > >> Le 26 avr. 2015 17:51, "Joseph Bergmark" <[email protected]> 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 hurt >> >>> On Sun, Apr 26, 2015 at 10:55 AM, Romain Manni-Bucau < >> [email protected]> >>> wrote: >>> >>>> 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" <[email protected]> a écrit : >>>>> >>>>> Hi folks! >>>>> >>>>> I wonder if we still like to support tomcat6 and servlet-2.5. We are >>>> talking about technology which got introduced more than 10 years ago >> and is >>>> outdated since 5 years now. >>>>> >>>>> When switching to servlet-3.0++ we would have a few options: >>>>> >>>>> Make WebBeansConfigurationListener just implement the >> contextInitialized >>>> and destroy and register the BeginWebBeansListener and >> EndWebBeansListener >>>> dynamically as first respective last listener in the chain. >>>>> >>>>> Any objections? >>>>> >>>>> LieGrue, >>>>> strub >>>> >>
