[
https://issues.jboss.org/browse/RF-10885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595651#comment-12595651
]
Adrian Meredith commented on RF-10885:
--------------------------------------
Slightly adapted your example to look more like mine, removing the last f:ajax
makes the popup alerts appear.
> 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
> Attachments: richfacesbug.zip
>
>
> 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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
