]
Jay Balunas updated RF-11219:
-----------------------------
Fix Version/s: 4.1.0.Milestone3
(was: 4.1.0.Milestone2)
Forum Reference:
Notify - validator messages and two stacks
------------------------------------------
Key: RF-11219
URL:
https://issues.jboss.org/browse/RF-11219
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-output
Affects Versions: 4.1.0.Milestone1
Reporter: Jan Papousek
Assignee: Lukáš Fryč
Priority: Minor
Fix For: 4.1.0.Milestone3
I have tried a validation and for attribute with two stacks
(
https://gist.github.com/1106505#). The notify component displays correctly. Each stack
contains one message generated by notify component. On the other side the notifyMessages
component produces all messages twice (into the both stacks).
(from
http://community.jboss.org/message/617599#617599)
Example source code:
{code}
<h:form>
<notify:notifyMessages for="number1" stack="topRightStack"
ajaxRendered="true" />
<notify:notifyMessages for="number2" stack="bottomRightStack"
ajaxRendered="true" />
<notify:notify sticky="false" stayTime="5000" title="Stack
1" text="Details of the message" stack="topRightStack"/>
<notify:notify sticky="false" stayTime="5000" title="Stack
2" text="Details of the message" stack="bottomRightStack"/>
<notify:notifyStack id="topRightStack" styleClass="topRight"
stackDir1="up" stackDir2="left" push="bottom"/>
<notify:notifyStack id="bottomRightStack"
styleClass="bottomRight" stackDir1="up" stackDir2="left"
push="bottom"/>
<h:outputLabel for="number1" value="Number for Stack 1"/>
<h:inputText id="number1" required="true">
<f:validateLongRange minimum="5" maximum="10"/>
<a4j:ajax event="change" execute="@form"/>
</h:inputText>
<h:outputLabel for="number2" value="Number for Stack 2"/>
<h:inputText id="number2" required="true">
<f:validateLongRange minimum="5" maximum="10"/>
<a4j:ajax event="change" execute="@form"/>
</h:inputText>
</h:form>
{code}
(from
https://gist.github.com/1133755)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: