You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2014/11/03 14:57:33 UTC
[jira] [Updated] (WICKET-5742) Facilitate the way to react upon
model changes
[ https://issues.apache.org/jira/browse/WICKET-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-5742:
------------------------------------
Description:
As already explained on the mailing list (http://markmail.org/thread/dpdejoiwzyiynfvq ):
I need a way to react upon model (object) changes to establish some "changelog" functionality. This is currently not possible in a consistent way, as e.g. CheckGroup updates the collection in-place before calling setObject (please see my posting for more in-depth explanation).
Therefore I'd propose to establish a listener concept, where listeners are called in Component#modelChanging (handing the component to the listener) and Component#modelChanged. Currently this is only possible by subclassing everything, which is not very practical.
I could find some time to implement this in the next couple of days I guess, if there is consense that this feature may be useful.
was:
As already explained on the mailing list (http://markmail.org/thread/dpdejoiwzyiynfvq):
I need a way to react upon model (object) changes to establish some "changelog" functionality. This is currently not possible in a consistent way, as e.g. CheckGroup updates the collection in-place before calling setObject (please see my posting for more in-depth explanation).
Therefore I'd propose to establish a listener concept, where listeners are called in Component#modelChanging (handing the component to the listener) and Component#modelChanged. Currently this is only possible by subclassing everything, which is not very practical.
I could find some time to implement this in the next couple of days I guess, if there is consense that this feature may be useful.
> Facilitate the way to react upon model changes
> ----------------------------------------------
>
> Key: WICKET-5742
> URL: https://issues.apache.org/jira/browse/WICKET-5742
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.17.0
> Reporter: Tom Götz
> Priority: Minor
>
> As already explained on the mailing list (http://markmail.org/thread/dpdejoiwzyiynfvq ):
> I need a way to react upon model (object) changes to establish some "changelog" functionality. This is currently not possible in a consistent way, as e.g. CheckGroup updates the collection in-place before calling setObject (please see my posting for more in-depth explanation).
> Therefore I'd propose to establish a listener concept, where listeners are called in Component#modelChanging (handing the component to the listener) and Component#modelChanged. Currently this is only possible by subclassing everything, which is not very practical.
> I could find some time to implement this in the next couple of days I guess, if there is consense that this feature may be useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)