2 Replies Latest reply on Mar 29, 2010 9:07 AM by ilya_shaikovsky

    filterevent delay in extendeddatatable?

    kukeltje

      A lot of things can be found in the forum and jira about filtering and extendeddatatable. I was however not able to find any post related to my issue

      When I fully 'manually' implement filtering in a datatable, I can put a delay on the a4j:support for the onkeyup event. In the extendeddatatable there is no option for this. Running the application remotely (not on a lan) it works ok, but within the lan behaviour is not really ok. The filter goes of way to often resulting in many calls to the system instead of just one. Is there a way to add a delay here *without* reverting back to fully manually doing filtering?

        • 1. Re: filterevent delay in extendeddatatable?
          berkum

          I was able to do it like this (v.3.3.3.BETA1) :

           

          <rich:column filterBy="#{object.field1}" filterEvent="onkeyup" filterValue="#{rmyFilterValue}"  >
                    <a4j:queue requestDelay="300" ignoreDupResponses="true" />
                      <h:outputText value="#{object.field1}" /> - <h:outputText value="#{object.field2}" />
          </rich:column>

           

          in a rich:dataTable

          • 2. Re: filterevent delay in extendeddatatable?
            ilya_shaikovsky

            yes using queue is right solution but just want to note that specifying it inside column isn't need. In order to define default queue as you trying you could just put single instance outside of table in the form.