This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: [docbook-apps] Xalan, Resolver classes, ~/lib/endorsed, default version org.apache.xalan.xslt.Process ?, override it? URIResolver class not found
- From: "Bob Stayton" <bobs at sagehill dot net>
- To: <swhitlat at getnet dot net>, <docbook-apps at lists dot oasis-open dot org>
- Date: Sat, 10 Jan 2004 22:35:50 -0800
- Subject: Re: [docbook-apps] Xalan, Resolver classes, ~/lib/endorsed, default version org.apache.xalan.xslt.Process ?, override it? URIResolver class not found
- References: <200401102227.12562.swhitlat@getnet.net>
Putting the xalan.jar file in the endorsed directory should have worked.
You might try this java command option to explicitly tell java
about the new xalan:
java -Djava.endorsed.dirs="../xalan251/bin"
org.apache.xalan.xslt.Process -V
where the path is to the directory on your system that contains the
xalan.jar file.
Bob Stayton
Sagehill Enterprises
bobs@sagehill.net
----- Original Message -----
From: "Steve Whitlatch" <swhitlat@getnet.net>
To: <docbook-apps@lists.oasis-open.org>
Sent: Saturday, January 10, 2004 9:27 PM
Subject: [docbook-apps] Xalan, Resolver classes, ~/lib/endorsed, default
version org.apache.xalan.xslt.Process ?, override it? URIResolver class not
found
> I just downloaded and installed Xalan Java version 2.5.2, but for some
> reason Java always uses Xalan version 2.4.1.
>
> %java org.apache.xalan.processor.XSLProcessorVersion
> Xalan Java 2.4.1
>
> That's bad because Xalan Java version 2.4.1 is known to have problems
> accessing the Resolver classes, which is the reason I upgraded Xalan.
>
> I'm trying to get Xalan Java to use either the Sun Resolver classes or
> the Apache Resolver classes, doesn't matter which. Saxon finds both
> and uses either with no trouble. But Xalan Java always issues the
> same error message:
> Class file not found for option -URIResolver
>
> I think this is the problem described in the bug report at:
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17030
> I see that bug report's STATUS=RESOLVED and the RESOLUTION=FIXED and
> the bug report has been marked as CLOSED. Trusting that this bug has
> actually been fixed, it would seem that if I were using an Xalan
> version > 2.4.1, then this bug would not be biting me. But it seems I
> cannot get java to use anything but the 2.4.1 version of Xalan.
>
> If I read the bug report correctly, the cause of Xalan not being able
> to load the Resolver classes was that Sun included an older version
> of Xalan (version 2.4.1) in the jre's ~/lib/endorsed directory. So, I
> downloaded Xalan Java 2.5.2, replaced the version in ~/lib/endorsed
> with the new one, put a copy version of xalan.jar version 2.5.2 in /
> usr/local/j2ee_1.4/jdk/jre/lib/ext/, and even put another copy of
> xalan.jar version 2.5.2 in my personal bin directory and included it
> in my CLASSPATH. So, the new 2.5.2 version should have replaced the
> 2.4.1 version. Correct? Nope, not yet.
>
> No matter what xalan.jar file I try to use, java uses a 2.4.1 version,
> the whereabouts of which I have not yet determined.
>
> %java org.apache.xalan.processor.XSLProcessorVersion
> Xalan Java 2.4.1
>
> And that's with all those Xalan Java 2.5.2 versions I just installed.
>
> I can do "locate xalan.jar" to find all files with that name anywhere
> on this computer. I did and replaced those that appeared to possibly
> be used by the JVM. Still, it is all 2.4.1.
>
> java org.apache.xalan.xslt.Process -V
> >>>>>>> Xalan Version Xalan Java 2.4.1, <<<<<<<
>
> %java -version
> java version "1.4.2_02"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)
>
> Please advise if you can.
>
> Thanks,
>
> Steve Whitlatch
>
>
>
>
> To unsubscribe from this list, send a post to
docbook-apps-unsubscribe@lists.oasis-open.org, or visit
http://www.oasis-open.org/mlmanage/.
>
>
To unsubscribe from this list, send a post to docbook-apps-unsubscribe@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/.