Upgrade to Tomcat 7
Description
Attachments
- 25 Sep 2011, 07:41 PM
relates to
Activity

Sam Ottenhoff October 27, 2011 at 7:18 AM
Sakai 2.9 QA servers are now running on Tomcat 7

Charles Hedrick September 30, 2011 at 10:06 AM
I'm sympathetic with the desire to make installation as easy as possible, but I'm not sure it's realistic to let people build from source and install without reading the notes, unless we make significant changes to what we're shipping. I think at a minimum they'll need to get the maven command to do the build, and in realistic cases they need to read what stuff to download, and various other things from the notes.
I'd love to see us ship the source with a bundled tomcat that is appropriately configured, and with a simple build script at the top level of trunk. I'd also recommend shipping a copy of mysql. The problem is that developers typically need to look at the database, and you can't really do that with hsqldb. There's actually a command-line SQL client, but it won't work while the system is running, because it has to open the files exclusively (and most devs won't know how to set it up anyway – it's not straightforward).
I'm constantly setting up new instances in order to test on different versions. While I've done it enough times that it's not a big deal, still, every time I need to test on a different version I have to remember all the stuff to do. And every time we have someone new start working on Sakai, we lose the first day of work just getting the thing to build.

Matthew Jones September 30, 2011 at 9:05 AM
We don't have any QA servers yet for 2.9, just nightly2. So if Chris has this updated we're good to go.
I think my only concern is making it easier (if possible) for those who maybe don't want to read the release notes or miss this step to patch their tomcat configuration files. I know if you 'pack-demo' or 'pack-bin' then we do supply a tomcat, which many people probably use too.
It seems kind of like overkill (what a sed regex would solve) but the metro project install script which updates the config file with an ant/java class seems kinda nice. Guess there's no easier solution for this problem.
https://svn.java.net/svn/wsit~svn/trunk/wsit/bundles/metro-standalone/src/main/resources/metro-on-tomcat.xml
http://www.java2s.com/Open-Source/Java-Document/6.0-JDK-Modules-com.sun/wsit/com/sun/xml/ws/installer/UpdateSharedLoaderProp.java.htm

Charles Hedrick September 30, 2011 at 7:34 AM
Done. I ended up putting dav-server.jar in common, to minimize hackery in catalina.properties.
DAV will take the tomcat version from master/pom.xml, so sakai.tomcat.version should be 7.x.
I believe this will break the QA servers until they are upgraded to Tomcat 7.
merge -r98831:98833 https://source.sakaiproject.org/svn/dav/trunk

Charles Hedrick September 29, 2011 at 3:59 PM
OK, I'll commit the DAV changes tomorrow. I'd rather not make changes like this and then immediately go to sleep. I'll do a last check that I've got everything right and then check it in.
Details
Priority
MajorAffects versions
Components
Assignee
Charles HedrickCharles HedrickReporter
mm
Details
Details
Priority
Affects versions
Components
Assignee

Reporter

Since release of JPA2 and Servlets 3.0. More so because of Servlet 3.0 there are major changes anticipated in existing web frameworks as perhaps new frameworks are on the way. The most compelling feature seems to beAsynchronous processing support in Servlet 3.0. Since as of now there is no success of moving to tomcat 6 at least it is pre QA.
Sakai team could perhaps move to Tomcat 7 directly . It may take a short while for many web frameworks to catch up to tomcat 7 and there may be more child Jiras associated with this update/feature but it will significantly reduces technical debt of sakai.
http://www.tomcatexpert.com/blog/2011/08/10/end-life-announced-apache-tomcat-55