The problem is that when a control is used inside an iterator, its ID changes internally to account the fact that there would be otherwise duplicate IDs. Cause of this if the af:message component is not configured properly for the iterator, it woludn't work properly.
Here is an example hot to use af:message components inside af:iterator:
<af:iterator id="i1" value="#{backingBeanScope.MyBean.listForIterator}" varStatus="vs"> <af:inputText label="Input #{vs.index}" id="it1"> <af:validateLongRange minimum="5" maximum="10"/> </af:inputText> <af:message id="m1" for="#{vs.index}:it1"/> </af:iterator>
..
No comments:
Post a Comment