[WICKET-6231] wicket:enclosure and getVariation().

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 8.0.0-M1, 7.4.0
• Fix Version/s: 8.0.0-M2, 7.5.0
• Component/s: wicket
• Assignee: Andrea Del Bene
• Reporter: Joris van Heesch
• Created: 24/Aug/16 06:21
• Updated: 01/Nov/16 16:53
• Resolved: 29/Aug/16 17:51

Description

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

Issue Links

• is related to: WICKET-6266 Component resolvers & variation broken in 7.5.0