[Mono-bugs] [Bug 69952][Nor] New - Xsl:param values declared inside xsl:template do not keep the values assigned to them by XslTransform

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 26 Nov 2004 21:29:47 -0500 (EST)


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by ariel@gnu.org.

http://bugzilla.ximian.com/show_bug.cgi?id=69952

--- shadow/69952	2004-11-26 21:29:47.000000000 -0500
+++ shadow/69952.tmp.31997	2004-11-26 21:29:47.000000000 -0500
@@ -0,0 +1,39 @@
+Bug#: 69952
+Product: Mono: Class Libraries
+Version: 1.0
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Sys.XML
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: ariel@gnu.org               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Xsl:param values declared inside xsl:template do not keep the values assigned to them by XslTransform
+
+In DotNet xsl:param variables can be defined inside templates keeping the
+value passed from C# via XslTransform. It looks like although
+xslt specs require them to be declared as a child of xsl:template,
+Microsoft accepts the former behaviour.
+
+in xsl file:
+ <xsl:template match="Reporte">
+	<xsl:param name="pag" />
+	<xsl:param name="modoAccion" />
+
+in cs file:
+  modoAccion="INICIAL";
+  XsltArgumentList xslArg = new XsltArgumentList();
+  xslArg.AddParam("modoAccion", "", modoAccion);
+  xslt.Transform(doc1, xslArg,Response.OutputStream , null);
+
+
+Doing the following test 'yes' is printed when I expect
+modoAccion's value to be different from ''.
+
+	<xsl:if test="$modoAccion=''">yes</xsl:if>