[
https://issues.apache.org/jira/browse/WICKET-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023047#comment-18023047
]
ASF subversion and git services commented on WICKET-7141:
---------------------------------------------------------
Commit 1a3b18cf8418fb3360332facf07b67acd267efed in wicket's branch
refs/heads/master from Florian Lacreuse
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=1a3b18cf84 ]
WICKET-7141 Add hook method afterUpdateFormComponentModels() in Form process
(#1087)
* WICKET-7141 Add hook methods before and after update form components models
(post order).
* Improve test method name
* Improve test method name
* Remove empty line
* Fixed bracket indentation
---------
Co-authored-by: Martin Grigorov <[email protected]>
Co-authored-by: Andrea Del Bene <[email protected]>
> Add hook method afterUpdateFormComponentModels() in Form process
> ----------------------------------------------------------------
>
> Key: WICKET-7141
> URL: https://issues.apache.org/jira/browse/WICKET-7141
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 10.3.0
> Reporter: Florian Lacreuse
> Priority: Minor
> Labels: form
> Attachments: form-process-hook.patch
>
>
> In my team, we need to be able to do specific actions once the update form
> component models phase is complete, at the parent form level.
> The process form algorithm provides a hook method
> {{beforeUpdateFormComponentModels()}} but it's way too early.
> Until Wicket 10.2.0 (included), we get around the problem by overriding the
> {{onValidateModelObjects()}} from the parent form.
> However since Wicket 10.3.0 and WICKET-3899, this small hack no longer works
> due to new postorder processing (nested forms come first).
> Anyway, we think this "after" hook method can be useful for many reasons,
> just like the "before" one.
> What do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
