myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeanne Waldman (JIRA)" <>
Subject [jira] [Updated] (TRINIDAD-2459) Addition of ValueUpdatedEvent + ValueUpdatedListener
Date Wed, 26 Mar 2014 17:43:16 GMT


Jeanne Waldman updated TRINIDAD-2459:

       Resolution: Fixed
    Fix Version/s: 2.1.1-core
         Assignee: Jeanne Waldman
           Status: Resolved  (was: Patch Available)

committed for Ji Kim on trunk.

> Addition of ValueUpdatedEvent + ValueUpdatedListener
> ----------------------------------------------------
>                 Key: TRINIDAD-2459
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: New Feature
>          Components: Components
>    Affects Versions: 2.1.0-core
>         Environment: N/A
>            Reporter: Ji Kim
>            Assignee: Jeanne Waldman
>             Fix For: 2.1.1-core
>         Attachments: valueUpdatedEvent.patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> This change is to add a new ValueUpdatedEvent + ValueUpdatedListener where ValueUpdatedEvent
will be queued within UIXEditableValueTemplate.updateModel method.
> This is to allow components and etcetera to listen to this event by adding a listener
in the new UIXEditableValueTemplate.addValueUpdatedListener API.
> The pro of adding this event + listener is that various components can then listen when
the value has been updated in the model.
> This is beneficial in
> 1) Clearing up any data that would have been persisted for some reason [i.e. if the app
wished to keep a temporary value of a component using some kind of polling from client to
server to not lose any dirty data {i.e. how confluence wiki allows users to preserves the
old states}].
> 2) To avoid sending a certain asynchronous dirty data from the client to the server
> Thanks!

This message was sent by Atlassian JIRA

View raw message