xsl-list
[Top] [All Lists]

Re: root node template - unmatching pattern?

2004-11-24 03:36:51
Trying to solve the issue, I discovered a strange, odd behavior:
A) calling the transformNodeToObject method of the IXMLDOMElement interface
(as I've done till now, for example:
Call xmlDoc.documentElement.transformNodeToObject(xslDoc, resultDoc)
) resulted in an undesired unmatching of the root-node template (xpath="/");
B) on the other hand, calling the "same" transformNodeToObject method of the
DOMDocument40 class (for example:
Call xmlDoc.transformNodeToObject(xslDoc, resultDoc)
) I got my wanted result (the root-node template matching).

Can someone explain me if either exists a DOM-specification difference
between the behavior of the two methods or it's just one of the sadly famous
non-conformance of the MSXML implementation?

Thanks

Stefano

-----Messaggio originale-----
Da:   Chizzolini Stefano [SMTP:chist(_at_)csb(_dot_)it]
Inviato:      mercoledì 24 novembre 2004 9.29
A:    xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Oggetto:      [xsl] R: [xsl] root node template - unmatching pattern?

-----Messaggio originale-----
Da: David Carlisle [SMTP:davidc(_at_)nag(_dot_)co(_dot_)uk]
Inviato:    martedì 23 novembre 2004 18.16
A:  xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Oggetto:    Re: [xsl] root node template - unmatching pattern?

[...]

Your stylesheet will produce
<test>Correctly matched!</test>
given any input.

If yo are not getting output then presumably something is wrong with the
way you are calling the processor.

More precisely: I'm getting *just* the default templates output (I say:
the
text content).
Testing the responsiveness of the processor, then I added this usual
element
to my stylesheet in order to override the default behavior and exclude the
text output:

<xsl:template match="text()"/>

As expected, no text content resulted from the processing, but neither I
achieved my goal to render the root node template content!

Regarding the way I call the processor, this is my relevant code (after
the
simple loading of the engaged documents):

Call xmlDoc.documentElement.transformNodeToObject(xslDoc, resultDoc)

Absurd?
Any suggestion?

Thanks again

Stefano

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--