Dear Sean,
> Any other ideas?
No solution, just some notes that may or may not help you in your quest.
Your problem is (as far as I can see) not that it cannot find Xerces 2.5
classes, but rather that it is mixing up classes loaded from Xerces
2.5.0 and an earlier version.
> invoke one of the methods on org.apache.xerces.impl.Version
> I also tried the other fellow's idea of printing the current
> version, it did come back as "2.5.0".
org.apache.xerces.impl.Version is only in there since Xerces 2, so if
your Xerces is older it will only find the 2.5.0 class and print that.
Perhaps you can also print
org.apache.xerces.framework.Version.fVersion
that would give you the other Xerces version, not that that is probably
that interesting.
> Is there any way to "force" an app. to use a specific
> version of Xerces or otherwise ensure it's only using
> code from the latest libs?
With your own classloader, but trust me you don't want to go there.
Instead you will want to ensure that your Xerces classes beat the other
Xerces classes, so that they don't get mixed up. A secondary goal is
then to do this elegantly....
I do not know how conforming JRun is to the servlet specs (or in fact
which version of the specs it uses). But the later specs say that
classes put in the lib of the servlet (WEB-INF/lib?) should always
override all other classes except for the classes in default packages.
So since you use JDK 1.2 in which XML parser classes are not yet default
packages, what should work is putting xercesImpl.jar and xml-apis.jar in
the servlet directory.
But from my experience with other servlet engines (Tomcat), apparently
this is very hard to implement correctly, so that may not work. In that
case you should look on the web first, e.g.
http://archives.real-time.com/pipermail/cocoon-users/2001-July/017144.ht
ml
Kind regards,
--Sander.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
