[
https://issues.apache.org/jira/browse/MYFACES-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639448#action_12639448
]
Taro App commented on MYFACES-2006:
-----------------------------------
I have voted for this issue. This is more serious for me. The problem is not
just inputText's tabindex, but more wide spread. For example,
- binding for inputText's size and maxlength must be an Integer and not null.
- binding for inputText's tabindex must be a String and not null.
- binding for inputText's disabled and readonly must not return null.
- binding for inputTextarea's rows and cols must be an Integer and not null.
- binding for graphicsImage's width and height must be a String and not null.
Firstly, it does not seem consistent. For example, inputText's size is an
Integer, where graphicsImage's width is a String. If a value binding does not
return matching data type, ClassCastException is thrown. In the previous
releases, it just worked.
Secondly, it does not default. If a value binding returns null,
NullPointerException is thrown. In the previous releases, default value is used
instead.
Thirdly, arithmatic expression binding cannot be used. For example, setting
size="#{bean.value * 10}" for inputText raises ClassCastExpression because the
calculated value is a Long.
I have a large application which has been working on MyFaces Core 1.1.3 and
Tomahawk 1.1.3. I am trying to upgrade to MyFaces Core 1.1.6 and Tomahawk
1.1.7, but this is the blocking issue.
> getTableIndex: Integer to String (ClassCastException)
> -----------------------------------------------------
>
> Key: MYFACES-2006
> URL: https://issues.apache.org/jira/browse/MYFACES-2006
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 1.1.6
> Reporter: Paris Holley
>
> Have a project using MyFaces 1.1.5 and Tomahawk 1.1.7. When MyFaces 1.1.5 is
> upgraded to 1.1.6 classcast exceptions are thrown when elements such as
> HtmlInputText try to access getTabIndex through an EL expression that returns
> an "int". Though the spec states that the EL expression should return a
> string, this was not a problem in the previous version. If tag attributes are
> more strict in the latest release, it would help to have stated so in the
> release notes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
