[richfaces-issues] [JBoss JIRA] Commented: (RF-6456) [SuggestionBox] SuggestionAction called twice during request if usingSuggestObjects = true

Gerrit Brehmer (JIRA) jira-events at lists.jboss.org
Wed Mar 4 18:29:22 EST 2009


    [ https://jira.jboss.org/jira/browse/RF-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12455527#action_12455527 ] 

Gerrit Brehmer commented on RF-6456:
------------------------------------

Thanks for your comment, but please could you explain what do you mean with "capable on filtering"? I don't found any further information on this topic in the developer guide (http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/docs/devguide/en/html/suggestionbox.html).
I thought that the "suggestedObjects" is only a JSon serialized copy of the entire result list of the first suggestionAction call.
Wu use usingSuggestObjects for accesing not visible values from selected entry to set them into other input fields.

> [SuggestionBox] SuggestionAction called twice during request if usingSuggestObjects = true
> ------------------------------------------------------------------------------------------
>
>                 Key: RF-6456
>                 URL: https://jira.jboss.org/jira/browse/RF-6456
>             Project: RichFaces
>          Issue Type: Bug
>    Affects Versions: 3.3.0
>            Reporter: Gerrit Brehmer
>
> SuggestionAction is called twice, if usingSuggestObjects is activated. I looked into the sourcecode and found the two calls:
> - Action with value from request/input field (method setupValue - setValue(suggestingAction.invoke(context.getELContext(), new Object[]{submittedValue}));)
> - Action with "null" as string (method getRequestValuesData - setValue(suggestingAction.invoke(context.getELContext(), new Object[]{requestedValue}));)
> (SourceCode from UiSuggestionBox.java Tag 3.3.0)
> Is the second call really necessary? Because we call an expensive backend method (200ms - 7000ms for address suggest) this makes a noticable delay for the user
> Our workaround is to return an empty list for the second call, which doesn't change the behaviour

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

        



More information about the richfaces-issues mailing list