Hani,
Looks like Jim Carroll's post on March 21, I was able to get crimson
rolling.
Here's how (its ugly but it works):
delete parser.jar
delete jaxp.jar
get the latest distribution of xalan. This should have xerces.jar for 1.30.
Replace the xalan.jar and xerces.jar with the latest files from xalan.
Copy the latest crimson.jar into orion/lib directory.
Copy the jaxp.jar from the crimson distribution into the orion directory.
restart orion.
Crimson now works. I haven't tried xalan...but we don't use xalan because
its so slow. We are using crimson with jdom to do our xml conversions, since
its so much faster than xalan.
Regards,
The elephantwalker
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hani Suleiman
Sent: Sunday, April 08, 2001 6:40 AM
To: Orion-Interest
Subject: Re: how to get crimson working?
Orion 1.4.8 will take care of that, I am told.
On Sun, 8 Apr 2001, elephantwalker wrote:
> Looks like this is a little problem.
>
> I know that there are several xml parser problems with orion. I want to
use
> crimson (the latest Jan 30 version) on orion because the sax 2 parser is
> about 4 times faster than xerces.
>
> The class clash problem with the sax 1 implementations used by orion will
> always clash with a sax 2 parser. This usually manifests itself with a
> "method not found" error. Has anybody gotten the latest crimson to run
with
> orion?
>
> What class paths are necessary for orion to run, so I can front-end my
> parser jar's before the offending sax 1 jar's?
>
> And to the orion developers...please use the latest jaxp to abstract the
> parser calls, and please upgrade to sax 2. Sax 1/Dom 1 are almost dead
now,
> so its time to upgrade.
>
> regards,
>
> The elephantwalker
>
>
>
>
>
>
