RE: Problem on: Cascading xslts on browsers

        > >     data.xml -> stage1.xsl -> stage2.xsl

        Mmh.. so, anyway, if the xslt engines don't have to do that,
        i'm forced to use some kind of include mechanism, i think.. right?
        or is it supposed that i dont ever try to do things like that!


The following works on ie6

<script>

// Set up the resulting document.
var result = new ActiveXObject("Msxml2.DOMDocument");
result.async = false
result.validateOnParse = true;

// Set up the resulting document.
var finalresult = new ActiveXObject("Msxml2.DOMDocument");
finalresult.async = false
finalresult.validateOnParse = true;

// Set up the Data document.
var Data = new ActiveXObject("Msxml2.DOMDocument");
Data.async = false
Data.validateOnParse = true;

// Set up the First XSL document.
var Stage1 = new ActiveXObject("Msxml2.DOMDocument");
Stage1.async = false
Stage1.validateOnParse = true;

// Set up the Second XSL document.
var Stage2 = new ActiveXObject("Msxml2.DOMDocument");
Stage2.async = false
Stage2.validateOnParse = true;

Data.load(Data.xml);
Stage1.load(Stage1.xsl);
Stage2.load(Stage2.xsl);

Data.transformNodeToObject(Stage1, result);
result.transformNodeToObject(Stage2, finalresult);
</script>

finalresult will be the result of both transforms...


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list