Hi Paul, >From your description it seems that MarkLogic Server doesn't allow conflicting >templates indeed. According to XSLT 1.x and 2.0 it is recoverable, so the >parser should continue, but it looks like 2.1 is defining it as >non-recoverable.
It should be relatively easy to work around this though: add a priority attribute to the last-defined template, and you should get the same behavior as with other parsers.. Kind regards, Geert -----Oorspronkelijk bericht----- Van: [email protected] [mailto:[email protected]] Namens Williams, Paul Verzonden: vrijdag 12 augustus 2011 22:05 Aan: General MarkLogic Developer Discussion Onderwerp: [MarkLogic Dev General] Conflicting templates in XSLT Anyone doing complex transforms with multiple xsl:imports and getting an error like this... "XSLT-TEMPLCONFLICT (err:XTRE0540) Conflicting templates found for node: /topic" I realize conflicting templates may indicate that there is some not-so-great xslt code in the stylesheets, but most transform engines deal with it by picking one of the conflicting templates by some rule, like last-defined. I'm trying to apply an existing stylesheet (porting from an eXist application) using xdmp:xslt-eval() and getting this error. The transformation works fine manually in Oxygen using Saxon or Xalan. Does the MLS implementation use a transformer that doesn't allow template conflicts? -- Paul _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
