[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...
]
Nick Belaevski commented on RF-10885:
-------------------------------------
Adrian,
Tried the following:
{noformat}<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich">
<h:head></h:head>
<h:body>
<script type="text/javascript">
jQuery.noConflict();
</script>
<h:form>
<rich:progressBar mode="client" />
<rich:progressBar mode="ajax" />
<script type="text/javascript">
function handler(event) {
alert('handler ' + event.status);
}
</script>
<h:commandLink value="Link">
<f:ajax onevent="handler" />
<f:ajax />
</h:commandLink>
</h:form>
</h:body>
</ui:composition>{noformat}
still not reproducible.
Can you please provide small example project that reproduces the issue?
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