[ https://issues.jboss.org/browse/RF-10885?page=com.atlassian.jira.plugin.s... ] Nick Belaevski commented on RF-10885: ------------------------------------- Adrian, I cannot reproduce the problem using the following page code: {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/output"> <h:head></h:head> <h:body> <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" /> </h:commandLink> </h:form> </h:body> </ui:composition>{noformat} Can you please post page code? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-10885?page=com.atlassian.jira.plugin.s... ] Adrian Meredith edited comment on RF-10885 at 4/14/11 6:45 AM: --------------------------------------------------------------- Thanks for trying this so quickly, the page is too complex to show here (we have our own datatable component and modalwindow component ) I would have expected that to show the same symptoms. I'll try it to. In my program i have two composite components a datatable and a modal window. when progressbar is placed in the datatable the modalwindow no longer closes as onevent is never called. Removing progress bar restores the functionality. the save button looks like this {code:xml} <h:commandButton style="float: right;" id="save" rendered="#{(cc.attrs.noExit eq false) and !cc.attrs.javascriptSaveButton}" onclick="$(this).removeClass().addClass('ui-state-default ui-corner-all ui-button modalwindow_save ui-state-disabled');$(this).attr('disabled', true);" value="#{cc.attrs.saveButtonText}" action="#{cc.attrs.modaldatabean.save}" type="button" styleClass="modalwindow_save button ui-button ui-corner-all ui-state-default"> <f:ajax execute="#{cc.attrs.execute}" render="#{cc.attrs.render}"/> <f:ajax execute="@none" render="@none" oneerror="doValidateMessages"/> <f:ajax execute="@none" render="#{cc.attrs.update}" onevent="#{cc.attrs.onevent}"/> </h:commandButton> for the purposes of this bug lets say there are two js functions like below <script type="text/javascript"> function doValidateMessages(data) { alert('Onevent fired! '+data.status); } function doValidateMessages2() { alert('Onevent fired!'); } </script> {code} when the save button is pressed I get 3 alerts for each status like i would expect however when I add progress bar, no alert appears at all. In other words the contents of one composite component is breaking another! but it i rename the onevent to doValidateMessages2() i get one alert (surely i should still get 3?). Since my application already uses existing jquery I also have {code:xml} <script type="text/javascript"> jQuery.noConflict(); </script> {code} at the top of each page. was (Author: adriaaaaan): Thanks for trying this so quickly, the page is too complex to show here (we have our own datatable component and modalwindow component ) I would have expected that to show the same symptoms. I'll try it to. In my program i have two composite components a datatable and a modal window. when progressbar is placed in the datatable the modalwindow no longer closes as onevent is never called. Removing progress bar restores the functionality. the save button looks like this <h:commandButton style="float: right;" id="save" rendered="#{(cc.attrs.noExit eq false) and !cc.attrs.javascriptSaveButton}" onclick="$(this).removeClass().addClass('ui-state-default ui-corner-all ui-button modalwindow_save ui-state-disabled');$(this).attr('disabled', true);" value="#{cc.attrs.saveButtonText}" action="#{cc.attrs.modaldatabean.save}" type="button" styleClass="modalwindow_save button ui-button ui-corner-all ui-state-default"> <f:ajax execute="#{cc.attrs.execute}" render="#{cc.attrs.render}"/> <f:ajax execute="@none" render="@none" oneerror="doValidateMessages"/> <f:ajax execute="@none" render="#{cc.attrs.update}" onevent="#{cc.attrs.onevent}"/> </h:commandButton> for the purposes of this bug lets say there are two js functions like below <script type="text/javascript"> function doValidateMessages(data) { alert('Onevent fired! '+data.status); } function doValidateMessages2() { alert('Onevent fired!'); } </script> when the save button is pressed I get 3 alerts for each status like i would expect however when I add progress bar, no alert appears at all. In other words the contents of one composite component is breaking another! but it i rename the onevent to doValidateMessages2() i get one alert (surely i should still get 3?). Since my application already uses existing jquery I also have <script type="text/javascript"> jQuery.noConflict(); </script> at the top of each page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-10885?page=com.atlassian.jira.plugin.s... ] Adrian Meredith edited comment on RF-10885 at 4/14/11 6:46 AM: --------------------------------------------------------------- Thanks for trying this so quickly, the page is too complex to show here (we have our own datatable component and modalwindow component ) I would have expected that to show the same symptoms. I'll try it to. In my program i have two composite components a datatable and a modal window. when progressbar is placed in the datatable the modalwindow no longer closes as onevent is never called. Removing progress bar restores the functionality. the save button looks like this {code:xml} <h:commandButton style="float: right;" id="save"> <f:ajax execute="#{cc.attrs.execute}" render="#{cc.attrs.render}"/> <f:ajax execute="@none" render="@none" onevent="doValidateMessages"/> <f:ajax execute="@none" render="#{cc.attrs.update}" onevent="#{cc.attrs.onevent}"/> </h:commandButton> for the purposes of this bug lets say there are two js functions like below <script type="text/javascript"> function doValidateMessages(data) { alert('Onevent fired! '+data.status); } function doValidateMessages2() { alert('Onevent fired!'); } </script> {code} when the save button is pressed I get 3 alerts for each status like i would expect however when I add progress bar, no alert appears at all. In other words the contents of one composite component is breaking another! but it i rename the onevent to doValidateMessages2() i get one alert (surely i should still get 3?). Since my application already uses existing jquery I also have {code:xml} <script type="text/javascript"> jQuery.noConflict(); </script> {code} at the top of each page. was (Author: adriaaaaan): Thanks for trying this so quickly, the page is too complex to show here (we have our own datatable component and modalwindow component ) I would have expected that to show the same symptoms. I'll try it to. In my program i have two composite components a datatable and a modal window. when progressbar is placed in the datatable the modalwindow no longer closes as onevent is never called. Removing progress bar restores the functionality. the save button looks like this {code:xml} <h:commandButton style="float: right;" id="save"> <f:ajax execute="#{cc.attrs.execute}" render="#{cc.attrs.render}"/> <f:ajax execute="@none" render="@none" oneerror="doValidateMessages"/> <f:ajax execute="@none" render="#{cc.attrs.update}" onevent="#{cc.attrs.onevent}"/> </h:commandButton> for the purposes of this bug lets say there are two js functions like below <script type="text/javascript"> function doValidateMessages(data) { alert('Onevent fired! '+data.status); } function doValidateMessages2() { alert('Onevent fired!'); } </script> {code} when the save button is pressed I get 3 alerts for each status like i would expect however when I add progress bar, no alert appears at all. In other words the contents of one composite component is breaking another! but it i rename the onevent to doValidateMessages2() i get one alert (surely i should still get 3?). Since my application already uses existing jquery I also have {code:xml} <script type="text/javascript"> jQuery.noConflict(); </script> {code} at the top of each page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-10885?page=com.atlassian.jira.plugin.s... ] 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-10885?page=com.atlassian.jira.plugin.s... ] Nick Belaevski resolved RF-10885. --------------------------------- Assignee: Nick Belaevski Resolution: Duplicate Issue -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira