[
https://issues.apache.org/jira/browse/WICKET-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Del Bene resolved WICKET-6231.
-------------------------------------
Resolution: Fixed
> wicket:enclosure and getVariation().
> ------------------------------------
>
> Key: WICKET-6231
> URL: https://issues.apache.org/jira/browse/WICKET-6231
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 8.0.0-M1, 7.4.0
> Reporter: Joris van Heesch
> Assignee: Andrea Del Bene
> Priority: Minor
> Fix For: 8.0.0-M2, 7.5.0
>
> Attachments: myproject.zip
>
>
> We have a panel with a child form.
> When the form is submitted (via a link, textfield, ...), the following
> events will happen:
> * 1 call to form's onSubmit()
> * n calls to panel's getVariation().
> * reload of panel (with or without ajax).
> If, however, there is a <wicket:enclosure> tag with a child (for example - a
> label) inside the form's markup, the following events will happen when the
> form is submitted:
> * 1 call to panel's getVariation()
> * 1 call to form's onSubmit()
> * m calls to panel's getVariation().
> The resulting problem:
> The form (and its children) seem to be rendered using the markup file that
> was found as a result of the first call to getVariation(), while all other
> children
> of the panel will be rendered using the markup file that was found as a
> result of a call to getVariation() that happened after the form's submission.
> In our case - the form's submission causes the result of getVariation() to
> change, which results in incorrect markup (mixture of two markup files).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
