I've got to say I don't quite follow this.
Unless you are *recompiling* tomcat from source,
then I don't see what build.xml and build.bat have
to do with anything.
I upgraded from tomcat3.1 to tomcat3.2 without any
issues at all - just removed the old directory, and
unzipped the new distribution. All worked ok.
I am aware that tomcat3.1 used to "hard-wire" a particular
xml parser (see Craig's comment earlier this week). Versions
of tomcat 3.2 and later allow any JAXP-compliant parser
to be used instead.
I'm pretty sure, though, that tomcat3.2 and later still include
a JAXP-compliant xml parser with the standard download.
All I can think of is that you have a CLASSPATH set up
so that a non-compliant parser implementation happens
to be found first. Look really carefully at the CLASSPATH,
and try to remove as much of the non-essentials as possible.
I use a script to start tomcat, which includes:
# run tomcat
JAVA_HOME=/opt/java1.2; export JAVA_HOME
CLASSPATH=; export CLASSPATH
TOMCAT_HOME=/home/ola3dev/jakarta-tomcat; export TOMCAT_HOME
P1="-Dinstance=/home/ola3dev/webserver"
P2="-Djava.security.manager=default"
P3="-Djava.security.policy=file:/home/ola3dev/webserver/ola3.policy"
TOMCAT_OPTS="$P1 $P2 $P3"; export TOMCAT_OPTS
nohup $TOMCAT_HOME/bin/tomcat.sh start -f
/home/ola3dev/webserver/tomcat/conf/server.xml
You note that CLASSPATH is set to be completely **empty**, and tomcat starts
ok.
Regards,
Simon
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, December 20, 2000 6:11 PM
> To: [EMAIL PROTECTED]
> Subject: Re: how to "upgrade" to 3.2.1 from 3.1beta
>
>
>
> I spent a lot of hours on this, I feel I can save you some.
>
> The build.xml and build.bat under your application's root directory need
> to be
> upgraded as well. Look for the default ones come with tomcat 3.2.1 under
> conf
> directory and compare with your old ones. You should be able to see the
> difference.
>
> Ma, Yanbin
>
>
>
> |--------+----------------------->
> | | "Harding, |
> | | David" |
> | | <dharding@Tho|
> | | mcomp.com> |
> | | |
> | | 12/20/00 |
> | | 11:47 AM |
> | | Please |
> | | respond to |
> | | tomcat-user |
> | | |
> |--------+----------------------->
>
> >-------------------------------------------------------------------------
> --|
> |
> |
> | To: [EMAIL PROTECTED]
> |
> | cc: (bcc: Yanbin Ma/SYS/NYTIMES)
> |
> | Subject: how to "upgrade" to 3.2.1 from 3.1beta
> |
>
> >-------------------------------------------------------------------------
> --|
>
>
>
> i had tomcat 3.1 beta running with no problems.
>
> i downloaded jakarta-tomcat-3.2.1.tar.gz from the tomcat website
> and gunzip'd and untar'd it. i copied my original tomcat installation
> directory to another location and then put the new 3.2.1 contents in its
> place.
>
> what else would have to be done assuming that i am only running very
> simplistic servlets (lets say it is just a HelloWorld)? i get an error
> when
> i try to build and deploy my webapp with a HelloWorld JSP file in it.
>
> anybody know why? of course more info can be given if someone requests
> it.
>
> the class that it says it cannot find does not appear to be on my system,
> however it was not there before either. did the XML parsing stuff change
> between 3.1 and 3.2.1? if so, where can i get the new XML parsing
> classes?
>
> thanks in advance...i am looking forward to the performance increase and
> built in security features of 3.2.1
>
> my error message:
>
> No JAXP compliant XML parser found. See http://java.sun.com/xml for the
> reference implementation.
> java.lang.ClassNotFoundException: javax.xml.parsers.SAXParserFactory
> at java.net.URLClassLoader$1.run(URLClassLoader.java, Compiled
> Code)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java, Compiled
> Code)
> at java.lang.ClassLoader.loadClass(ClassLoader.java, Compiled
> Code)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java,
> Compiled Code)
> at java.lang.ClassLoader.loadClass(ClassLoader.java, Compiled
> Code)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java, Compiled Code)
> at org.apache.tools.ant.Main.runBuild(Main.java, Compiled Code)
> at org.apache.tools.ant.Main.main(Main.java, Compiled Code)
>
>
>
>
>
>
