[
https://issues.jboss.org/browse/RF-11711?page=com.atlassian.jira.plugin.s...
]
Stefan Risto commented on RF-11711:
-----------------------------------
In my case I have a status that I want to display ajax activity from multiple forms. Due
to my view structure it is located in on form, instead of the view.
a4j:status has the disadvantage, that it is tidly coupled to the view structure.
Now I tried to trigger the status component manually using its javascript functions that I
connected to the queues eventhandlers "onbegin" and "oncomplete" which
apparently are not implemented.
The workaround I came up with was to declare a second aj4:status on the view level that
triggers the a4j:status that I had to put in the form:
<a4j:status onstart="#{rich:component('statView')}.start();"
onstop="#rich:component('statView')}.stop();"/>
statView is the visible a4j:status indicator defined in a form (due to my layout
restrictions).
That did the trick for me, but it is not a nice solution...
For me a solution would be either to get a more flexible a4j:status or get the queue
events implemented. But that is probably more an issue of a4j:status instead of
a4j:queue.
a4j:queue - remove attributes onsubmit, oncomplete, onevent
-----------------------------------------------------------
Key: RF-11711
URL:
https://issues.jboss.org/browse/RF-11711
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.1.0.CR1
Reporter: Lukáš Fryč
Priority: Minor
Fix For: 4.3-Tracking
--
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