[richfaces-issues] [JBoss JIRA] (RF-13023) a4j:queue Functionality gets lost after Submit (with disabled PARTIAL_STATE_SAVING)

[Marco Goetz (JIRA)]

Marco Goetz created RF-13023:
--------------------------------

             Summary: a4j:queue Functionality gets lost after Submit (with disabled PARTIAL_STATE_SAVING)
                 Key: RF-13023
                 URL: https://issues.jboss.org/browse/RF-13023
             Project: RichFaces
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: component-a4j-core
    Affects Versions: 4.3.2
         Environment: MyFaces 2.1.11 
Richfaces 4.3.2.Final.
Reproducible with Chrome, FF, IE10
            Reporter: Marco Goetz


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