[
https://issues.apache.org/jira/browse/WICKET-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18022424#comment-18022424
]
ASF GitHub Bot commented on WICKET-7141:
----------------------------------------
reiern70 commented on PR #1087:
URL: https://github.com/apache/wicket/pull/1087#issuecomment-3328335641
> @reiern70 @pedrosans Sorry about that, but I have to bring up the subject
again. Do you know if this fix will be merged soon (if the fix is good enough)?
To be honest I do not fully grok the related code-base and the full
implications of this change. To me it looks like it will not break any existing
applications. But I would like also some more senior wicket developers, e.g.,
@martin-g to have a look and approve this work.
> 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)
