clearing up issues around jsvc or jakarta commons daemon
subscribed at red56.co.uk
Thu Mar 30 09:31:43 UTC 2006
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  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 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.
More information about the freebsd-java