See recent discussion of encodings. If the character you're generating is
directly supported by the encoding you specified in xsl:output, it should
be written out correctly. If it isn't, we *must* represent it as a numeric
character reference, or we'd be generating broken XML.
_
Hi,
I upgraded from Xalan2.1.0 to 2.4.1 and noticed one difference when
processing the same XML files through the same XSLT styles:
after transforming xml through 2.1.0 the resulting xml file has non-printing
characters represented as, for example, '\222'
processing the same file through 2.4.1 resu
Which version of Xalan are you using? I just looked at the code in
DTMNodeProxy.getChildNodes(). The older Xalan version throws a
DTMDOMException here. But it was now changed to do something meaningful.
You can try with the latest Xalan 2.4.1 release.
Morris Kwan
XSLT Development
IBM Toronto Lab
T
Hi Stefan,
I believe that's a known bug in recent IBM JDK's, but I'd encourage
you to report it to make sure the developers are aware of its impact on
users.
In fact, my understanding is that it's an internal error that
indicates the Just-in-Time Compiler in the JDK was able to compi
Hi,
it's bundled java with IBMs Websphere Application Developer 5 Trial Edidition.
C:\Programme\IBM\WebSphere Studio\runtimes\base_v5\java\bin>.\java.exe -version
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1)
Classic VM (build 1.3.1, J2RE 1.3.1 IBM Windows 32
I'm having some troubles using nodes, that are passes to my extension
function. My methods signature looks like this:
public static int method( NodeList nodes, String name )
The problem is that when I call getChildNodes() on the node in the passes
nodelist, the following exception occurs:
org.apa
