RichFaces
  1. RichFaces
  2. RF-4387

Event queues for groups of components

    Details

    • Type: Feature Request Feature Request
    • Status: Closed Closed (View Workflow)
    • Priority: Critical Critical
    • Resolution: Done
    • Affects Version/s: 3.2.2
    • Fix Version/s: 3.3.0
    • Component/s: None
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      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>

        Issue Links

          Activity

          Hide
          Jay Balunas
          added a comment -

          Part of a bulk update, all resolutions changed to done, please review history to original resolution type

          Show
          Jay Balunas
          added a comment - Part of a bulk update, all resolutions changed to done, please review history to original resolution type

            People

            • Assignee:
              Nick Belaevski
              Reporter:
              Pete Muir
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 5 weeks, 2 days, 2 hours Original Estimate - 5 weeks, 2 days, 2 hours
                5w 2d 2h
                Remaining:
                Time Spent - 2 days, 4 hours Remaining Estimate - 5 weeks, 6 hours
                5w 6h
                Logged:
                Time Spent - 2 days, 4 hours Remaining Estimate - 5 weeks, 6 hours
                2d 4h