You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Florian Lacreuse (Jira)" <ji...@apache.org> on 2025/04/22 15:57:00 UTC

[jira] [Commented] (WICKET-7141) Add hook method afterUpdateFormComponentModels() in Form process

    [ https://issues.apache.org/jira/browse/WICKET-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17946462#comment-17946462 ] 

Florian Lacreuse commented on WICKET-7141:
------------------------------------------

Hi,

Did you have time to look at my pull request?
I imagine you're all pretty busy already, but let me know if I can help in any way.

Thanks!

> 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)