6:46 a.m.
Author: remy.maucherat(a)jboss.com
Date: 2010-05-07 07:46:42 -0400 (Fri, 07 May 2010)
New Revision: 1467
Modified:
trunk/BUILDING.txt
trunk/RELEASE-NOTES
Log:
- Cleanup.
Modified: trunk/BUILDING.txt
===================================================================
--- trunk/BUILDING.txt 2010-05-07 11:46:06 UTC (rev 1466)
+++ trunk/BUILDING.txt 2010-05-07 11:46:42 UTC (rev 1467)
@@ -105,20 +105,8 @@
cd ${jboss-web.source}
ant
-(5) Building the Servlet and JSP API documentation
+(5) Building EL parser with JavaCC 4.1+:
-The documentation can be easily built:
-
- cd ${jboss-web.source}
- ant -f dist.xml dist-javadoc
-
-(6) Building a release running tests:
-
- cd ${jboss-web.source}
- ant -f dist.xml release
-
-(7) Building EL parser with JavaCC 4.1+:
-
Download JavaCC 4.1+
export JAVACC_HOME=/somepath/javacc-4.1
export PATH=$JAVACC_HOME/bin:$PATH
Modified: trunk/RELEASE-NOTES
===================================================================
--- trunk/RELEASE-NOTES 2010-05-07 11:46:06 UTC (rev 1466)
+++ trunk/RELEASE-NOTES 2010-05-07 11:46:42 UTC (rev 1467)
@@ -4,23 +4,6 @@
Release Notes
-=============================
-KNOWN ISSUES IN THIS RELEASE:
-=============================
-
-* Dependency Changes
-* JNI Based Applications
-* Bundled APIs
-* Web application reloading and static fields in shared libraries
-* Tomcat on Linux
-* Enabling SSI and CGI Support
-* Security manager URLs
-* Symlinking static resources
-* Enabling invoker servlet
-* Viewing the Tomcat Change Log
-* When all else fails
-
-
===================
Dependency Changes:
===================
@@ -57,43 +40,6 @@
during the lifetime of a particular JVM.
-=============
-Bundled APIs:
-=============
-A standard installation of JBoss Web makes all of the following APIs available
-for use by web applications (by placing them in "common/lib"):
-* el-api.jar (EL 2.1 API)
-* jsp-api.jar (JSP 2.2 API)
-* servlet-api.jar (Servlet 3.0 API)
-
-In server/default/deploy/jbossweb.sar you will find
-* jbossweb.jar which contains most of the JBoss Web classes.
-* jstl.jar jstl classes.
-* jasper-jdt.jar (Eclipse JDT 3.2 Java compiler)
-
-You can make additional APIs available to all of your web applications by
-putting unpacked classes into a "classes" directory (not created by default),
-or by placing them in JAR files in the "lib" directory.
-
-To override the XML parser implementation or interfaces, use the endorsed
-mechanism of the JVM. The default configuration defines JARs located in
-"endorsed" as endorsed.
-
-
-================================================================
-Web application reloading and static fields in shared libraries:
-================================================================
-Some shared libraries (many are part of the JDK) keep references to objects
-instantiated by the web application. To avoid class loading related problems
-(ClassCastExceptions, messages indicating that the classloader
-is stopped, etc.), the shared libraries state should be reinitialized.
-
-Something which might help is to avoid putting classes which would be
-referenced by a shared static field in the web application classloader,
-and putting them in the shared classloader instead (JARs should be put in the
-"lib" folder, and classes should be put in the "classes" folder).
-
-
=============================
Enabling SSI and CGI Support:
=============================
@@ -101,16 +47,6 @@
attributes documentation for more details.
-======================
-Security manager URLs:
-======================
-In order to grant security permissions to JARs located inside the
-web application repository, use URLs of of the following format
-in your policy file:
-
-file:${catalina.home}/webapps/examples/WEB-INF/lib/driver.jar
-
-
============================
Symlinking static resources:
============================
@@ -121,19 +57,6 @@
the check.
-=========================
-Enabling invoker servlet:
-=========================
-Starting with Tomcat 4.1.12, the invoker servlet is no longer available by
-default in all webapps. Enabling it for all webapps is possible by editing
-$CATALINA_HOME/conf/web.xml to uncomment the "/servlet/*" servlet-mapping
-definition.
-
-Using the invoker servlet in a production environment is not recommended and
-is unsupported. More details are available on the Tomcat FAQ at
-http://tomcat.apache.org/faq/misc.html#invoker.
-
-
================================
Viewing the JBoss Web Change Log:
================================