Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: domain of joerg.heinicke@gmx.de
 designates 213.165.64.20 as permitted sender)
Message-ID: <45221A20.8010303@gmx.de>
Date: Tue, 03 Oct 2006 10:06:56 +0200
From: Joerg Heinicke <joerg.heinicke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [CFORMS] Template priority problems fix with saxon
References: <DACD67E5D2FBD441BF4E9D957A6DD5A203722C@sonne.univativ.com>
In-Reply-To: <DACD67E5D2FBD441BF4E9D957A6DD5A203722C@sonne.univativ.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 02.10.2006 15:05, Christofer.Dutz@univativ.de wrote:

> One of the patches was a change of template priorities in the
> forms-field-styling.xslt  If this isn't applied, I get
> Abiguous Template errors from Saxon.
> 
> <xsl:template match="fi:styling/@*" mode="styling"> 
> 
> Has to be changed to:
> 
> <xsl:template match="fi:styling/@*" mode="styling" priority="-1"> 
> 
> And this bug is resolved.

I would not call this a bug, it's just another way of confirming to the 
spec. It says [1]:
"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."

But I don't like influencing the priority as it might break other 
stylesheets extending our ones. Not only once, but regularly. This can 
happen if we add a new template rule and have to adapt priority again. 
But probably this is not that much a matter anymore as there are already 
so many @priority's added.

I only wonder with which template it conflicts. All others have 
specified the attribute name and should so be more specific. Does this 
occur only with a specific version of Saxon? Is everybody using Saxon in 
need for such a patch?

J�rg

[1] http://www.w3.org/TR/xslt#conflict