a validation rule is to make a field required. In paragraph 11.4.2 we have already seen how this can be done calling setRequired(true) on a field. However, to set a validation 95 rule on a FormComponent into the page will not be dequeued into the panel. This minimizes confusion and debugging time. The rule so far is that if a component provides its own markup only components queued inside it will be dequeued To use XML bundles in Wicket we don’t need to put in place any additional configuration. The only rule we have to respect with these files is to use properties.xml as extension while their base name follows

a validation rule is to make a field required. In paragraph 11.4.2 we have already seen how this can be done calling setRequired(true) on a field. However, to set a validation 94 rule on a FormComponent into the page will not be dequeued into the panel. This minimizes confusion and debugging time. The rule so far is that if a component provides its own markup only components queued inside it will be dequeued To use XML bundles in Wicket we don’t need to put in place any additional configuration. The only rule we have to respect with these files is to use properties.xml as extension while their base name follows

a validation rule is to make a field required. In paragraph 11.4.2 we have already seen how this can be done calling setRequired(true) on a field. However, to set a validation 98 rule on a FormComponent into the page will not be dequeued into the panel. This minimizes confusion and debugging time. The rule so far is that if a component provides its own markup only components queued inside it will be dequeued To use XML bundles in Wicket we don’t need to put in place any additional configuration. The only rule we have to respect with these files is to use properties.xml as extension while their base name follows

example of a validation rule is to make a field required. In paragraph 11.3 we have already seen how this can be done calling setRequired(true) on a field. However, to set a validation rule on 97 a FormComponent into the page will not be dequeued into the panel. This minimizes confusion and debugging time. The rule so far is that if a component provides its own markup only components queued inside it will be dequeued To use XML bundles in Wicket we don’t need to put in place any additional configuration. The only rule we have to respect with these files is to use properties.xml as extension while their base name follows