[ https://issues.apache.org/jira/browse/WICKET-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916103#comment-17916103 ]
ASF GitHub Bot commented on WICKET-7141: ---------------------------------------- florianlacreuse opened a new pull request, #1087: URL: https://github.com/apache/wicket/pull/1087 (no comment) > 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)