[
https://issues.apache.org/jira/browse/TRINIDAD-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948200#comment-13948200
]
Jeanne Waldman commented on TRINIDAD-2459:
------------------------------------------
Completed: At revision: 1581963
> Addition of ValueUpdatedEvent + ValueUpdatedListener
> ----------------------------------------------------
>
> Key: TRINIDAD-2459
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2459
> Project: MyFaces Trinidad
> Issue Type: New Feature
> Components: Components
> Affects Versions: 2.1.0-core
> Environment: N/A
> Reporter: Ji Kim
> 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
(v6.2#6252)
