From owner-freebsd-java Sun Mar 23 2: 8:53 2003 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 9B8A637B401 for ; Sun, 23 Mar 2003 02:08:51 -0800 (PST) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5538943F75 for ; Sun, 23 Mar 2003 02:08:49 -0800 (PST) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.12) id 18x2P7-000Fhh-00; Sun, 23 Mar 2003 12:08:37 +0200 Date: Sun, 23 Mar 2003 12:08:37 +0200 From: Sheldon Hearn To: Tom Samplonius Cc: Westbay Family , freebsd-java@FreeBSD.ORG Subject: Re: keytool and Tomcat https under 1.4.1 Message-ID: <20030323100837.GI740@starjuice.net> Mail-Followup-To: Tom Samplonius , Westbay Family , freebsd-java@FreeBSD.ORG References: <516F9055-5BFE-11D7-A432-000A9575BE46@seaple.icc.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.3i Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On (2003/03/22 13:43), Tom Samplonius wrote: > Disable the port's silly startup script in /usr/local/etc/rc.d, and use > Tomcat's own startup script startup.sh in the bin directory. See the > Tomcat install docs. As clarified in follow-up from the original poster, this wasn't the cause of the problem. :-) > In many cases, "ports" of Java applications is needless. The binary is > cross-platform already. And wrapping the app in a undocumented > propietary startup script isn't helping anyone. Most people are going to > better off downloading the Tomcat binary from http://jakarta.apache.org > than using the FreeBSD port. Just untar it, and run startup.sh. While it's true that many ports of Java applications don't need to do anything more than unpack a tarball into the correct location, ports are still useful because they a) make it very easy to locate and install software, e.g. cd /usr/ports/devel/jakarta-ant && make install clean b) cause packages to be built by the packaging system, for possible inclusion on FreeBSD release media. I believe that the second of these two will become critical to the success of FreeBSD as an enterprise server platform. I've been touting absence of Oracle and Java support as the two biggest threats to FreeBSD for a while now, even without a solid understanding of the Java platforms. :-) Basically, we need to get to the stage where FreeBSD release kits constitute (amongst other things) two things: a) a "cheap'n'easy" J2EE application server, and b) a "cheap'n'easy" Java development environment. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message