]
Juraj Huska resolved RF-11405.
------------------------------
Resolution: Out of Date
I can not reproduce this bug whether on current SNAPSHOTS or on the 4.1.0.20111101-M4
showcase version
showcase - rich:messages - validation does not work on Tomcats,
warning is rendered
-----------------------------------------------------------------------------------
Key: RF-11405
URL:
https://issues.jboss.org/browse/RF-11405
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-validators, showcase
Affects Versions: 4.1.0.Milestone2
Environment: application: richfaces-showcase-4.1.0.20110910-M2-tomcat6.war
browsers: Chrome, FF
containers: Tomcat 6.0.32, Tomcat 7.0.20
Reporter: Juraj Huska
Fix For: 4.1.0.Tracking
Validation in demo for rich:messages does not work. When I click on Ajax Validate no
inputs are validated. Ajax request is thrown, but no validation messages are shown. In the
place where validation messages should be, a warning is generated:
The form component needs to have a UIForm in its ancestry. Suggestion: enclose the
necessary components within <h:form>.
However when I inspect the code, it seems to be ok:
{code:xml}
<h:form>
<rich:messages ajaxRendered="true" />
<h:panelGrid columns="2">
<h:outputText value="Name:" />
<h:inputText label="Name" id="name"
required="true" value="#{userBean.name}">
<f:validateLength minimum="3" />
</h:inputText>
<h:outputText value="Job:" />
<h:inputText label="Job" id="job"
required="true" value="#{userBean.job}">
<f:validateLength minimum="3" maximum="50"
/>
</h:inputText>
<h:outputText value="Address:" />
<h:inputText label="Address" id="address"
required="true" value="#{userBean.address}">
<f:validateLength minimum="10" />
</h:inputText>
<h:outputText value="Zip:" />
<h:inputText label="Zip" id="zip"
required="true" value="#{userBean.zip}">
<f:validateLength minimum="4" maximum="9"
/>
</h:inputText>
<f:facet name="footer">
<a4j:commandButton value="Ajax Validate" />
</f:facet>
</h:panelGrid>
</h:form>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: