cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Maring <Steven.Mar...@trcinc.com>
Subject need help managing multiple parsers
Date Fri, 31 Mar 2000 20:24:59 GMT
I am running into alot of problems trying to manage the usage of different
parsers.  Ant and Tomcat seem to favor Sun's jaxp1.0 parser and Cocoon seems
to favor the Xerces parser, but also has some need for Sun's.  And then I
have other third party stuff that uses an older version of IBM's XML4J.

The problem comes about since ever parser includes the pieces of the DOM
specification that they are implementing.

Xerces seems to include DOM2 and DOM1 stuff so I figured I would be safe by
always making sure Xerces was in the classpath first.

I find it easier to manage all the required packages by putting symbolic
links to everything inside $JAVA_HOME/jre/lib/ext

Here is what I have so far:
ant.jar -> /usr/local/jakarta/jakarta-ant/lib/ant.jar
cocoon.jar -> /usr/local/cocoon-1.7.1/build/cocoon.jar
fop.jar -> /usr/local/fop-0_12_1/fop_bin_0_12_1.jar
servlet.jar -> /usr/local/servlet-2_2/servlet.jar
tools.jar -> /usr/local/jdk1.2.2/lib/tools.jar
xalan.jar -> /usr/local/xalan_1_0_0/xalan.jar
xerces.jar -> /usr/local/xerces-1_0_3/xerces.jar
xml.jar -> /usr/local/jaxp1.0/parser.jar
xml4j.jar -> /usr/local/xml4j2.0.14/xml4j.jar


With that, here is a build error I am getting with Cocoon:
# javac -deprecation
/usr/local/cocoon-1.7.2/build/src/org/apache/cocoon/parser/SunXMLParser.java

/usr/local/cocoon-1.7.2/build/src/org/apache/cocoon/parser/SunXMLParser.java
:24: Note: interface org.xml.sax.Parser has been deprecated.
      	org.xml.sax.Parser parser;
      	           ^

Anybody see the problem or have a nice trick for dealing with all these
different parsers at once?

Is the classloading of $JAVA_HOME/jre/lib/ext not sequential?


-Steve Maring

Mime
View raw message