[
https://issues.jboss.org/browse/RF-9324?page=com.atlassian.jira.plugin.sy...
]
Jack Frosch commented on RF-9324:
---------------------------------
Sorry to comment twice on this. I had made multiple attempts to get the a4j:queue
oncomplete to fire after upgrading to 4.0.0, but without success. The workaround that I
cited above seemed to work, but after redeploying my app and restarting my server, I found
it's not working now. :(
a4j:queue event handlers doesn't work at all
--------------------------------------------
Key: RF-9324
URL:
https://issues.jboss.org/browse/RF-9324
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.0.0.Milestone2
Environment: Java(TM) SE Runtime Environment 1.6.0_20-b02
Linux 2.6.31-22-generic
Mojarra 2.0.2-FCS
Firefox 3.6.3
Apache Tomcat 6.0.26
core-demo : M2
https://repository.jboss.org/nexus/content/groups/public/org/richfaces/ex...
http://localhost:8080/core-demo/queue.jsf
Reporter: Lukáš Fryč
Assignee: Ilya Shaikovsky
Fix For: 4.Future
I modified queue.html sample to look like this:
<a4j:queue requestDelay="500" oncomplete="alert('1')"
/>
<h:form>
<h:commandLink value="Common link">
<a4j:ajax />
</h:commandLink>
</h:form>
It seems queue is working, because it handles multiple events and triggers only one
request, but alert is not shown on completion.
The same for all other event handlers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira