Um, "everything that Gary said". Good suggestions.
Also:
-- What specific distribution of Xalan are you using? One of the most
obvious things that helps us debug problems is knowing which version of the
product you're using, and what OS and JVM you're on.
-- I also would be *quite* surprised if any of our posted builds had
compile/build problems like mismatched .class/.java files! More likely
it's either some wierd use of reflection (i.e. it could still have compiled
because someone does a Class.forName() of an outdated string) or outdated
classes/jars in your local environment.
A grep for the 'old' classname on current xml-xalan/java/**/*.java doesn't
show it
- Shane
> Johannes Eggers wrote:
>
> Hi all,
>
> I'm new to this list and Xalan, and I don't like to start off
> negative, but these types of issues are very frustrating (and don't
> say a lot for the quality of open source).
>
> Anyhow... something in Xalan 2 seems to refer to (or
> throw) org.apache.xalan.utils.WrappedRuntimeException, but that class
> isn't shipped in the xalan jar, instead it has
> org.apache.xml.utils.WrappedRuntimeException
>
> I'm baffled how this could have ever compiled/built without having had
> old classes or source in the classpath, and if that is the case then
> the way production-builds are being made needs to be revisited.
>
> If I'm missing the obvious, I will take the flames lying down like a
> man !
>
> Thanks,
>
> Johannes
>
> ============================================
> Johannes Eggers The Structure Group
> 2000 W. Sam Houston Parkway, Houston, TX 77042
> www.scgo.com Ph: (713) 243-7194 Fax: (713) 243-7199
