[Home] [By Thread] [By Date] [Recent Entries]
An XML name cannot begin with ".". So after
number(. the only things that can legally come next are either ")", or an operator such as "+", "div", or "/". It's not a good message. Sometimes when you get a poor error message, it's worth trying another XSLT processor to see if it gives you a better one. Saxon on this one gives you: Error at xsl:when on line 24 column 67 of test.xsl: XPST0003 XPath syntax error at char 9 on line 24 in {(number(.DisplayPrice)}: expected ")", found name "DisplayPrice" The "expected ')'" when there are many other symbols that could occur is symptomatic of a top-down parser, which typically only reports what it was expecting as a 'last resort'. A bottom-up parser that builds a finite-state machine would know all the possible symbols that could validly occur in this context. Michael Kay Saxonica On 29/09/2011 21:28, aellath wrote: Hello! i wish i could tell you versions, etc., but i am modifying code for a webstore my boss is opening, and everything goes through IAModules. i'm not even allowed to see the .jsp files they're using, much less tinker with *them*. all store inventory data is xml, and the jsps wrap html around various xsl files, pulling data from the xml files.
|

Cart



