From owner-freebsd-ports@FreeBSD.ORG Mon Jul 21 01:26:55 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F6DF37B401; Mon, 21 Jul 2003 01:26:55 -0700 (PDT) Received: from zaphod.euronet.nl (zaphod.euronet.nl [194.134.168.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B26243FCB; Mon, 21 Jul 2003 01:26:54 -0700 (PDT) (envelope-from ernst@zaphod.euronet.nl) Received: from zaphod.euronet.nl (localhost [127.0.0.1]) by zaphod.euronet.nl (8.12.9/8.12.9) with ESMTP id h6L8QuAf044269; Mon, 21 Jul 2003 10:26:56 +0200 (CEST) (envelope-from ernst@zaphod.euronet.nl) Received: from localhost (localhost [[UNIX: localhost]]) by zaphod.euronet.nl (8.12.9/8.12.9/Submit) id h6L8QuIf044268; Mon, 21 Jul 2003 10:26:56 +0200 (CEST) From: Ernst de Haan To: java@FreeBSD.org, ports@FreeBSD.org Date: Mon, 21 Jul 2003 10:26:56 +0200 User-Agent: KMail/1.5.1 X-Address: Muiderstraat 1, Amsterdam, Netherlands MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307211026.56111.znerd@FreeBSD.org> Subject: Ports: Deploying WAR files X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 08:26:55 -0000 Folks, Does anyone have any ideas on deploying WAR files from a port? Some applications nowadays consist of a single WAR file. Should we not find a standard way to deploy these applications in an existing servlet container? We could do the following: 1) dedicate a single directory for WAR files, e.g.: /usr/local/share/java/webapps In this directory we could stick all WAR files that need to be deployed automatically. 2) we could set a variable to point to that location, in bsd.java.mk: WAR_DIR=${LOCALBASE}/share/java/webapps 3) we could modify the servlet container ports (www/orion, www/tomcat41, etc) to use ${WAR_DIR} as their primary location for WAR files. Either with a configuration setting or with a symbolic link. 4) Then we could introduce a variable SERVLET_CONTAINER and set it to the servlet container port to install when one is needed. By default it would be set to TOMCAT, but it could also be overridden in /etc/make.conf, to be set to ORION, for example. 5) Finally, we could specify that ports that install a WAR file must set USE_SERVLET_CONTAINER to YES. Then they could use WAR_DIR in the port Makefile to put the WAR file in. The ports system will add the appropriate servlet container as a runtime dependency (to RUN_DEPENDS). Biggest issue with this is probably that it changes the existing servlet container ports. And thoughts on this? Ernst