[
https://issues.apache.org/jira/browse/WICKET-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769835#action_12769835
]
Juergen Donnerstag commented on WICKET-2541:
--------------------------------------------
Unfortunately, since Enclosure is a transparent resolver, that cannot be solved
by Wicket. But you can easily do that yourself. A a wicket:id to the enclosure
tag, e.g.
<wicket:enclosure wicket:id="myEnclosure" ...>
manually add an Enclosure component to your container add(new
Enclosure("myEnclosure", ....) and add the childrens A and B to the enclosure.
That's it
> 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.
