[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Rene O commented on RF-11902:
-----------------------------
It is not sufficient, beacause it doesn't work.
I have tried the following code within h:form
{code}
<rich:autocomplete id="mya" minChars="2"
value="#{myModel.testValue}"
autocompleteMethod="#{userCtr.autocompleteVermittler}">
<a4j:attachQueue id="myq" name="myq"
requestDelay="750" ignoreDupResponses="true"
requestGroupingId="myqg"/>
</rich:autocomplete>
{code}
The search starts immediatly after i put in the 2nd character. The search doesn't wait
750ms.
Apart from that i think it is not the best solution. Imagine if you have a lot of
autocomplete components. Then its better to reuse a global queue.
[rich:autocomplete] add attribute queueId
-----------------------------------------
Key: RF-11902
URL:
https://issues.jboss.org/browse/RF-11902
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.1.0.Final
Reporter: Rene O
Labels: waiting_on_user
It would be nice if rich:autocomplete has an attribute queueId like a4j:ajax component.
With this you will have more control over the ajax requests if ajax mode is enabled within
autocomplete component.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira