4:32 a.m.
Rene O created RF-11902:
---------------------------
Summary: [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
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
11:28 p.m.
[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-11902:
------------------------------------
Is it not sufficient to nest a
[a4j:attachQueue|http://showcase.richfaces.org/richfaces/component-sample....]
within the component?
[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
1:23 a.m.
[
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
4:17 p.m.
[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-11902:
------------------------------------
Just to be sure:
Did you create the analagous a4j:queue with name "myq" that you are trying to
attach to?
[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
11:32 a.m.
[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Rene O commented on RF-11902:
-----------------------------
I have investigated this a bit more:
1. If my global queue has no name, then rich:autocomplete uses the global request delay
{code:title=global queue without name}
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich">
<h:head >
<title>jsf2testcase</title>
</h:head>
<h:body>
<a4j:queue id="myGlobalQ" requestDelay="2000"
ignoreDupResponses="true"/>
<h:form id="form">
<rich:autocomplete id="mya" minChars="1"
mode="cachedAjax" value="#{model.testValue}"
autocompleteMethod="#{ctr.doAutocomplete}">
</rich:autocomplete>
<br/><br/><br/><br/>
<br/><br/><br/><br/>
<a4j:status>
<f:facet name="start">
Please wait...
</f:facet>
</a4j:status>
</h:form>
</h:body>
</html>
{code}
2. If my global queue has a name, then rich:autocomplete doesn't use the global
request delay and executes immediately
{code:title=global queue with name}
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich">
<h:head >
<title>jsf2testcase</title>
</h:head>
<h:body>
<a4j:queue id="myGlobalQ" name="myGlobalQ"
requestDelay="2000" ignoreDupResponses="true"/>
<h:form id="form">
<rich:autocomplete id="mya" minChars="1"
mode="cachedAjax" value="#{model.testValue}"
autocompleteMethod="#{ctr.doAutocomplete}">
</rich:autocomplete>
<br/><br/><br/><br/>
<br/><br/><br/><br/>
<a4j:status>
<f:facet name="start">
Please wait...
</f:facet>
</a4j:status>
</h:form>
</h:body>
</html>
{code}
3. If i use an attachedQueue with the name of my global queue, then execution starts again
immediately and in addition the suggestion list shows no values, but has the correct size
(This behaviour also occurs if the attached queue has no name)
{code:title=attached queue with name}
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich">
<h:head >
<title>jsf2testcase</title>
</h:head>
<h:body>
<a4j:queue id="myGlobalQ" name="myGlobalQ"
requestDelay="2000" ignoreDupResponses="true"/>
<h:form id="form">
<rich:autocomplete id="mya" minChars="1"
mode="cachedAjax" value="#{model.testValue}"
autocompleteMethod="#{ctr.doAutocomplete}">
<a4j:attachQueue id="myAttachedQ" name="myGlobalQ"
requestDelay="300" />
</rich:autocomplete>
<br/><br/><br/><br/>
<br/><br/><br/><br/>
<a4j:status>
<f:facet name="start">
Please wait...
</f:facet>
</a4j:status>
</h:form>
</h:body>
</html>
{code}
Now the question is, do i something wrong or is this a bug?
Extra information: I have used richfaces-4.2.0.CR1 and myfaces-2.1.6
[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
11:35 a.m.
[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-11902:
------------------------------------
Rene, are you able to try this with Mojarra?
[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
2:40 p.m.
[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Rene O commented on RF-11902:
-----------------------------
All 3 cases behave identically with mojarra-2.1.6
[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
1:30 p.m.
[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Brian Leathem reassigned RF-11902:
----------------------------------
Assignee: Pavol Pitonak
QE, would you please build a metamer test incorporating the 3 provided scenario code
snippets?
[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
Assignee: Pavol Pitonak
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
9:15 a.m.
[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Pavol Pitonak reassigned RF-11902:
----------------------------------
Assignee: Ján Jamrich (was: Pavol Pitonak)
[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
Assignee: Ján Jamrich
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
7:03 a.m.
[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Ján Jamrich reassigned RF-11902:
--------------------------------
Assignee: (was: Ján Jamrich)
Issue simulated in Metamer using code snippet provided by reporter.
See following commit for more details:
https://github.com/richfaces/qa/commit/eb60f82f7b80f6e6d1a1f4762b4a981d41...
[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
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
1:50 p.m.
[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11902:
-------------------------------
Fix Version/s: 4.3-Tracking
[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
Fix For: 4.3-Tracking
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
9:28 a.m.
[
https://issues.jboss.org/browse/RF-11902?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-11902:
-------------------------------
Component/s: component-input
[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)
Components: component-input
Affects Versions: 4.1.0.Final
Reporter: Rene O
Fix For: 4.3-Tracking
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
4576
days inactive
4701
days old
richfaces-issues@lists.jboss.org
11 comments
4 participants
participants (4)
-
Brian Leathem (JIRA) -
Ján Jamrich (JIRA)
-
Pavol Pitonak (JIRA)
-
Rene O (JIRA)