[richfaces-issues] [JBoss JIRA] Commented: (RF-10885) Using rich:progressBar on a page breaks f:ajax onevent
[
https://issues.jboss.org/browse/RF-10885?page=com.atlassian.jira.plugin.s...
]
Adrian Meredith commented on RF-10885:
--------------------------------------
Okay I know how to break it, in my code with your example in the middle of it. It breaks
whenever i have another f:ajax after the one with the event.
retry you example with this.
<h:commandLink value="Link">
<f:ajax onevent="handler" />
<f:ajax/>
</h:commandLink>
in my code if i alter the save button f:ajax to only have one it works..... This is less
than ideal as I use the multiple ajax's to have custome events fired after a
successful save has occurred
Using rich:progressBar on a page breaks f:ajax onevent
------------------------------------------------------
Key: RF-10885
URL: https://issues.jboss.org/browse/RF-10885
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-output
Affects Versions: 4.0.0.Final
Environment: glassfish 3.1 mojarra 2.1
Reporter: Adrian Meredith
Labels: backwardcompatibility, jsf2, richfaces4
When using rich:progress bar on a page onevent no longer functions the same way. When
using mojarra onevent takes the name of a js function that takes one parameter (data).
After inserting a rich component on the page onevent now requires attributes breaking
compatability with standard jsf (and introducing untold amount of unpredictable bugs).
mojarra :
<f:ajax onevent="doValidateMessages"/>
richfaces:
<f:ajax onevent="doValidateMessages()"/>
This means i have to use diffent syntax depending on whether i'm using richfaces on a
particular page!! This is already a well established jsf2 application so rewriting it
using the aforementioned workaround isn't very practical.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira