craigmcc 01/03/23 17:23:23
Modified: . README.txt RELEASE-NOTES-4.0-B2.txt build.bat
build.sh
Added: lib crimson.jar jaxp.jar
Log:
Add a special version of the jaxp.jar and crimson.jar files (from JAXP/1.1
final release) that have had the "sealed" attribute removed. These JARs
are used for the XML parser that Jasper uses (in directory "jasper"), to
avoid "package sealing violation" errors that occurred when the sealed
versions were used on JDK 1.3 systems when a web application loaded its
own parser from WEB-INF/lib.
WARNING: you MUST NOT replace jasper/jaxp.jar and jasper/crimson.jar with
versions from a different (even if newer) release of JAXP, unless the
"sealed" attribute has been removed from those files.
WARNING: The Tomcat 4.0 build process now ignores any JASPER_JAXP_HOME
and JASPER_JAXP_PARSER_JAR environment variables you may have set. The
scripts are hard coded to use the files in the "lib" directory being
checked in with this patch.
PR: Bugzilla #1002
Submitted by: [EMAIL PROTECTED]
Revision Changes Path
1.14 +8 -0 jakarta-tomcat-4.0/README.txt
Index: README.txt
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/README.txt,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- README.txt 2001/03/23 01:12:10 1.13
+++ README.txt 2001/03/24 01:23:21 1.14
@@ -266,3 +266,11 @@
JASPER_JAXP_HOME [default: JAXP_HOME]
JASPER_JAXP_PARSER_JAR [default: JAXP_PARSER_JAR]
+
+ ----> WARNING: The current build process uses a special copy of the
+ jaxp.jar and crimson.jar files from JAXP/1.1 (Final)
+ that has had the "sealed" attribute removed. This works
+ around "sealing violation" errors that occur when Tomcat 4.0
+ is run under JDK 1.3. As a result of this, the
+ JASPER_JAXP_HOME and JASPER_JAXP_PARSER_JAR environment
+ variables are currently ignored.
1.2 +15 -19 jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B2.txt
Index: RELEASE-NOTES-4.0-B2.txt
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-B2.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- RELEASE-NOTES-4.0-B2.txt 2001/03/20 04:14:48 1.1
+++ RELEASE-NOTES-4.0-B2.txt 2001/03/24 01:23:21 1.2
@@ -3,7 +3,7 @@
Release Notes
=============
-$Id: RELEASE-NOTES-4.0-B2.txt,v 1.1 2001/03/20 04:14:48 craigmcc Exp $
+$Id: RELEASE-NOTES-4.0-B2.txt,v 1.2 2001/03/24 01:23:21 craigmcc Exp $
============
@@ -260,16 +260,9 @@
Previous versions of Tomcat 4.0 exposed the XML parser used by Jasper (the
JAXP/1.1 reference implementation) to web applications. This is no longer
the case, because Jasper loads its parser with a new class loader instead.
+Keep the following points in mind when considering how to use XML parsers
+in Tomcat 4.0 and your web applications:
-This change was primarily made to deal with "package sealing violation" errors
-caused by the fact that the "jaxp.jar" and "crimson.jar" files (supplied with
-the JAXP/1.1 release) are sealed. While this change appears to have eliminated
-sealing violation problems when running under JDK 1.2, problems have still been
-reported under JDK 1.3.
-
-Until a solution to this problem is implemented, keep the following
-information in mind with respect to XML parsers.
-
* If you wish to make the JAXP/1.1 RI XML parser available to all web
applications, simply move the "jaxp.jar" and "crimson.jar" files from
the "$TOMCAT_HOME/jasper" directory to the "$TOMCAT_HOME/lib" directory.
@@ -284,13 +277,16 @@
be able to utilize JSP pages in XML syntax (which requires a parser that
is compatible with JAXP/1.1) until Xerces completely implements this
specification.
-
-* If you wish to include an XML parser (such as Xerces) in the WEB-INF/lib
- directory of your web application, you may encounter "package sealing
- violation" errors under JDK 1.3. One solution would be to manually modify
- the JAXP JAR files (jaxp.jar and crimson.jar) so that they are not sealed
- (Remove the "sealed" line from META-INF/MANIFEST.MF and re-JAR the files).
- This is being considered as a permanent solution to the sealing problem,
- so feedback is requested about successful (or unsuccessful) attempts to
- use this approach.
+* If you wish to use an XML parser (such as Xerces) in the WEB-INF/lib
+ directory of your web application, this should now be possible, because
+ of the modified JAXP 1.1 parser mentioned below.
+
+WARNING: Tomcat 4.0 now ships with a modified version of the JAXP/1.1
+(Final) "jaxp.jar" and "crimson.jar" files in the "jasper" subdirectory.
+The "sealed" attribute has been removed from the manifest file for these
+two JARs, to avoid "package sealing violation" errors that were caused by
+them in a JDK 1.3 environment. You MUST NOT replace these files with a
+different (or later) release of JAXP, unless that later release has had
+the sealed attribute removed, or you will encounter "package sealing violation"
+errors when trying to use a different XML parser in a web application.
1.18 +5 -3 jakarta-tomcat-4.0/build.bat
Index: build.bat
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/build.bat,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- build.bat 2001/03/23 01:12:10 1.17
+++ build.bat 2001/03/24 01:23:21 1.18
@@ -45,7 +45,7 @@
rem The jar filename of the JAXP compliant XML parser
rem used for jasper [JAXP_PARSER_JAR]
rem
-rem $Id: build.bat,v 1.17 2001/03/23 01:12:10 craigmcc Exp $
+rem $Id: build.bat,v 1.18 2001/03/24 01:23:21 craigmcc Exp $
rem ---------------------------------------------------------------------------
@@ -89,11 +89,13 @@
if not "%JASPER_JAXP_HOME%" == "" goto gotJasperJaxpHome
if "%JAXP_HOME%" == "" goto jaxpHome
-set JASPER_JAXP_HOME=%JAXP_HOME%
+rem set JASPER_JAXP_HOME=%JAXP_HOME%
+set JASPER_JAXP_HOME=..\lib
:gotJasperJaxpHome
if not "%JASPER_JAXP_PARSER_JAR%" == "" goto gotJasperJaxpParserJar
-set JASPER_JAXP_PARSER_JAR=%JAXP_PARSER_JAR%
+rem set JASPER_JAXP_PARSER_JAR=%JAXP_PARSER_JAR%
+set JASPER_JAXP_PARSER_JAR=crimson.jar
:gotJasperJaxpParserJar
goto gotJaxpHome
1.13 +5 -3 jakarta-tomcat-4.0/build.sh
Index: build.sh
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/build.sh,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- build.sh 2001/03/23 01:12:10 1.12
+++ build.sh 2001/03/24 01:23:21 1.13
@@ -49,7 +49,7 @@
# The jar filename of the JAXP compliant XML parser
# used for jasper [$JAXP_PARSER_JAR]
#
-# $Id: build.sh,v 1.12 2001/03/23 01:12:10 craigmcc Exp $
+# $Id: build.sh,v 1.13 2001/03/24 01:23:21 craigmcc Exp $
# -----------------------------------------------------------------------------
@@ -98,7 +98,8 @@
fi
if [ "$JASPER_JAXP_HOME" = "" ] ; then
- JASPER_JAXP_HOME=$JAXP_HOME
+# JASPER_JAXP_HOME=$JAXP_HOME
+ JASPER_JAXP_HOME=../lib
fi
if [ "$CATALINA_JAXP_HOME" = "" -o "$JASPER_JAXP_HOME" = "" -o "$ANT_USING_DEFAULT"
= "true" -a "$JAXP_HOME" = "" ] ; then
@@ -120,7 +121,8 @@
fi
if [ "$JASPER_JAXP_PARSER_JAR" = "" ] ; then
- JASPER_JAXP_PARSER_JAR=$JAXP_PARSER_JAR
+# JASPER_JAXP_PARSER_JAR=$JAXP_PARSER_JAR
+ JASPER_JAXP_PARSER_JAR=crimson.jar
fi
if [ "$ANT_HOME" = "" ] ; then
1.1 jakarta-tomcat-4.0/lib/crimson.jar
<<Binary file>>
1.1 jakarta-tomcat-4.0/lib/jaxp.jar
<<Binary file>>
