You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sven Meier (JIRA)" <ji...@apache.org> on 2012/07/20 19:15:35 UTC
[jira] [Created] (WICKET-4666) ResourceModel once assigned should
not re-assign
Sven Meier created WICKET-4666:
----------------------------------
Summary: ResourceModel once assigned should not re-assign
Key: WICKET-4666
URL: https://issues.apache.org/jira/browse/WICKET-4666
Project: Wicket
Issue Type: Improvement
Components: wicket
Affects Versions: 6.0.0-beta3
Reporter: Sven Meier
Assignee: Sven Meier
Priority: Trivial
ResourceModel's AssignmentWrapper is itself a ResourceModel.
But sometimes you want to assign a ResourceModel to a component explicitely via #wrapOnAssignment() before passing the wrapper elsewhere.
This is not possible currently, because the passed AssignmentWrapper will re-assign to the component it is passed to.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-4666) ResourceModel once assigned should
not re-assign
Posted by "Sven Meier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sven Meier resolved WICKET-4666.
--------------------------------
Resolution: Fixed
Fix Version/s: 6.0.0
AssignmentWrapper no longer extends ResourceModel, thus preventing re-assignment to other component.
> ResourceModel once assigned should not re-assign
> ------------------------------------------------
>
> Key: WICKET-4666
> URL: https://issues.apache.org/jira/browse/WICKET-4666
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.0.0-beta3
> Reporter: Sven Meier
> Assignee: Sven Meier
> Priority: Trivial
> Fix For: 6.0.0
>
>
> ResourceModel's AssignmentWrapper is itself a ResourceModel.
> But sometimes you want to assign a ResourceModel to a component explicitely via #wrapOnAssignment() before passing the wrapper elsewhere.
> This is not possible currently, because the passed AssignmentWrapper will re-assign to the component it is passed to.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira