Date: Thu, 30 Mar 2006 10:31:37 +0100 From: Tim Diggins <subscribed@red56.co.uk> To: freebsd-java@freebsd.org Subject: clearing up issues around jsvc or jakarta commons daemon Message-ID: <442BA579.70509@red56.co.uk>
next in thread | raw e-mail | index | archive | help
Hi - having googled and read around, there seems to be an approach to jakarta commons daemon (jsvc) that I don't understand. There is no FreeBSD port of it (there are darwinports and other OSX ports, however). The last discussion of this [1] simply states - "you must use .... (apache + mod_webdav/mod_proxy/mod_jk)" -- no discussion of why... However almost all *recent* informed discussion in the tomcat world suggests that one should never just blindly serve tomcat behind apache, unless there is reason to - instead you serve your application both ways, profile them both and choose the optimal solution (many times standalone tomcat is more appropriate, even with lots static files) With Jsvc / jakarta commons daemon, you can then start up tomcat on port 80 (and switch down to a lesser user) - just like apache httpd. On the tomcat site, there are full instructions[2] for how to compile on the tomcat site (including specific details for FreeBSD - there are even FreeBSD binaries around). So why no port? If there's just no one willing to do it, that's cool, but is there some reason that it __should not__ be done (security?), it would be good to understand that. thanks Tim [1] http://lists.freebsd.org/pipermail/freebsd-java/2004-March/001877.html [2] http://tomcat.apache.org/tomcat-5.5-doc/setup.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?442BA579.70509>