I'm getting a little frustrated about this. In fact I only wanted to run Apache and Tomcat on the same machine listening on 2 different IP's. (Both on port 80). I found that Tomcat is seemingly unable to listen to only 1 IP and inteferes with Apache, which as a mature product is simple to setup in this way. So now I'm re-visiting the apache module thing which I looked at before a few months ago. When I looked at this before I found that Tomcat3 (production) is really only compatible with mod_jserv, due to the config file being automatically generated for inclusion into httpd.conf. No mod_jk config file is generated and I was unsuccessful in manually building oneand getting it to work. So I moved onto Tomcat4 which although in Beta is allegedly much better and uses the improved mod_jk. As so often happens the project was shelved at the time, and now I'm revisiting it some months later I find a new kid on the block, mod_webapp. What is mod_webapp? no documentation exists, although there are a few newsgroup messages about it, It appears however that my newly downloaded distro of Tomcat4 supports mod_webapp natively and apparently not mod_jk anymore. So..... who can advise me on what I should use, I realise I'm messing with very young products here but the different versions seem significantly different and I'd rather be forward looking within reason. When will this development stabilize? By the way ----- Apache Org ---- I love you guys!!! JJ
