myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paris Holley (JIRA)" <>
Subject [jira] Commented: (MYFACES-2006) getTableIndex: Integer to String (ClassCastException)
Date Mon, 06 Oct 2008 21:33:44 GMT


Paris Holley commented on MYFACES-2006:

Indeed, this does not appear to be a blocker issue.

So the best solution I would assume (on my end), is to return an Integer instead of a String
(so that there are no conflicts), however the question you present is an interesting dilemma.

In my opinion, introducing "new standards" within the JSF 1.1 releases wouldn't seem appropriate
given that it is an older version and it has been used since the MyFaces 1.0.x releases. I
am always for standards (which surely should be put in place on JSF 1.2), however I think
that at some point backwards compatibility is just as important (particularly if you consider
the 1.0.x releases a "legacy" library).

> getTableIndex: Integer to String (ClassCastException)
> -----------------------------------------------------
>                 Key: MYFACES-2006
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 1.1.6
>            Reporter: Paris Holley
>            Priority: Blocker
> 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

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

View raw message