[
https://issues.apache.org/jira/browse/WICKET-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-1764.
-----------------------------------
Resolution: Won't Fix
Assignee: Igor Vaynberg
there is simply no way for us to fix this. the modelchanged/changing may be
going away in 1.5 for this reason.
> Component#modelChanging and Component#modelChanged are inconsistent with
> IModel#setObject
> -----------------------------------------------------------------------------------------
>
> Key: WICKET-1764
> URL: https://issues.apache.org/jira/browse/WICKET-1764
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.3.4
> Environment: N/A
> Reporter: Will Hoover
> Assignee: Igor Vaynberg
>
> Component#modelChanging and Component#modelChanged are inconsistent with
> IModel#setObject. Someone can call IModel#setObject for a model that is being
> used on a component that overrides Component#modelChanging and/or
> Component#modelChanged and they may never be notified.
> Consider the use case where a CompoundPropertyModel is being used- setObject
> can be called with out receiving a notification that the model is changing or
> has been changed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
