You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Will Hoover (JIRA)" <ji...@apache.org> on 2008/07/31 23:38:31 UTC
[jira] Created: (WICKET-1764) Component#modelChanging and
Component#modelChanged are inconsistent with IModel#setObject
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
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 are never notified.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-1764) Component#modelChanging and
Component#modelChanged are inconsistent with IModel#setObject
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (WICKET-1764) Component#modelChanging and
Component#modelChanged are inconsistent with IModel#setObject
Posted by "Will Hoover (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Will Hoover updated WICKET-1764:
--------------------------------
Description:
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.
was: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 will never be notified.
> 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
>
> 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.
[jira] Updated: (WICKET-1764) Component#modelChanging and
Component#modelChanged are inconsistent with IModel#setObject
Posted by "Will Hoover (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Will Hoover updated WICKET-1764:
--------------------------------
Description: 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 will never be notified. (was: 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 are never notified.)
> 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
>
> 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 will never be notified.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.