RE: [xsl] Transforming using Javascript's documentElement

Subject: RE: [xsl] Transforming using Javascript's documentElement
From: "Chris Bayes" <Chris@xxxxxxxxxxx>
Date: Thu, 12 Jul 2001 10:47:21 +0100
You need to set fXSL.async = false;

Ciao Chris

XML/XSL Portal

>-----Original Message-----
>From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>[mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Rosa I-Ting
>Sent: 12 July 2001 05:16
>To: 'xsl-list@xxxxxxxxxxxxxxxxxxxxxx'
>Subject: [xsl] Transforming using Javascript's documentElement
>I'm not sure if this has been asked before... but can anyone please tell me
>why sometimes fXML.documentElement returns a null and sometimes it doesn't?
>this is the javascript code I have:
>	function writeToPage(xsl1, xsl2)
>	{
>		qXML.load(qXML.src);
>		fXSL.load(xsl1);
>cumentElement always have problems
>		fXSL.load(xsl2);
>		mainBody.document.close();
>	}
><xml id="qXML" src="TotalQuotesPolicies.xml"></xml>
><xml id="gpXML"></xml>
><xml id="fXSL"></xml>
>I'm trying to transform the XML twice with 2 different XSLs. And when I
>directly put in the
><?xml-stylesheet type="text/xsl" href="saBySALogin2.xsl"?>
>line in the XML, the transformation works fine, but when trying to use that
>javascrit code above, at times it works and at times it doesn't. I know it
>is due to the fXML.documentElement return null and the
>transformNodeToObject() and the transformNode() returns an error when that
>happens... is there a way around it? or a substitute for the
>documentElement? or am I doing something wrong?
>thank you!
> XSL-List info and archive:

 XSL-List info and archive:

Current Thread