>I was under the same impression but the error only occurs when the >new version of Xalan is added to my class path.
Hmmm. It's possible that we're invoking Xerces slightly differently than we used to, I suppose, but I'm still surprised. Xalan per se really doesn't and shouldn't get involved with that sort of detail. Time to reproduce it in the lab... ______________________________________ Joe Kesselman / IBM Research
