[jdom-interest] AW: jdom-interest digest, Vol 1 #1264 - 4 msgs

[lanikfs at cox.net]

Thanks Christian.  I'm using JDK 1.3.1_02 - the default with JDeveloper.  I gave it a shot, but unfortunately, no go.
Perhaps, if nothing else, I'll download the latest JDK and see if that makes a difference.  I'll try anything at this point.

From: "Christian Peter" <cpeter at rostock.igd.fhg.de>
Date: 2003/07/11 Fri AM 02:43:01 EDT
To: <jdom-interest at jdom.org>
Subject: [jdom-interest] AW: jdom-interest digest, Vol 1 #1264 - 4 msgs

Hi,

which JDK are you using? Maybe your problem is that the standard parser
since (I think) jdk 1.4 is Crimson. Since Crimson starts with 'C' and Xerces
with 'X', the Crimson parser will be loaded per default and will always
offer its services, not allowing other parsers to do so. To avoid this,
rename Crimson to, say, Zcrimson, and Xerces should be found.

HTH,

Christian

--
From: <lanikfs at cox.net>
To: jdom-interest at jdom.org
Subject: Re: [jdom-interest] Error validating schema - can't find xerces
parser
Date: Thu, 10 Jul 2003 11:21:16 -0400

Thanks John and Sanjeev.

I have confirmed that the parser class is indeed in the classpath.  I even
tried explicitly including the class-file in the .jar file that the
application was deployed to.  I've made sure that there is no other instance
of the class in the classpath.

I've seen before where the compiler won't pull in a class if it's not
explicitly instantiated somewhere in the code - which I've made sure to do
and that compiles and runs just fine.  Therefore, I've confirmed that at
least the compiler and runtime can find it that way.  It seems it's only the
SAXBuilder and something about the way it's looking up the class.

From: John Jefferson <surfer97301 at yahoo.com>
Date: 2003/07/09 Wed PM 08:53:52 EDT
To: lanikfs at cox.net,  jdom-interest at jdom.org
Subject: Re: [jdom-interest] Error validating schema - can't find xerces
parser


I am not familar with Oracle JDeveloper but it sounds
like the xerces jar is not in your classpath at
runtime or perhaps you have multiple
org.apache.xerces.parsers.SAXParser classes in your
classpath and an older invalid one is obsuring the
relevant one.


--- lanikfs at cox.net wrote:
> I'll probably kick myself once I find out what I'm
> doing wrong but I need some help.
>
> I'm using JDOM to validate against a schema and I'm
> specifying the xerces parser in the SAXBuilder
> constructor.
>
> I have the latest xerces lib.  I'm using Oracle
> JDeveloper and am including it in the library list.
>
> At runtime, when the SAXBuilder constructor is
> called, I keep getting an error message saying:
>
> Could not load org.apache.xerces.parsers.SAXParser:
> SAX2 driver class
> org.apache.xerces.parsers.SAXParser not found:
> org.apache.xerces.parsers.SAXParser
>
> Is there something I'm missing?  Has anyone else run
> into this problem before?
>
> _______________________________________________
> To control your jdom-interest membership:
>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com



_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com