Moving & Cloning subtrees (Parser V2)

Question

I have noticed some bugs(?) in the XSLProcessor that have been
causing me some minor headaches.
I have a test harness for my XSL stylesheet that takes an XML
document and the stylesheet as arguments. This works fine. In my
application however, the XML document is constructed from a
number of different sources including other XML documents.
Anyway, the following XSL will return null if the FOO branch is
copied from another document.
given:
<FOO>hello
<BAR/></FOO>
and:
<xsl:template match="FOO">
<xsl:value-of select="BAR/.."/>
</xsl:template>
It would appear to me that the cloneNode(true) method forgets to
set the parent references.
I have managed to get around this problem so far by adding
attributes to the child so I don't have to reference the
parent...but this is not very neat.
If I am just missing something really basic, please let me know,
otherwise I think it is a bug.
Grant Jennings
null

Answer 1

Oracle XML Team wrote:
: Grant Jennings (guest) wrote:
: : I have noticed some bugs(?) in the XSLProcessor that have
been
: : causing me some minor headaches.
: : I have a test harness for my XSL stylesheet that takes an XML
: : document and the stylesheet as arguments. This works fine. In
: my
: : application however, the XML document is constructed from a
: : number of different sources including other XML documents.
: : Anyway, the following XSL will return null if the FOO branch
: is
: : copied from another document.
: : given:
: : <FOO>hello
: : <BAR/></FOO>
: : and:
: : <xsl:template match="FOO">
: : <xsl:value-of select="BAR/.."/>
: : </xsl:template>
: : It would appear to me that the cloneNode(true) method forgets
: to
: : set the parent references.
: : I have managed to get around this problem so far by adding
: : attributes to the child so I don't have to reference the
: : parent...but this is not very neat.
: : If I am just missing something really basic, please let me
: know,
: : otherwise I think it is a bug.
: : Grant Jennings
: Could you please provide a Java test case which reproduces the
: problem?
I was getting the correct result when I ran it in the test
harness, but incorrect results in my application. The XML was
identical, the only difference was that construction of the tree
in the application was done piecemeal, whereas the test harness
just parsed a saved version of the doc.
The latest version seems to fix the problem though. Thanks.
null