You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Andy Schwartz (JIRA)" <de...@myfaces.apache.org> on 2013/11/05 17:10:20 UTC

[jira] [Updated] (TRINIDAD-2410) LOCAL_VALUE_SET_KEY and SUBMITTED_VALUE_KEY should specify CAP_NOT_BOUND

     [ https://issues.apache.org/jira/browse/TRINIDAD-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Schwartz updated TRINIDAD-2410:
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.0-core
           Status: Resolved  (was: Patch Available)

> LOCAL_VALUE_SET_KEY and SUBMITTED_VALUE_KEY should specify CAP_NOT_BOUND
> ------------------------------------------------------------------------
>
>                 Key: TRINIDAD-2410
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2410
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>            Reporter: Andy Schwartz
>            Assignee: Andy Schwartz
>            Priority: Minor
>             Fix For: 2.1.0-core
>
>         Attachments: trinidad-2410.patch
>
>
> UIXEditableValue includes the following two property key definitions:
>   static public final PropertyKey LOCAL_VALUE_SET_KEY =
>     TYPE.registerKey("localValueSet", Boolean.class);
>   static public final PropertyKey SUBMITTED_VALUE_KEY =
>     TYPE.registerKey("submittedValue");
> Note that although neither of these property keys support EL binding, the property key definitions fail to specify the PropertyKey.CAP_NOT_BOUND capability.
> We should specify this to avoid unnecessary lookups in the ValueExpression map.



--
This message was sent by Atlassian JIRA
(v6.1#6144)