Gary Larsen napisał(a): > Hi, > > >> net.sf.saxon.trans.DynamicError: Ambiguous rule match for >> > > I just changed to Saxon and ran into this. My fix (it seems to work) was to > change the "fi:styling/@*" template to: > > <xsl:template match="fi:styling/@*[not(local-name()='type')]" > mode="styling"> > <xsl:copy-of select="."/> > </xsl:template> > > According to spec: "It is an error if this leaves more than one matching template rule. An XSLT processor may signal the error; if it does not signal the error, it must recover by choosing, from amongst the matching template rules that are left, the one that occurs last in the stylesheet." [1] That means Saxon behaves correctly choosing way of throwing error instead of recovering mechanism.
I think it's better to raise priority of one template than constructing clunky matches. What do you think? [1] http://www.w3.org/TR/xslt#conflict -- Grzegorz Kossakowski --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
