[
https://jira.jboss.org/jira/browse/RF-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsikhon Kuprevich closed RF-4387.
---------------------------------
> Event queues for groups of components
> -------------------------------------
>
> Key: RF-4387
> URL: https://jira.jboss.org/jira/browse/RF-4387
> Project: RichFaces
> Issue Type: Feature Request
> Components: planning, planning_all
> Affects Versions: 3.2.2
> Reporter: Pete Muir
> Assignee: Tsikhon Kuprevich
> Priority: Critical
> Fix For: 3.3.0
>
>
> the event queue is important for use with conversations (to which we
> serialize concurrent requests) as it stops the server being flooded. To make
> it easier to use, our suggestion is that we make it possible to define an
> event to be used by all nested components:
> <h:form>
> <div id="bar1">
> <h:inputText value="#{foo1.bar1}">
> <a:support id="onblur" event="onblur" reRender="bar1"
> eventsQueue="foo1" />
> </h:inputText>
> </div>
> <a:eventQueue name="foo2">
> <div id="bar21">
> <h:inputText value="#{foo2.bar1}">
> <a:support id="onblur" event="onblur" reRender="bar21"
> eventsQueue="foo2" />
> </h:inputText>
> </div>
> <div id="bar22">
> <h:inputText value="#{foo2.bar2}">
> <a:support id="onblur" event="onblur" reRender="bar22"
> eventsQueue="foo2" />
> </h:inputText>
> </div>
> </a:eventQueue>
> </h:form>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
