myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Rossmueller (JIRA)" <>
Subject [jira] Resolved: (MYFACES-623) setValue() method of ValueBindingImpl does not behave properly
Date Sun, 02 Oct 2005 12:51:48 GMT
     [ ]
Oliver Rossmueller resolved MYFACES-623:

    Resolution: Fixed

Modifications as described above are in r293105 on the 1.1.1 branch. I did not merge it to
the trunk as there might be some issues related to removing coercion from ValueBindingImpl.setValue.

TCK passes with this modifications, and all cactus tests are ok with the exception of
I don't know if this one also failed before, so someone should have a look at it. I also did
not check the examples so far ...

> setValue() method of ValueBindingImpl does not behave properly
> --------------------------------------------------------------
>          Key: MYFACES-623
>          URL:
>      Project: MyFaces
>         Type: Bug
>   Components: JSR-127
>     Versions: 1.1.0
>     Reporter: sean schofield
>     Assignee: Oliver Rossmueller
>      Fix For: 1.1.1
>  Attachments: MYFACES-623.patch
> According to section 5.1.4 of the specification (p. 5-4) ...
> If you have #{expr-a[value-b]}  where value-a is a Map then ...
> call value-a.put(value-b, newValue).
> The MyFaces implementation is coercing newValue into String which is incorrect behavior.
> NOTE: I discovered the problem while using a bean that was programatically added to the
session map.  So there is is no class defined in faces-config.xml.  I don't think this should
matter but I thought I would mention it.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message