[jdom-interest] RE:Weblogic60:swapping Jdom specific code out for JAXP

[Mark Scott]

Hi,
     I've called the builder with the JAXP SAX parser classname
as you suggested, I now get this mesg..

java.io.IOException: Problems occurred:SAX2 driver class
javax.xml.parsers.SAXParserFactory loaded but cannot be instantiated (no
empty public constructor?)

Consequently, I see in the build method that it checks for JAXP first
anyway, so I'll use it as is, but am still interested in what this mesg is
pointing to..

thanks for your efforts...

Mark


>Parsers in JDOM have always been pluggable.  See the builder
>constructors.  In the latest daily snapshot we can use JAXP also.

>-jh-



Mark Scott wrote:
>
> Hi,
>   I'm running the code from "Validation using Jdom & XML Schema"
example...
> In which the shema attributes get mapped to constraint objects, by the
> schema parser
> I have a problem with it in weblogic 6, so to remedy the issues I'd like
to
> swap out
> the JDOM parser for either a xerces specific one or using JAXP, any
thoughts
> or help
> is appreciated...






M. Scott
msmail at postmark.net

-----Original Message-----
From: Jason Hunter [mailto:jhunter at collab.net]
Sent: Monday, February 12, 2001 9:28 PM
To: Mark Scott
Cc: jdom-interest at jdom.org
Subject: Re: [jdom-interest] RE:Weblogic60:swapping Jdom specific code
out for JAXP


Mark Scott wrote:
>
> Hi,
>   I'm running the code from "Validation using Jdom & XML Schema"
example...
> In which the shema attributes get mapped to constraint objects, by the
> schema parser
> I have a problem with it in weblogic 6, so to remedy the issues I'd like
to
> swap out
> the JDOM parser for either a xerces specific one or using JAXP, any
thoughts
> or help
> is appreciated...

Parsers in JDOM have always been pluggable.  See the builder
constructors.  In the latest daily snapshot we can use JAXP also.

-jh-