Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
xmlParserAPIs.jar and parser.jar

xmlParserAPIs.jar and parser.jar

2003-08-28       - By Giana Marco
Reply:     1     2  

Hi all,

this is more a general Java question, but it is associated with Xerces.

I am currently writing library of classes to obviously process some XML
documents, using jdk1.3.1_01.

I have places the necessary jar files in jdk1.3.1_01\jre\lib\ext to be able
to compile and run.
The machines which will use this also contain parser.jar in this directory.
When I go to compile the classes I get the following error,

mapbroker/MBXML.java:97: cannot resolve symbol
symbol  : method createDocument  (java.lang.String,java.lang.String,<null>)
location: interface org.w3c.dom.DOMImplementation
       Document subDocument = domImpl.createDocument("", "roottagname",
null);

Now when I remove parser.jar, everything compiles and runs without a
problem.
This leads me to believe that cause both jar files contain the
org.w3c.dom.DOMImplementation, then the JVM cannot resolve which one to use.
Now I thought depending on which order these are loaded in the classpath,
then it will use the first. It seems to me placing the jars in \jre\lib\ext
does not do this. Well it is more of a case that I do not really understand
what happens to these files when java application starts.

So my question is how can I have both of these files in \jre\lib\ext and
have java resolve it.

Also this will be run as both for a stand alone application, which is where
I have encountered this problem, and as a web application.
using ServletExec. I have not done any test for the web application, but I
suppose I could add the xmlParserAPIs.jar
to the Java Virtual Machine (VM) Classpath, which should resolve this
problem for my web application.
Regards
Marco Giana



___________________________________________________________
Marco Giana
mailto:m.giana@(protected)
WebGIS-Entwicklung                                       Phone:++43 1 87806
ext. 49
SynerGIS Informationssysteme GmbH                   Fax:++43 1 87806 ext. 98
Amalienstrasse 65
A-1130 Wien
http://www.synergis.co.at
___________________________________________________________

18. European ESRI User Conference Oct 8-10, Innsbruck
10. Deutschsprachige ESRI Anwenderkonferenz 8.-10.10. Innsbruck
GIS @ Work http://www.esri2003.info


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)