You are right. I tried it with the latest version in command line and it works fine. However, the strangest thing is, when I use XML SPY 4.3 to do the same thing, I got the problematic result. This is what I put in XML SPY tools menu -> options -> External XSL Program
java -classpath \xml-xalan\java\build\xalan.jar;\xml-xalan\java\bin\xercesImpl.jar;\xml-xalan\java\bin\xml-apis.jar org.apache.xalan.xslt.Process -IN %1 -XSL %3 -OUT %2 Perhaps it's some XML SPY problem. Thanks for your response. Guoliang Cao >Can't reproduce the problem. When I modify your stylesheet just slightly to >make comparing the two options easier: > > <xsl:template match="a"> > <xsl:param name="param1"/> > <first> > <xsl:apply-templates select="xalan:nodeset($param1)//b|b"/> > </first> > <second> > <xsl:apply-templates select="xalan:nodeset($param1)//b"/> > <xsl:apply-templates select="b"/> > </second> > </xsl:template> > >... and run it against the sample file you provided, I get identical >content for the <first> and <second> elements. > >I'm runnning current version of Xalan from CVS, so you may be seeing a bug >we've already found and fixed. >
