I haven't tried Process (ever), our calls have always been through the API. I'd try Process with multiple threads to see if I could get the same output, but its not thread friendly.
You might be right about feeding the processor something incorrect - I wonder if the real problem is in the generation of the Document object, but I just don't notice it until its been transformed. Anyone know if Xalan would accept a document structure that had xml declrations in node attribute values?
Also: I didn't want to list *all* my problems, but I actually have some other issues, such as this (also rare / hard to reproduce):
Could not load output_text.properties (check CLASSPATH), now using just the defaults
which upon examination of the loadPropertiesFile() method implies a classloader issue of some sort. Maybe my environment is just too buggy/unstable to get anything reliable out of..
Thanks, Alex
Joseph Kesselman wrote:
Tried running these sample fragments from the command line, and I get the output
That looks like appropriate results for the fragments you supplied, and doesn't demonstrate the failure.
Did you try running these via org.apache.xalan.xslt.Process on your own
system and get the failure, or is it only happening when Xalan is being
called through the API? If the latter, it's time to look at how the API is
being invoked to see if there's some subtlety of configuration that causes
us to fail, and/or whether what you think you're feeding into the
processor matches what it's actually receiving.
______________________________________ Joe Kesselman / IBM Research
