I've been wondering that myself. I'm working on a couple of bits around the Tomcat integration an run into what looks like a couple of bugs in Tomcat. I've been wondering whether to send over a patch to Tomcat so hopefully it would be considered for the next release, and then going forward. The alternative is to work-around the issues in OpenEJB by subclassing the relevant Tomcat classes and wiring them into StandardContext, with the advantage that older Tomcat versions also get the fix. I'm still not sure what the right route is - currently I'm just changing what I need to, to prove the problem, and then I'll post up some diffs.
Back to your question though - I don't think I have a particularly strong feeling either way. Tomcat 7 is definitely needed for TomEE to be webprofile certified, I very much doubt we could certify with Tomcat 6. I can definitely see some advantage to not needing to worry about supporting older versions. I just wonder how many people are using Tomcat 6 - it still seems to be used by a lot of the customers I work with in my day job. Jon On Wed, Aug 31, 2011 at 8:41 AM, Romain Manni-Bucau <[email protected]>wrote: > Hi, > > for the 4.0.0 should we break the tomcat 5.5 and tomcat 6.0 support? > > JEE 6 needs tomcat 7 so i think we can strip a lot of ugly code. > > IMHO Tomcat 6 is still used but if somebody wants to write a jee 6 > application he will easily go to tomcat 7. > > A user recently saw we are using a tomcat 7 specific API in the > tomcatWebappBuilder. This one can be replaced by a Tomcat6/Tomcat 7 one but > with some efforts (constructor args). I'm not sure it is useful to twist > our > code like it. > > What's your opinions? > > - Romain >
