cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abbas Mousavi (JIRA)" <>
Subject [jira] Commented: (COCOON-1999) form styling stylesheets dont work with Saxon (forms-field-styling.xsl)
Date Sat, 03 Feb 2007 14:21:05 GMT


Abbas Mousavi commented on COCOON-1999:

and Grzegorz Kossakowski said on mailing list:

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, 
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?

> form styling stylesheets dont work with Saxon (forms-field-styling.xsl)
> -----------------------------------------------------------------------
>                 Key: COCOON-1999
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Forms
>    Affects Versions: 2.1.10, 2.1.11-dev (Current SVN)
>            Reporter: Abbas Mousavi
>            Priority: Minor
> when you use saxon, some form block examples show this error:
> net.sf.saxon.trans.DynamicError: Ambiguous rule match for /html/body[1]/fi:form-template[1]/div[1]/fi:group[1]/fi:items[1]/fi:group[1]/fi:items[1]/fi:field[2]/fi:styling[1]/@list-type
> Matches both "fi:styling/@list-type | fi:styling/@list-orientation | fi:styling/@listbox-size
| fi:styling/@format | fi:styling/@layout | fi:styling/@class" on line 149 of resource://org/apache/cocoon/forms/resources/forms-field-styling.xsl
> and "fi:styling/@*" on line 137 of resource://org/apache/cocoon/forms/resources/forms-field-styling.xsl
> resource://org/apache/cocoon/forms/resources/forms-field-styling.xsl - 102:-1

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message