DO NOT REPLY [Bug 7603] New: - XSLT not reporting error when a template rule's match attribute has a variable in it

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7603>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7603

XSLT not reporting error when a template rule's match attribute has a variable in it

           Summary: XSLT not reporting error when a template rule's match
                    attribute has a variable in it
           Product: XalanJ2
           Version: 2.3
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Xalan
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: gary.frederick@jsoft.com


The template rule 
  <xsl:template match="item[position() mod $thisnup = 1]">
should generate an error because the match attribute has a variable in it.
  http://www.w3.org/TR/xslt#section-Defining-Template-Rules

I like that it does not generate an error. The variable can be resolved at
runtime and the match's expression with the variable gives me a way to generate
different results, based on the value at runtime.

But it is not correct...

I reported this to the mozilla folks
  http://bugzilla.mozilla.org/show_bug.cgi?id=134013
there are test cases there

Gary