Index: lams_build/build.xml
===================================================================
RCS file: /usr/local/cvsroot/lams_build/build.xml,v
diff -u -r1.73 -r1.74
--- lams_build/build.xml	6 Feb 2009 06:47:38 -0000	1.73
+++ lams_build/build.xml	13 Feb 2009 17:31:36 -0000	1.74
@@ -164,16 +164,22 @@
 			<fileset dir="../${lams_learning}/${sub.build.language}"><include name="**" /></fileset>
 			<fileset dir="../${lams_admin}/${sub.build.language}"><include name="**" /></fileset>
 		</copy>
+
 		<!-- create a temporary ear -->
 		<ear destfile="${assembly.temp.ear}" compress="false"
 			appxml="${app.xml}">
 			<fileset dir="${assembly}/temp" includes="**" />
 		</ear>
+
 		<!-- remove temp lib -->
-<!--		<delete dir="${assembly}/temp" includeEmptyDirs="true" /> -->
+		<!--		<delete dir="${assembly}/temp" includeEmptyDirs="true" /> -->
 		<!-- explode the ear (Why doesn't the EAR task support exploded format?) -->
 		<!-- lams-central.war is already exploded when copied -->
 		<unjar src="${assembly.temp.ear}" dest="${assembly.lams.ear}" />
+		<!-- Add local copy of DTD so developers with no internet access can still build the project -->
+		<copy todir="${assembly.lams.ear}/META-INF" failonerror="true">
+			<fileset dir="${app.xml.dir}"><include name="application_1_3.dtd" /></fileset>
+		</copy>
 		<move file="${assembly.lams.ear}/lams-www.war" tofile="${assembly.lams.ear}/temp.war"/>
 		<unjar src="${assembly.lams.ear}/temp.war" dest="${assembly.lams.ear}/lams-www.war"/>
 		<delete file="${assembly.lams.ear}/temp.war"/>
Index: lams_build/shared.properties
===================================================================
RCS file: /usr/local/cvsroot/lams_build/shared.properties,v
diff -u -r1.31 -r1.32
--- lams_build/shared.properties	6 Feb 2009 02:11:23 -0000	1.31
+++ lams_build/shared.properties	13 Feb 2009 17:31:36 -0000	1.32
@@ -25,7 +25,8 @@
 assembly.temp.ear=${assembly}/temp.ear
 deploy.tool=deploy-tool
 lib=lib
-app.xml=conf/j2ee/${conf.application}.application.xml
+app.xml.dir=conf/j2ee
+app.xml=${app.xml.dir}/${conf.application}.application.xml
 lams_common=lams_common
 lams_admin=lams_admin
 lams_learning=lams_learning
Index: lams_build/conf/j2ee/application_1_3.dtd
===================================================================
RCS file: /usr/local/cvsroot/lams_build/conf/j2ee/Attic/application_1_3.dtd,v
diff -u
--- /dev/null	1 Jan 1970 00:00:00 -0000
+++ lams_build/conf/j2ee/application_1_3.dtd	13 Feb 2009 17:31:36 -0000	1.1
@@ -0,0 +1,271 @@
+<!--
+DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
+
+Copyright 2000-2007 Sun Microsystems, Inc. All rights reserved.
+
+The contents of this file are subject to the terms of either the GNU
+General Public License Version 2 only ("GPL") or the Common Development
+and Distribution License("CDDL") (collectively, the "License").  You
+may not use this file except in compliance with the License. You can obtain
+a copy of the License at https://glassfish.dev.java.net/public/CDDL+GPL.html
+or glassfish/bootstrap/legal/LICENSE.txt.  See the License for the specific
+language governing permissions and limitations under the License.
+
+When distributing the software, include this License Header Notice in each
+file and include the License file at glassfish/bootstrap/legal/LICENSE.txt.
+Sun designates this particular file as subject to the "Classpath" exception
+as provided by Sun in the GPL Version 2 section of the License file that
+accompanied this code.  If applicable, add the following below the License
+Header, with the fields enclosed by brackets [] replaced by your own
+identifying information: "Portions Copyrighted [year]
+[name of copyright owner]"
+
+Contributor(s):
+
+If you wish your version of this file to be governed by only the CDDL or
+only the GPL Version 2, indicate your decision by adding "[Contributor]
+elects to include this software in this distribution under the [CDDL or GPL
+Version 2] license."  If you don't indicate a single choice of license, a
+recipient has the option to distribute your version of this file under
+either the CDDL, the GPL Version 2 or to extend the choice of license to
+its licensees as provided above.  However, if you add GPL Version 2 code
+and therefore, elected the GPL Version 2 license, then the option applies
+only if the new code is made subject to such option by the copyright
+holder.
+-->
+
+<!--
+This is the XML DTD for the J2EE 1.3 application deployment
+descriptor.  All J2EE 1.3 application deployment descriptors
+must include a DOCTYPE of the following form:
+
+  <!DOCTYPE application PUBLIC
+	"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
+	"http://java.sun.com/dtd/application_1_3.dtd">
+
+-->
+
+<!--
+The following conventions apply to all J2EE deployment descriptor
+elements unless indicated otherwise.
+
+- In elements that contain PCDATA, leading and trailing whitespace
+  in the data may be ignored.
+
+- In elements whose value is an "enumerated type", the value is
+  case sensitive.
+
+- In elements that specify a pathname to a file within the same
+  JAR file, relative filenames (i.e., those not starting with "/")
+  are considered relative to the root of the JAR file's namespace.
+  Absolute filenames (i.e., those starting with "/") also specify
+  names in the root of the JAR file's namespace.  In general, relative
+  names are preferred.  The exception is .war files where absolute
+  names are preferred for consistency with the servlet API.
+-->
+
+
+<!--
+The application element is the root element of a J2EE application
+deployment descriptor.
+-->
+<!ELEMENT application (icon?, display-name, description?, module+,
+		security-role*)>
+
+<!--
+The alt-dd element specifies an optional URI to the post-assembly
+version of the deployment descriptor file for a particular J2EE module.
+The URI must specify the full pathname of the deployment descriptor
+file relative to the application's root directory. If alt-dd is not
+specified, the deployer must read the deployment descriptor from the
+default location and file name required by the respective component
+specification.
+
+Used in: module
+-->
+<!ELEMENT alt-dd (#PCDATA)>
+
+<!--
+The connector element specifies the URI of a resource adapter archive
+file, relative to the top level of the application package.
+
+Used in: module
+-->
+<!ELEMENT connector (#PCDATA)>
+
+<!--
+The context-root element specifies the context root of a web
+application.
+
+Used in: web
+-->
+<!ELEMENT context-root (#PCDATA)>
+
+<!--
+The description element is used to provide text describing the parent
+element.  The description element should include any information that
+the application ear file producer wants to provide to the consumer of
+the application ear file (i.e., to the Deployer). Typically, the tools
+used by the application ear file consumer will display the description
+when processing the parent element that contains the description.
+
+Used in: application, security-role
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!--
+The display-name element contains a short name that is intended to be
+displayed by tools.  The display name need not be unique.
+
+Used in: application
+
+Example:
+
+<display-name>Employee Self Service</display-name>
+-->
+<!ELEMENT display-name (#PCDATA)>
+
+<!--
+The ejb element specifies the URI of an ejb-jar, relative to the top
+level of the application package.
+
+Used in: module
+-->
+<!ELEMENT ejb (#PCDATA)>
+
+<!--
+The icon element contains small-icon and large-icon elements that
+specify the file names for small and a large GIF or JPEG icon images
+used to represent the parent element in a GUI tool.
+
+Used in: application
+-->
+<!ELEMENT icon (small-icon?, large-icon?)>
+
+<!--
+The java element specifies the URI of a java application client module,
+relative to the top level of the application package.
+
+Used in: module
+-->
+<!ELEMENT java (#PCDATA)>
+
+<!--
+The large-icon element contains the name of a file
+containing a large (32 x 32) icon image. The file
+name is a relative path within the application's
+ear file.
+
+The image may be either in the JPEG or GIF format.
+The icon can be used by tools.
+
+Used in: icon
+
+Example:
+
+<large-icon>employee-service-icon32x32.jpg</large-icon>
+-->
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+The module element represents a single J2EE module and contains a
+connector, ejb, java, or web element, which indicates the module type
+and contains a path to the module file, and an optional alt-dd element,
+which specifies an optional URI to the post-assembly version of the
+deployment descriptor.
+
+The application deployment descriptor must have one module element for
+each J2EE module in the application package.
+
+Used in: application
+-->
+<!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
+
+<!--
+The role-name element contains the name of a security role.
+
+The name must conform to the lexical rules for an NMTOKEN.
+
+Used in: security-role
+-->
+<!ELEMENT role-name (#PCDATA)>
+
+<!--
+The security-role element contains the definition of a security
+role. The definition consists of an optional description of the
+security role, and the security role name.
+
+Used in: application
+
+Example:
+
+    <security-role>
+	<description>
+	    This role includes all employees who are authorized
+	    to access the employee service application.
+	</description>
+	<role-name>employee</role-name>
+    </security-role>
+-->
+<!ELEMENT security-role (description?, role-name)>
+
+<!--
+The small-icon element contains the name of a file
+containing a small (16 x 16) icon image. The file
+name is a relative path within the application's
+ear file.
+
+The image may be either in the JPEG or GIF format.
+The icon can be used by tools.
+
+Used in: icon
+
+Example:
+
+<small-icon>employee-service-icon16x16.jpg</small-icon>
+-->
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+The web element contains the web-uri and context-root of a web
+application module.
+
+Used in: module
+-->
+<!ELEMENT web (web-uri, context-root)>
+
+<!--
+The web-uri element specifies the URI of a web application file,
+relative to the top level of the application package.
+
+Used in: web
+-->
+<!ELEMENT web-uri (#PCDATA)>
+
+<!--
+The ID mechanism is to allow tools that produce additional deployment
+information (i.e., information beyond the standard deployment
+descriptor information) to store the non-standard information in a
+separate file, and easily refer from these tool-specific files to the
+information in the standard deployment descriptor.
+
+Tools are not allowed to add the non-standard information into the
+standard deployment descriptor.
+-->
+
+<!ATTLIST alt-dd id ID #IMPLIED>
+<!ATTLIST application id ID #IMPLIED>
+<!ATTLIST connector id ID #IMPLIED>
+<!ATTLIST context-root id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST ejb id ID #IMPLIED>
+<!ATTLIST icon id ID #IMPLIED>
+<!ATTLIST java id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST module id ID #IMPLIED>
+<!ATTLIST role-name id ID #IMPLIED>
+<!ATTLIST security-role id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST web id ID #IMPLIED>
+<!ATTLIST web-uri id ID #IMPLIED>
Index: lams_build/conf/j2ee/lams.application.xml
===================================================================
RCS file: /usr/local/cvsroot/lams_build/conf/j2ee/lams.application.xml,v
diff -u -r1.7 -r1.8
--- lams_build/conf/j2ee/lams.application.xml	6 Feb 2009 02:11:22 -0000	1.7
+++ lams_build/conf/j2ee/lams.application.xml	13 Feb 2009 17:31:36 -0000	1.8
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN' 'http://java.sun.com/dtd/application_1_3.dtd'>
+<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN' 'application_1_3.dtd'>
 <application>
     <display-name>LAMS</display-name>
     <description>