[richfaces-issues] [JBoss JIRA] Work logged: (RF-7520) #{rich:component('suggestion')}.callSuggestion(true) becomes practically unusable with frequency on rich:suggestionbox

[Andrey Markhel (JIRA)]

     [ https://jira.jboss.org/jira/browse/RF-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_12422167 ]

Andrey Markhel logged work on RF-7520:
--------------------------------------

                Author: Andrey Markhel
            Created on: 15/Jul/09 09:51 AM
            Start Date: 15/Jul/09 09:50 AM
    Worklog Time Spent: 5 hours 
      Work Description: Fixed

Issue Time Tracking
-------------------

    Remaining Estimate: 0 minutes
            Time Spent: 5 hours


> #{rich:component('suggestion')}.callSuggestion(true) becomes practically unusable with  frequency on rich:suggestionbox
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-7520
>                 URL: https://jira.jboss.org/jira/browse/RF-7520
>             Project: RichFaces
>          Issue Type: Bug
>          Components: component-input
>    Affects Versions: 3.3.1
>         Environment: Any rendering kit that can run correctly  Richfaces 3.3.1 showcase
>            Reporter: Konstantin Spirov
>            Assignee: Andrey Markhel
>             Fix For: 3.3.2.CR1
>
>          Time Spent: 5 hours
>  Remaining Estimate: 0 minutes
>
> Very simple scenario to reproduce the problem:
> 1) Take from Richfaces showcase RichInput:SuggestionBox:ObjectsUsageExample
> 2) Just add in rich:suggestionbox frequency="10" attribute
> 3) Recompile & redeploy
> 4) Click on the arrow
> 5) You will need to wait 10 seconds before you see the suggestion list.
> Please correct the problem or  create an alternative method as callSuggestionASAP() 
> There was a good idea behind .callSuggestion(true): to  give us  some solution to emulate the "combobox" - all delays after 
> clicking the arrow make very bad impression, they should be minimized always when if is possible.
> Even without giving frequency parameter, we have default value of 400 ms. This, plus the requestDelay parameter in a4j:queue we cannot escape from,
> plus the time for processing  the request and... the delay before diplaying the list starts to be very visible for the end user (in local network!). We need
> some practical alternative to skip at least the delay from "frequency".

-- 
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