*** empty log message ***

7 files changed, 422 insertions, 0 deletions

diff --git a/net-www/jboss/files/3.2.5/NEWS.Gentoo b/net-www/jboss/files/3.2.5/NEWS.Gentoo
new file mode 100644
index 000000000000..d036c3b88772
--- /dev/null
+++ b/net-www/jboss/files/3.2.5/NEWS.Gentoo
@@ -0,0 +1,46 @@
+-*-text-*- $Id: NEWS.Gentoo,v 1.1 2004/07/20 03:50:56 mkennedy Exp $
+
+* net-www/jboss-3.2.5
+
+SERVER_HOME Changes
+-------------------
+
+Prior to this release in Portage, the SERVER_HOME (ie. /var/lib/jboss)
+used to deploy user applications was maintained with CONFIG_PROTECT.
+There are a few problems with this approach:
+
+    1. Upon updating, you may have to merge over 100 files with
+       etc-update.
+
+    2. Most of the files in SERVER_HOME are binary in nature and do
+       not benifit from CONFIG_PROTECT.
+
+    3. The CONFIG_PROTECT mechanism is only capable of merging files.
+       Thus the mechanism cannot support updates which require old
+       files in SERVER_HOME to be removed.
+
+Release net-www/jboss-3.2.5 onward will no longer maintain SERVER_HOME
+with CONFIG_PROTECT.  Instead of this, we recommended you to consider
+creating your own SERVER_HOME sub-directory based on the 3 templates
+provided by the JBoss installation (ie. SERVER_HOME/all,
+SERVER_HOME/default and SERVER_HOME/minimal).
+
+After you have made your own SERVER_HOME sub-directory, simply
+annotate /etc/conf.d/jboss so that JBoss uses your SERVER_HOME
+sub-directory rather than the default one. e.g.
+
+    cp -a /var/lib/jboss/default /var/lib/jboss/myserver
+    sed -i 's,^\(JBOSS_CONF=\).*,\1"myserver",g' /etc/conf.d/jboss
+
+Log4J Changes
+-------------
+
+The log4j.xml configuration file now sets prority INFO for
+"org.apache.commons" category which is extremely noise at DEBUG
+priority.
+
+
+Authors of this Document
+------------------------
+
+Matthew Kennedy <mkennedy@gentoo.org>
diff --git a/net-www/jboss/files/3.2.5/README.Gentoo b/net-www/jboss/files/3.2.5/README.Gentoo
new file mode 100644
index 000000000000..e99fed3c0338
--- /dev/null
+++ b/net-www/jboss/files/3.2.5/README.Gentoo
@@ -0,0 +1,62 @@
+-*-text-*- $Id: README.Gentoo,v 1.1 2004/07/20 03:50:56 mkennedy Exp $
+
+Starting 
+-------- 
+
+Start JBoss by running the jboss RC script found in /etc/init.d/.  Do
+the regular 'rc-update jboss <runlevel>' to automatically start JBoss
+upon entering a runlevel.  Customizing the JBoss setup by changing the
+environment variables in /etc/conf.d/jboss.  Refer to that file for
+further documentation on the environment variables used during
+startup.
+
+For security reasons, the application server is running as the 'jboss'
+user.  This may be changed in the /etc/conf.d/jboss script.
+
+NOTE: ANY LOCAL USER MAY STOP A RUNNING JBOSS.  YOU SHOULD CONSIDER
+THIS ASPECT FOR PRODUCTION SYSTEMS.  
+
+Tips on securing your JBoss installations can be found along with
+other documentation at the JBoss Wiki:
+
+       http://jboss.org/wiki/Wiki.jsp
+       http://www.jboss.org/wiki/Wiki.jsp?page=SecureJBoss
+
+
+Logging 
+-------
+
+All configurations shipping with this ebuild have been set up to log
+to the /var/log/jboss/server file using a time/date based rolling
+file appender.
+
+While console logging is turned on for debugging purposes, standard
+out and standard err are redirected to /dev/null by default.  This may
+be changed in /etc/conf.d/jboss.  As the application server is running
+as 'jboss', you will have to tweak /dev/console's access permissions
+to allow jboss access to the device.
+
+
+Gentoo Specific News about the JBoss port
+-----------------------------------------
+
+NEWS.Gentoo is now installed with this document.  It documents
+high-level changes to this port.
+
+
+Client applications
+-------------------
+
+The jars required for compiling and running client applications are
+installed to /usr/share/jboss/lib.  Add these jars to your classpath
+with the java-config command using either the --set-system-classpath
+or --set-user-classpath parameter.
+
+Enjoy!
+
+
+Authors of this Document
+------------------------
+
+tho <thomas.osterlie@acm.org>
+Matthew Kennedy <mkennedy@gentoo.org>
diff --git a/net-www/jboss/files/3.2.5/catalog b/net-www/jboss/files/3.2.5/catalog
new file mode 100644
index 000000000000..91c09e9fc7de
--- /dev/null
+++ b/net-www/jboss/files/3.2.5/catalog
@@ -0,0 +1,27 @@
+
+  -- Catalog data for JBoss/Gentoo SGML integration
+
+  -- This set was extracted from the DTD files in the build output
+     directory, build/output/${P}/docs/dtd/
+
+PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application Client 1.3//EN" "application-client_1_3.dtd"
+PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "application_1_3.dtd"
+PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "ejb-jar_2_0.dtd"
+PUBLIC "-//JBoss//DTD JAWS 2.4//EN" "jaws_2_4.dtd"
+PUBLIC "-//JBoss//DTD JAWS 3.0//EN" "jboss-app_3_0.dtd"
+PUBLIC "-//JBoss//DTD J2EE Application 1.3//EN" "jboss-app_3_0.dtd"
+PUBLIC "-//JBoss//DTD J2EE Application 1.3V2//EN" "jboss-app_3_2.dtd"
+PUBLIC "-//JBoss//DTD MBean Service 3.2//EN" "jboss-service_3_2.dtd"
+PUBLIC "-//JBoss//DTD Web Application 2.2//EN" "jboss-web.dtd"
+PUBLIC "-//JBoss//DTD Web Application 2.3//EN" "jboss-web_3_0.dtd"
+PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN" "jboss-web_3_2.dtd"
+PUBLIC "-//JBoss//DTD JBOSS//EN" "jboss.dtd"
+PUBLIC "-//JBoss//DTD JBOSS 2.4//EN" "jboss_2_4.dtd"
+PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "jboss_3_0.dtd"
+PUBLIC "-//JBoss//DTD JBOSS 3.2//EN" "jboss_3_2.dtd"
+PUBLIC "-//JBoss//DTD JBOSS XMBEAN 1.0//EN" "jboss_xmbean_1_0.dtd"
+PUBLIC "-//JBoss//DTD JBOSS XMBEAN 1.1//EN" "jboss_xmbean_1_1.dtd"
+PUBLIC "-//JBoss//DTD JBOSSCMP-JDBC 3.0//EN" "jbosscmp-jdbc_3_0.dtd"
+PUBLIC "-//JBoss//DTD JBOSSCMP-JDBC 3.2//EN" "jbosscmp-jdbc_3_2.dtd"
+PUBLIC "-//JBoss//DTD JBOSS Security Config 3.0//EN" "security_config.dtd"
+PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "web-app_2_3.dtd"
diff --git a/net-www/jboss/files/3.2.5/conf.d/jboss b/net-www/jboss/files/3.2.5/conf.d/jboss
new file mode 100644
index 000000000000..9147dbf054c8
--- /dev/null
+++ b/net-www/jboss/files/3.2.5/conf.d/jboss
@@ -0,0 +1,82 @@
+# -*- mode: shell-script; mode: outline-minor; outline-regexp: "##+"; indent-tabs-mode: nil -*-
+
+## GENERAL SETTINGS
+
+# You can choose which configuration you want to run JBoss with.  The
+# default configuration is, you guessed it, 'default'. The Gentoo
+# JBoss installation ships with two other predefined configurations;
+# 'all' and 'minimal'. The configurations are located in
+# $JBOSS_HOME/server/
+
+# JBOSS_CONF="all"
+JBOSS_CONF="default"
+# JBOSS_CONF="minimal"
+
+# Console logging defaults to '/dev/null'. This env variable is
+# included for debugging purposes.  You might have to run add
+# $JBOSS_USER to the 'console' group to gain access to '/dev/console'.
+
+JBOSS_CONSOLE="/dev/null" 
+# JBOSS_CONSOLE="/dev/console"
+
+# The user JBoss will run as.
+
+JBOSS_USER="jboss"
+
+
+## SPECIFIC SETTINGS
+
+SERVER_SETTINGS=""
+
+# The directory JBoss will use for temporary file storage
+
+SERVER_SETTINGS="${SERVER_SETTINGS} -Djboss.server.temp.dir=/var/tmp/jboss"
+
+# The directory which JBoss will use for persistent data file storage
+
+SERVER_SETTINGS="${SERVER_SETTINGS} -Djboss.server.data.dir=/var/cache/jboss"
+
+# The base URL for calculating server home URLs.  In a stock JBoss
+# install, this would be <jboss_home>/server/ where sub-directories
+# default, minimal and all exist.  Our defaults are /var/lib/jboss to
+# be consistent with other servers such as PostgreSQL and Apache.
+
+SERVER_HOME="/var/lib/jboss"
+SERVER_SETTINGS="${SERVER_SETTINGS} -Djboss.server.base.url=file://${SERVER_HOME}"
+
+# Whether or not the server should exit the JVM on shutdown (comment
+# out to disable)
+
+# SERVER_SETTINGS="${SERVER_SETTINGS} -Djboss.server.exitonshutdown"
+
+# Whether or not the server should shutdown synchronously (true) or
+# asynchronously (false).
+
+SERVER_SETTINGS="${SERVER_SETTINGS} -Djboss.server.exitonshutdown=false"
+
+# The address JBoss will bind services to.  (Note: JBoss 3.2.3 ignores
+# the JVM environment parameter in favour of the command line switch.)
+
+JBOSS_BIND_ADDRESS="0.0.0.0"
+
+
+## STARTUP/SHUTDOWN CONFIGURATION
+
+# Commands used in starting/stopping the server.  Normally you would
+# not need to change the following settings.
+
+# We need to have JBOSS_HOME and JAVA_HOME set in order to start
+# jboss.
+
+[ -z "$JBOSS_HOME" ] \
+    && export JBOSS_HOME=`grep JBOSS_HOME /etc/profile.env | sed -e "s;.*=;;" -e "s;';;g"`
+[ -z "$JAVA_HOME" ] \
+    && export JAVA_HOME=`java-config --jdk-home`
+
+# Commands for starting and stopping the server
+
+CMD_START="JAVA_OPTS=\"${SERVER_SETTINGS}\" ${JBOSS_HOME}/bin/run.sh -b ${JBOSS_BIND_ADDRESS} -c ${JBOSS_CONF}" 
+
+CMD_STOP="${JAVA_HOME}/bin/java -classpath ${JBOSS_HOME}/bin/shutdown.jar:${JBOSS_HOME}/lib/jboss-system.jar:`java-config --classpath=jboss` org.jboss.Shutdown -S"
+
+SUBIT="su $JBOSS_USER -c "
diff --git a/net-www/jboss/files/3.2.5/env.d/50jboss b/net-www/jboss/files/3.2.5/env.d/50jboss
new file mode 100644
index 000000000000..92bc5e1feb30
--- /dev/null
+++ b/net-www/jboss/files/3.2.5/env.d/50jboss
@@ -0,0 +1 @@
+JBOSS_HOME="@JBOSSPREFIX@"
diff --git a/net-www/jboss/files/3.2.5/init.d/jboss b/net-www/jboss/files/3.2.5/init.d/jboss
new file mode 100644
index 000000000000..7427a49ee4bb
--- /dev/null
+++ b/net-www/jboss/files/3.2.5/init.d/jboss
@@ -0,0 +1,37 @@
+#!/sbin/runscript
+# Copyright 1999-2004 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: /var/cvsroot/gentoo-x86/net-www/jboss/files/3.2.5/init.d/jboss,v 1.1 2004/07/20 03:50:56 mkennedy Exp $
+
+depend() {
+    need net
+}
+
+start() {
+	ebegin "Starting JBoss"
+	if [ -z "$JBOSS_HOME" ]; then
+		eerror "The JBOSS_HOME environment variable is not set."
+		return 1
+	fi
+	if [ ! -d ${SERVER_HOME}/${JBOSS_CONF}/tmp ]; then
+		mkdir ${SERVER_HOME}/${JBOSS_CONF}/tmp
+		chown jboss:jboss ${SERVER_HOME}/${JBOSS_CONF}/tmp
+	fi
+	cd ${SERVER_HOME}/${JBOSS_CONF}/tmp
+	if [ -z "${SUBIT}" ]; then
+		eval ${CMD_START} >${JBOSS_CONSOLE} 2>&1 &
+	else
+		${SUBIT} "${CMD_START} >${JBOSS_CONSOLE} 2>&1 &" 
+	fi
+	eend $?
+}
+
+stop() {
+	ebegin "Stopping JBoss"
+	if [ -z "$SUBIT" ]; then
+		${CMD_STOP}
+	else
+		${SUBIT} "$CMD_STOP"
+	fi 
+	eend $?
+}
diff --git a/net-www/jboss/files/3.2.5/log4j.xml b/net-www/jboss/files/3.2.5/log4j.xml
new file mode 100644
index 000000000000..c2f6f7ed6205
--- /dev/null
+++ b/net-www/jboss/files/3.2.5/log4j.xml
@@ -0,0 +1,167 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
+
+<!-- ===================================================================== -->
+<!--                                                                       -->
+<!--  Log4j Configuration                                                  -->
+<!--                                                                       -->
+<!-- ===================================================================== -->
+
+<!-- $Id: log4j.xml,v 1.1 2004/07/20 03:50:56 mkennedy Exp $ -->
+
+<!--
+   | For more configuration infromation and examples see the Jakarta Log4j
+   | owebsite: http://jakarta.apache.org/log4j
+ -->
+
+<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">
+
+  <!-- ================================= -->
+  <!-- Preserve messages in a local file -->
+  <!-- ================================= -->
+
+  <!-- A time/date based rolling appender -->
+  <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
+    <param name="File" value="/var/log/jboss/server.log"/>
+    <param name="Append" value="false"/>
+
+    <!-- Rollover at midnight each day -->
+<!--    <param name="DatePattern" value="'.'yyyy-MM-dd"/> -->
+
+    <!-- Rollover at the top of each hour -->
+    <param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
+
+    <layout class="org.apache.log4j.PatternLayout">
+      <!-- The default pattern: Date Priority [Category] Message\n -->
+      <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
+
+      <!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
+      <param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/>
+       -->
+
+    </layout>	    
+  </appender>
+
+  <!-- A size based file rolling appender
+  <appender name="FILE" class="org.jboss.logging.appender.RollingFileAppender">
+    <param name="File" value="${jboss.server.home.dir}/log/server.log"/>
+    <param name="Append" value="false"/>
+    <param name="MaxFileSize" value="500KB"/>
+    <param name="MaxBackupIndex" value="1"/>
+
+    <layout class="org.apache.log4j.PatternLayout">
+      <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
+    </layout>	    
+  </appender>
+  -->
+
+  <!-- ============================== -->
+  <!-- Append messages to the console -->
+  <!-- ============================== -->
+
+  <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
+    <param name="Threshold" value="INFO"/>
+    <param name="Target" value="System.out"/>
+
+    <layout class="org.apache.log4j.PatternLayout">
+      <!-- The default pattern: Date Priority [Category] Message\n -->
+      <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
+    </layout>
+  </appender>
+
+
+  <!-- ====================== -->
+  <!-- More Appender examples -->
+  <!-- ====================== -->
+
+  <!-- Buffer events and log them asynchronously
+  <appender name="ASYNC" class="org.apache.log4j.AsyncAppender">
+    <appender-ref ref="FILE"/>
+    <appender-ref ref="CONSOLE"/>
+    <appender-ref ref="SMTP"/>
+  </appender>
+  -->
+
+  <!-- EMail events to an administrator
+  <appender name="SMTP" class="org.apache.log4j.net.SMTPAppender">
+    <param name="Threshold" value="ERROR"/>
+    <param name="To" value="admin@myhost.domain.com"/>
+    <param name="From" value="nobody@myhost.domain.com"/>
+    <param name="Subject" value="JBoss Sever Errors"/>
+    <param name="SMTPHost" value="localhost"/>
+    <param name="BufferSize" value="10"/>
+    <layout class="org.apache.log4j.PatternLayout">
+      <param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}] %m%n"/>
+    </layout>
+  </appender>
+  -->
+
+  <!-- Syslog events
+  <appender name="SYSLOG" class="org.apache.log4j.net.SyslogAppender">
+    <param name="Facility" value="LOCAL7"/>
+    <param name="FacilityPrinting" value="true"/>
+    <param name="SyslogHost" value="localhost"/>
+  </appender>
+  -->
+ 
+
+  <!-- Log events to JMS (requires a topic to be created)
+  <appender name="JMS" class="org.apache.log4j.net.JMSAppender">
+    <param name="Threshold" value="ERROR"/>
+    <param name="TopicConnectionFactoryBindingName" value="java:/ConnectionFactory"/>
+    <param name="TopicBindingName" value="topic/MyErrorsTopic"/>
+  </appender>
+  -->
+
+  <!-- ================ -->
+  <!-- Limit categories -->
+  <!-- ================ -->
+
+  <!-- Limit JBoss categories to INFO
+  <category name="org.jboss">
+    <priority value="INFO"/>
+  </category>
+  -->
+
+  <!-- Increase the priority threshold for the DefaultDS category
+  <category name="DefaultDS">
+    <priority value="FATAL"/>
+  </category>
+  -->
+
+  <!-- Decrease the priority threshold for the org.jboss.varia category
+  <category name="org.jboss.varia">
+    <priority value="DEBUG"/>
+  </category>
+  -->
+
+  <!-- Quieten the incredibly noisey Apache Commons log messages -->
+  <category name="org.apache.commons">
+    <priority value="INFO"/>
+  </category>
+
+  <!--
+     | An example of enabling the custom TRACE level priority that is used
+     | by the JBoss internals to diagnose low level details. This example
+     | turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
+     | subpackages. This will produce A LOT of logging output.
+       If you use replace the log4j 1.2 jar with a 1.1.3 jar you will need to
+       change this from XLevel to XPriority.
+  <category name="org.jboss.system">
+    <priority value="TRACE" class="org.jboss.logging.XLevel"/>
+  </category>
+  <category name="org.jboss.ejb.plugins">
+    <priority value="TRACE" class="org.jboss.logging.XLevel"/>
+  </category>
+  -->
+
+  <!-- ======================= -->
+  <!-- Setup the Root category -->
+  <!-- ======================= -->
+
+  <root>
+    <appender-ref ref="CONSOLE"/>
+    <appender-ref ref="FILE"/>
+  </root>
+  
+</log4j:configuration>