[
https://issues.apache.org/jira/browse/WICKET-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769913#action_12769913
]
Christian Oldiges commented on WICKET-2541:
-------------------------------------------
Yep, this works and is the solution I have choosen after your initial response,
because this limitation of wicket:enclosure makes it kinda useless for
FormComponents and I rather use the more "logical" WMC.
In any case I would recommend adding some kind of warning to the
wicket:enclosure docs to not use it for hiding FormComponents.
Thx for your quick response.
> FormComponents hidden by wicket:enclosure should not be validated upon form
> submit
> ----------------------------------------------------------------------------------
>
> Key: WICKET-2541
> URL: https://issues.apache.org/jira/browse/WICKET-2541
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.3
> Reporter: Christian Oldiges
> Priority: Minor
>
> FormComponents that are hidden by an enclosing wicket:enclosure tag should
> not by validated.
> If there is a form with 2 form components A and B and an enclosure is used to
> hide both A and B and it is controlled by B.isVisible (wicket:enclosure
> child="B"), the FormComponent A is still validated.
> Simple example: a RequiredTextField is still required even if made invisible
> by a surrounding enclosure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
