[ https://issues.jboss.org/browse/RF-13023?page=com.atlassian.jira.plugin.s... ] Marco Goetz updated RF-13023: ----------------------------- Description: I have noticed that the requestDelay settings or the whole a4j:queue is not working after a page submit. When I open the view the requestDelay works fine and 4 seconds after a keyup event in the input field, an ajax request is processed. But when I press the commandButton the queue functionality is lost and ajax requests are performed immediately without a delay. {code:xml} <h:body> <h:form id="form"> <h:commandButton value="Button" /> <a4j:queue requestDelay="4000"/> <h:inputText> <a4j:ajax event="keyup" ></a4j:ajax> </h:inputText> </h:form> </h:body> {code} The same problem exists when I use <a4j:attachQueue> I found out that this issue is related with PARTIAL_STATE_SAVING context parameter in the web.xml. I need to disable this paramter otherwise some views won't work correctly. If this paramter is enabled the a4j:queue works like it should. My web.xml: {code:xml} <context-param> <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name> <param-value>false</param-value> </context-param> {code} was: I have noticed that the requestDelay settings or the whole a4j:queue is not working after a page submit. When I open the view the requestDelay works fine and 4 seconds after a keyup event in the input field, an ajax request is processed. But when I press the commandButton the queue functionality is lost and ajax requests are performed immediately without a delay. {code:xml} <h:body> <h:form id="form"> <h:commandButton value="Button" /> <a4j:queue requestDelay="4000"/> <h:inputText> <a4j:ajax event="keyup" ></a4j:ajax> </h:inputText> </h:form> </h:body> Notation Comment {noformat} preformatted piece of text so *no* further _formatting_ is done here {noformat} Makes a preformatted block of text with no syntax highlighting. All the optional parameters of {panel} macro are valid for {noformat} too. nopanel: Embraces a block of text within a fully customizable panel. The optional parameters you can define are the following ones: Example: preformatted piece of text so *no* further _formatting_ is done here {panel}Some text{ {panel:title=My Title}Some text with a title{ {panel:title=My Title| borderStyle=dashed| borderColor=#ccc| titleBGColor=#F7D6C1| bgColor=#FFFFCE} a block of text surrounded with a *panel* yet _another_ line {panel} Embraces a block of text within a fully customizable panel. The optional parameters you can define are the following ones: title: Title of the panel borderStyle: The style of the border this panel uses (solid, dashed and other valid CSS border styles) borderColor: The color of the border this panel uses borderWidth: The width of the border this panel uses bgColor: The background color of this panel titleBGColor: The background color of the title section of this panel Example: My Title a block of text surrounded with a panel yet another line {code:title=Bar.java|borderStyle=solid} // Some comments here public String getFoo() { return foo; } {code} {code:xml} <test> <another tag="attribute"/> </test> {code} The same problem exists when I use <a4j:attachQueue> I found out that this issue is related with PARTIAL_STATE_SAVING context parameter in the web.xml. I need to disable this paramter otherwise some views won't work correctly. If this paramter is enabled the a4j:queue works like it should. My web.xml: <context-param> <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name> <param-value>false</param-value> </context-param> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira