xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nathaniel.D...@wdr.com
Subject bugs w/ Xerces.jar from Xalan and IBM ZIPs
Date Mon, 03 Apr 2000 23:34:14 GMT
     (Maybe this should go to alphaworks instead)
     
     Xalan has mostly worked fine for me when used with the Xerces.jar 
     supplied in the Xalan download.
     
     However, I already had the Xerces.jar from the IBM XML4J 3.0 download. 
     These two xerces.jar's are not the same!  I ran into runtime 
     ClassNotFound errors when the CLASSPATH had the IBM Xerces.jar:
     My Xalan application was looking for the class : 
     
     org.xml.sax.ext.LexicalHandler
     
     This class was present in the Xerces.jar from IBM, but under:
     
     org.xml.sax.LexicalHandler
     
     
     So the problem is with the SAX libs in the jars.  I don't know who is 
     right.  In SAX 2.0 a bunch of the old handlers are deprecated, though 
     LexicalHandler is still around.  I am thinking that the /ext/ folder 
     has gone away and that LexicalHandler now belongs simply in the SAX 
     directory.  
     
     (I also tried to download the Xerces.jar from the plain Xerces 1.0.3 
     download, but that jar is corrupt or something, because JBuilder 
     crashes when I try and register it as a library.  I must admit I 
     haven't looked into this at depth...)


This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.


Mime
View raw message