From owner-freebsd-java@FreeBSD.ORG Thu Mar 30 09:31:43 2006 Return-Path: X-Original-To: freebsd-java@freebsd.org Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3178616A41F for ; Thu, 30 Mar 2006 09:31:43 +0000 (UTC) (envelope-from subscribed@red56.co.uk) Received: from fanta.soda.co.uk (soda-2.dsl1.easynet.co.uk [212.135.162.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A785043D48 for ; Thu, 30 Mar 2006 09:31:42 +0000 (GMT) (envelope-from subscribed@red56.co.uk) Received: from localhost (localhost.soda.co.uk [127.0.0.1]) by fanta.soda.co.uk (Postfix) with ESMTP id BEA5E23BA for ; Thu, 30 Mar 2006 10:31:41 +0100 (BST) Received: from fanta.soda.co.uk ([127.0.0.1]) by localhost (fanta.soda.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78128-03 for ; Thu, 30 Mar 2006 10:31:38 +0100 (BST) Received: from [192.168.1.163] (unknown [192.168.1.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by fanta.soda.co.uk (Postfix) with ESMTP id 770182393 for ; Thu, 30 Mar 2006 10:31:38 +0100 (BST) Message-ID: <442BA579.70509@red56.co.uk> Date: Thu, 30 Mar 2006 10:31:37 +0100 From: Tim Diggins User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-java@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at soda.co.uk Subject: clearing up issues around jsvc or jakarta commons daemon X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2006 09:31:43 -0000 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