StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Nesting forms is illegal in HTML. The browser behaviour is unspecified. From JSF perspective, you should thus never nest <code><h:form></code> components.</p> <p>As to the reason why you needed to nest the forms,</p> <blockquote> <p><em>If would avoid to nest forms but this is impossible because mojarra would not allow me to put, e.g. a commandLink that is contained in a component without sorrounding it by a form.</em></p> </blockquote> <p>This is not true. Perhaps you're taking the following well known <em>warning</em> <strong>too</strong> serious.</p> <blockquote> <p>WARNING: The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <code><h:form></code></p> </blockquote> <p>This is "just" a warning, not an error. If your page works fine, then you can just ignore the warning. This warning will only show when you've set the project stage to <code>Development</code>. It will not show when you set it to <code>Production</code>.</p> <p>On early Mojarra versions there was however a bug which makes this warning to also occur when you've put for example the command link in some child/include template file, while the form is placed in the master template (which is thus inside a physically different file). Upgrading the Mojarra version should fix this incorrect and confusing warning.</p> <h3>See also:</h3> <ul> <li><a href="https://stackoverflow.com/questions/4089076/the-form-component-needs-to-have-a-uiform-in-its-ancestry-suggestion-enclose-t">The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form> </a></li> <li><a href="https://stackoverflow.com/questions/7371903/multiple-hform-in-a-jsf-page">How to use <h:form> in JSF page? Single form? Multiple forms? Nested forms?</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload