RichFaces
  1. RichFaces
  2. RF-4387

Event queues for groups of components

    Details

    • Type: Feature Request Feature Request
    • Status: Closed (View Workflow)
    • Priority: Critical Critical
    • Resolution: Done
    • Affects Version/s: 3.2.2
    • Fix Version/s: 3.3.0
    • Component/s: None
    • 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>

        Gliffy Diagrams

          Issue Links

          1.
          Requirements: gathering Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 4 days
          Remaining Estimate - 4 days
          3.3.0  
           
          2.
          Requirements: documenting Sub-task Closed Ilya Shaikovsky

          0%

          Original Estimate - 1 day
          Remaining Estimate - 1 day
          3.3.0  
           
          3.
          Implementation: component base creation Sub-task Closed Nick Belaevski   3.3.0  
           
          4.
          Implementation: server-side code: component class Sub-task Closed Nick Belaevski   3.3.0  
           
          5.
          Implementation: basic client-side code Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 3 days
          Remaining Estimate - 3 days
          3.3.0  
           
          6.
          Implementation: queues discovery and checks services Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 1 week
          Remaining Estimate - 1 week
          3.3.0  
           
          7.
          Implementation: queue-size related code Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 2 days
          Remaining Estimate - 2 days
          3.3.0  
           
          8.
          Implementation: unit tests: client-side code 1 Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 3 days
          Remaining Estimate - 3 days
          3.3.0  
           
          9.
          Implementation: queue disablement Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 4 hours
          Remaining Estimate - 4 hours
          3.3.0  
           
          10.
          Implementation: client-side code: event attributes Sub-task Closed Nick Belaevski

          100%

          Original Estimate - 2 hours Original Estimate - 2 hours
          Time Spent - 5 hours
          3.3.0  
           
          11.
          Add similarityGroupingId attribute to AJAX components (WAS: Add requestId attribute to AJAX components) Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 1 hour
          Remaining Estimate - 1 hour
          3.3.0  
           
          12.
          Implement ignoreDupResponses attribute Sub-task Closed Nick Belaevski

          100%

          Original Estimate - 2 hours Original Estimate - 2 hours
          Time Spent - 7 hours
          3.3.0  
           
          13.
          Implementation: unit tests: server-side code Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 4 hours
          Remaining Estimate - 4 hours
          3.3.0  
           
          14.
          Code refactoring Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 2 hours
          Remaining Estimate - 2 hours
          3.3.0  
           
          15.
          Adding debug code Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 2 hours
          Remaining Estimate - 2 hours
          3.3.0  
           
          16.
          Implementation: unit tests: client-side code: queue discovery services Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 6 hours
          Remaining Estimate - 6 hours
          3.3.0  
           
          17.
          Implementation: unit tests: client-side code: queue attributes Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 1 day, 4 hours
          Remaining Estimate - 1 day, 4 hours
          3.3.0  
           
          18.
          Implementation: unit tests: client-side code: similar requests functionality Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 6 hours
          Remaining Estimate - 6 hours
          3.3.0  
           
          19.
          Documenting Sub-task Closed Michael Sorokin   3.3.0  
           
          20.
          Test cases design Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 2 days
          Remaining Estimate - 2 days
          3.3.0 qe
           
          21.
          Implementation 2 Sub-task Closed Aleksandr Dubovsky   3.3.0  
           
          22.
          Poll component: define default requestDelay as 0 Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 1 hour
          Remaining Estimate - 1 hour
          3.3.0  
           
          23.
          Code review Sub-task Closed Nick Belaevski

          100%

          Original Estimate - 1 day
          Time Spent - 1 day
          3.3.0  
           
          24.
          Bug fixing and testing 1 Sub-task Closed Nick Belaevski

          0%

          Original Estimate - 1 day
          Remaining Estimate - 1 day
          3.3.0  
           
          25.
          demosite-sample Sub-task Closed Nick Belaevski   3.3.0  
           

            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

                    Development