I was thinking it was time to start planning out a release package when I decided to try using Tomcat 5 instead of Tomcat 4 (which is vendor supplied) and I'm disappointed to find out that the changes in the class files have combined the docroot, work and scratch dir variable initialization so changing docroot dynamically on the fly doesn't work cause it then complains about no WEB-INF and no work dir and exits with a 500 error msg.
I thought to be safe I'd try Tomcat 6 (forced me to use JSDK 1.5) and it exhibits the same issue.
It looks like my current solution only works with Tomcat 4.1 (I didn't try anything older).
I'm wondering how to resolve this, I doubt they'd make changes in the source to allow the ability to modify the docroot without affecting other directory designations because I need it for my module.
Maybe using Tomcat was a poor choice based on the current available config state or maybe there is another method in the newer Tomcat's to achieve the docroot change without disrupting the others or maybe I should consider dropping it as a possible method of implementation?
-- Dale
PGP.sig
Description: This is a digitally signed message part
