It performs well enough to saturate our I/O channels for mass ETL type
work. :o)
David Johnson
Programmer Specialist
J. B. Hunt Transport
Information Services / GAR New Dev
[EMAIL PROTECTED]
I would like to talk with someone who is responsible for maintaining the
source repository and learn some of the issues and practices that make it
possible to function as an open-source repository administrator.
Thanks,
David Johnson
Programmer Specialist
J. B. Hunt Transport
Information Service
Xalan version: 2.6.2
When I transform a document, I want to be able to make the transformation
reversible. I am having issues with the namespaces that are in the
original document.
Since this transformation is specifically targeted at XML generated by
Excel workbooks, the XML namespaces are con
I think I identified the core of the problem:
DOM2SAX.parse is failing on
The problem is exposed in this snippet:
case Node.TEXT_NODE:
final String data = node.getNodeValue();
_sax.characters(data.toCharArray(), 0, data.length());
break;
getNodeValue()
... nevertheless, when I prepended the jar files to bootclasspath, it
worked.
Problem resolved.
Thanks
David Johnson
Programmer Analyst
J. B. Hunt Transport
Information Services / OPR New Dev
[EMAIL
I have also confirmed that I am running the correct version of xalan by
debugging into the xalan 2.6.0 source code.
David Johnson
Programmer Analyst
J. B. Hunt Transport
Information Services / OPR New Dev
Thanks for the response. We are using the "endorsed standards" mechanism
to override this. The log indicates that we are using the correct xalan
version.
>From the configuration code:
log.info( "JVM:\t" + System.getProperty("java.vm.vendor") +
" " + System.getPr
Situation:
I have a set of XSLT scripts that function correctly under
interpreted xalan. I am trying to test the performance benefit of shifting
to the TRAX compiler. We are running three successive transformations
(one to produce outbound data, two to take inbound data and convert it
I a similar symptom recently when the file said it was in UTF-8 but a
non-compliant XML parser only supported ISO-8859-1. Make sure that your
character set encoding is correcton both sides.
David Johnson
Programmer Analyst
J. B. Hunt Transport
Information Services / OPR New Dev
