myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sean schofield (JIRA)" <>
Subject [jira] Updated: (MYFACES-889) Spec compliance: managed-beans do not support List properties that are write-only
Date Wed, 30 Nov 2005 03:39:30 GMT
     [ ]

sean schofield updated MYFACES-889:

    Component: JSR-127
                   (was: Implementation)
     Priority: Critical  (was: Major)

> Spec compliance: managed-beans do not support List properties that are write-only
> ---------------------------------------------------------------------------------
>          Key: MYFACES-889
>          URL:
>      Project: MyFaces
>         Type: Bug
>   Components: JSR-127
>     Versions: 1.1.1
>  Environment: All.
>     Reporter: Adam Winer
>     Priority: Critical

> If you use <list-entries> for a property that has only a setter, you get a FacesException
> as a result of ManagedBeanBuilder.initializeProperties() calling PropertyResolver.getValue().
> However, the spec is clear that this scenario is supported;  see
> For <list-entries>:
> 1. Call the property getter, if it exists.
> 2. If the getter returns null or doesn't exist, create a java.util.ArrayList,
> otherwise use the returned Object (an array or a java.util.List).
> (etc.)
> Note that <map-entries> has the same language, and therefore the
> same bug exists in MyFaces.
> The above behavior is properly implemented by the RI.
> Generally speaking, there is a problem that the managed bean facility is attempting to
> use PropertyResolver - which is cool, and which the spec should have done in
> retrospect - but I think is illegal, since it implies functionality and extensibility
that is not
> stated in the spec, and language like the above for list-entries more-or-less implies
> that PropertyResolver is not used.

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