× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: failed to import xerces.jar
  • From: "David Morris" <dmorris@xxxxxxxxxxxxx>
  • Date: Thu, 09 Aug 2001 14:38:55 -0600

Rizwan,

I am using  Xerces 1.4 with VA/Java 3.5.3. I usually delete all of the w3c 
packages that 
IBM adds and go to the W3C CVS repository and update to the latest version.  I 
also 
blow away the org.apache.xerces and xalan packages that exist from IBM and go 
with 
the Apache versions.  I have had problems on occasion and as I recall I got a 
system 
error with Xerces 1.4 and VA/Java 3.5.2.

David Morris

>>> rizwan@nscsa.com.sa 08/07/01 11:50PM >>>
Hi

My VAJAVA is version 3.5 with WebSphere Tst Env & IBM Java Parsers included
to my workbench.I want to include the  Xerces.jar from the XML4J parser the
latest.

What I did was versioned the existing IBM java parsers and tried to import
the Xerces jar to my workbench.But I am not able to do so.It gives "System
Uncaught Exception".I think there is a conflict while adding org.w3.dom or
so.

I need to have  Xerces.jar and WebSphere Tst env to my workbench.

TIA

Thanks
Rizwan    



 

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.