[ http://issues.apache.org/jira/browse/XALANJ-1742?page=comments#action_12356522 ]
Henry Zongaro commented on XALANJ-1742: --------------------------------------- For any interested users, the work-around for this problem is to place global variables and parameters in the stylesheet in the order in which they need to be evaluated. That is, if a variable B depends upon the value of a variable A, place the xsl:variable element for A before the xsl:variable element for B in the stylesheet. That doesn't solve the problem with variables that have a potential for mutual reference that is only decided at run-time, but I hope that nobody will ever actually run into that problem. > Order of global variable and param affect the output > ---------------------------------------------------- > > Key: XALANJ-1742 > URL: http://issues.apache.org/jira/browse/XALANJ-1742 > Project: XalanJ2 > Type: Bug > Components: XSLTC > Versions: 2.6 > Environment: Operating System: All > Platform: All > Reporter: Joanne Tong > Assignee: Xalan Developers Mailing List > Priority: Critical > Attachments: d25344b.xml, d25344b.xsl, d25344c.xml, testcase_bug_25344.txt > > When a global variable/param references another global variable/param, the > order that the processor translates the global elements affects the output. > This is evident in the testcase variable31.xsl if you reverse the order of > the > global variable and param. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
