From issues at jboss.org Mon Jun 2 04:03:15 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:03:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972252#comment-12972252 ] Juraj H?ska commented on RF-13648: ---------------------------------- I have tried to reproduce the issue on this branch of Metamer: https://github.com/richfaces/richfaces-qa/tree/RF-13648 I *can not* reproduce it. When {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is true, submitted empty strings are coerced to the empty {{String}} according to the EL specification. See the [comment|https://issues.apache.org/bugzilla/show_bug.cgi?id=56522#c1] in the mentioned jasper issue. If {{Object}} type is used instead of {{String}}, then empty fields remains {{null}} as expected (however graph validator does not support Object properties). I have tried it both with graph validator and client side validation. Graph Validator files: * [facelet|https://github.com/richfaces/richfaces-qa/blob/e2cbfcc00937ede44b0d0ff5f955378da05452fd/metamer/application/src/main/webapp/components/richGraphValidator/RF-13648.xhtml] * [bean|https://github.com/richfaces/richfaces-qa/blob/e2cbfcc00937ede44b0d0ff5f955378da05452fd/metamer/application/src/main/java/org/richfaces/tests/metamer/bean/issues/rf13648/RF13648.java] CSV: * [facelet|https://github.com/richfaces/richfaces-qa/blob/e2cbfcc00937ede44b0d0ff5f955378da05452fd/metamer/application/src/main/webapp/components/richGraphValidator/RF-13648_2.xhtml] * [bean|https://github.com/richfaces/richfaces-qa/blob/e2cbfcc00937ede44b0d0ff5f955378da05452fd/metamer/application/src/main/java/org/richfaces/tests/metamer/bean/issues/rf13648/UserBean2.java] > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:09:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:09:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972253#comment-12972253 ] Juraj H?ska commented on RF-13648: ---------------------------------- [~tony.cramer] could you please provide more specific steps to reproduce (e.g. small maven project which demonstrates your issue) ? Without further information I think this is not a bug. > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Labels: waiting_on_user > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 04:09:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 2 Jun 2014 04:09:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13648: ----------------------------- Labels: waiting_on_user (was: ) > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Labels: waiting_on_user > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 05:47:16 2014 From: issues at jboss.org (Robin Pradel (JIRA)) Date: Mon, 2 Jun 2014 05:47:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972281#comment-12972281 ] Robin Pradel commented on RF-13018: ----------------------------------- I can confirm the NPE. When clicking on {{h:commandButton}} beside a {{a4j:commandButton}} it leads to a NPE because {{String source = paramMap.get(SOURCE_ID);}} is {{null}}. {code} java.lang.NullPointerException at org.richfaces.renderkit.AjaxCommandRendererBase.isSubmitted(AjaxCommandRendererBase.java:83) at org.richfaces.renderkit.AjaxCommandRendererBase.doDecode(AjaxCommandRendererBase.java:59) at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1181) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIForm.processDecodes(UIForm.java:225) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:933) at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) {code} > a4j:commandButton wrong actions performed > ----------------------------------------- > > Key: RF-13018 > URL: https://issues.jboss.org/browse/RF-13018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15 > Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9 > Reporter: Rob Hare > Assignee: Michal Petrov > Labels: 45x > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > Attachments: RF-13018.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired. > For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions. > {noformat} > > action="#{richBean.function1}" /> > action="#{richBean.function2}" /> > > {noformat} > Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 05:47:17 2014 From: issues at jboss.org (Robin Pradel (JIRA)) Date: Mon, 2 Jun 2014 05:47:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972282#comment-12972282 ] Robin Pradel commented on RF-13018: ----------------------------------- I can confirm the NPE. When clicking on {{h:commandButton}} beside a {{a4j:commandButton}} it leads to a NPE because {{String source = paramMap.get(SOURCE_ID);}} is {{null}}. {code} java.lang.NullPointerException at org.richfaces.renderkit.AjaxCommandRendererBase.isSubmitted(AjaxCommandRendererBase.java:83) at org.richfaces.renderkit.AjaxCommandRendererBase.doDecode(AjaxCommandRendererBase.java:59) at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1181) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIForm.processDecodes(UIForm.java:225) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:933) at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) {code} > a4j:commandButton wrong actions performed > ----------------------------------------- > > Key: RF-13018 > URL: https://issues.jboss.org/browse/RF-13018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15 > Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9 > Reporter: Rob Hare > Assignee: Michal Petrov > Labels: 45x > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > Attachments: RF-13018.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired. > For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions. > {noformat} > > action="#{richBean.function1}" /> > action="#{richBean.function2}" /> > > {noformat} > Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 05:53:17 2014 From: issues at jboss.org (Robin Pradel (JIRA)) Date: Mon, 2 Jun 2014 05:53:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972282#comment-12972282 ] Robin Pradel edited comment on RF-13018 at 6/2/14 5:53 AM: ----------------------------------------------------------- _deleted_ (jira took my comment twice) was (Author: r0bb3n): I can confirm the NPE. When clicking on {{h:commandButton}} beside a {{a4j:commandButton}} it leads to a NPE because {{String source = paramMap.get(SOURCE_ID);}} is {{null}}. {code} java.lang.NullPointerException at org.richfaces.renderkit.AjaxCommandRendererBase.isSubmitted(AjaxCommandRendererBase.java:83) at org.richfaces.renderkit.AjaxCommandRendererBase.doDecode(AjaxCommandRendererBase.java:59) at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1181) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIForm.processDecodes(UIForm.java:225) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:933) at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) {code} > a4j:commandButton wrong actions performed > ----------------------------------------- > > Key: RF-13018 > URL: https://issues.jboss.org/browse/RF-13018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15 > Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9 > Reporter: Rob Hare > Assignee: Michal Petrov > Labels: 45x > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > Attachments: RF-13018.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired. > For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions. > {noformat} > > action="#{richBean.function1}" /> > action="#{richBean.function2}" /> > > {noformat} > Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 05:57:16 2014 From: issues at jboss.org (Robin Pradel (JIRA)) Date: Mon, 2 Jun 2014 05:57:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972281#comment-12972281 ] Robin Pradel edited comment on RF-13018 at 6/2/14 5:56 AM: ----------------------------------------------------------- I can confirm the NPE. When clicking on {{h:commandButton}} beside a {{a4j:commandButton}} it leads to a NPE because {{String source = paramMap.get(SOURCE_ID);}} is {{null}}. {code} java.lang.NullPointerException at org.richfaces.renderkit.AjaxCommandRendererBase.isSubmitted(AjaxCommandRendererBase.java:83) at org.richfaces.renderkit.AjaxCommandRendererBase.doDecode(AjaxCommandRendererBase.java:59) at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1181) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIForm.processDecodes(UIForm.java:225) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:933) at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) {code} b.t.w. I am using {{4.3.6.Final}}. was (Author: r0bb3n): I can confirm the NPE. When clicking on {{h:commandButton}} beside a {{a4j:commandButton}} it leads to a NPE because {{String source = paramMap.get(SOURCE_ID);}} is {{null}}. {code} java.lang.NullPointerException at org.richfaces.renderkit.AjaxCommandRendererBase.isSubmitted(AjaxCommandRendererBase.java:83) at org.richfaces.renderkit.AjaxCommandRendererBase.doDecode(AjaxCommandRendererBase.java:59) at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:787) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1181) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIForm.processDecodes(UIForm.java:225) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1176) at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:933) at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:78) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) {code} > a4j:commandButton wrong actions performed > ----------------------------------------- > > Key: RF-13018 > URL: https://issues.jboss.org/browse/RF-13018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15 > Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9 > Reporter: Rob Hare > Assignee: Michal Petrov > Labels: 45x > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > Attachments: RF-13018.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired. > For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions. > {noformat} > > action="#{richBean.function1}" /> > action="#{richBean.function2}" /> > > {noformat} > Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 06:49:16 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 2 Jun 2014 06:49:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13651) Integration tests failing in chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13651: ---------------------------------- Assignee: Matej Novotny (was: Pavol Pitonak) > Integration tests failing in chrome > ----------------------------------- > > Key: RF-13651 > URL: https://issues.jboss.org/browse/RF-13651 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > The framework tests pass in phantomjs but some fail in chrome. > Resolution of this issue involves running and stabilizing the tests in all supported browsers. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 10:15:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 2 Jun 2014 10:15:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13653) Update component namespaces in 4.5 examples In-Reply-To: References: Message-ID: Michal Petrov created RF-13653: ---------------------------------- Summary: Update component namespaces in 4.5 examples Key: RF-13653 URL: https://issues.jboss.org/browse/RF-13653 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.5.0.Alpha3 Reporter: Michal Petrov Assignee: Michal Petrov With the exception of showcase, all examples use the r namespace, it needs to be changed back to a4j/rich. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 10:57:16 2014 From: issues at jboss.org (Tony Cramer (JIRA)) Date: Mon, 2 Jun 2014 10:57:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Cramer updated RF-13648: ----------------------------- Attachment: rf-demo.zip > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Labels: waiting_on_user > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 10:59:16 2014 From: issues at jboss.org (Tony Cramer (JIRA)) Date: Mon, 2 Jun 2014 10:59:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Cramer updated RF-13648: ----------------------------- Description: {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. Some debugging info: Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. This causes validation to not pass. Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. Tomcat bug or RF bug? Edit: It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 Edit: Simple project for reproducing the issue included (rf-demo.zip). - Build WAR with Maven (3.2.1 tested) - Get a clean Tomcat 8.0.8, unpack - Place WAR into webapps - Run tomcat - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT was: {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. Some debugging info: Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. This causes validation to not pass. Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. Tomcat bug or RF bug? Edit: It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Labels: waiting_on_user > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue included (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 10:59:17 2014 From: issues at jboss.org (Tony Cramer (JIRA)) Date: Mon, 2 Jun 2014 10:59:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Cramer updated RF-13648: ----------------------------- Description: {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. Some debugging info: Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. This causes validation to not pass. Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. Tomcat bug or RF bug? Edit: It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 Edit: Simple project for reproducing the issue attached (rf-demo.zip). - Build WAR with Maven (3.2.1 tested) - Get a clean Tomcat 8.0.8, unpack - Place WAR into webapps - Run tomcat - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT was: {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. Some debugging info: Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. This causes validation to not pass. Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. Tomcat bug or RF bug? Edit: It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 Edit: Simple project for reproducing the issue included (rf-demo.zip). - Build WAR with Maven (3.2.1 tested) - Get a clean Tomcat 8.0.8, unpack - Place WAR into webapps - Run tomcat - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Labels: waiting_on_user > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 11:01:18 2014 From: issues at jboss.org (Tony Cramer (JIRA)) Date: Mon, 2 Jun 2014 11:01:18 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972503#comment-12972503 ] Tony Cramer commented on RF-13648: ---------------------------------- Simple demo project attached. > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Labels: waiting_on_user > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 2 11:41:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 2 Jun 2014 11:41:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13653) Update component namespaces in 4.5 examples In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13653. -------------------------------- Fix Version/s: 4.5.0.Alpha3 Resolution: Done > Update component namespaces in 4.5 examples > ------------------------------------------- > > Key: RF-13653 > URL: https://issues.jboss.org/browse/RF-13653 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > With the exception of showcase, all examples use the r namespace, it needs to be changed back to a4j/rich. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 02:57:15 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 3 Jun 2014 02:57:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13654) Port photoalbum changes from 4.3.x In-Reply-To: References: Message-ID: Michal Petrov created RF-13654: ---------------------------------- Summary: Port photoalbum changes from 4.3.x Key: RF-13654 URL: https://issues.jboss.org/browse/RF-13654 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha4 Reporter: Michal Petrov Assignee: Michal Petrov -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 02:57:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 3 Jun 2014 02:57:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13654) Port photoalbum changes from 4.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13654: ------------------------------- Fix Version/s: 4.5.0.Alpha3 5.0.0.Alpha4 > Port photoalbum changes from 4.3.x > ---------------------------------- > > Key: RF-13654 > URL: https://issues.jboss.org/browse/RF-13654 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha4 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 04:33:15 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 3 Jun 2014 04:33:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13655) Popup Panel autosize does not work when its content is dynamically updated In-Reply-To: References: Message-ID: Juraj H?ska created RF-13655: -------------------------------- Summary: Popup Panel autosize does not work when its content is dynamically updated Key: RF-13655 URL: https://issues.jboss.org/browse/RF-13655 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.3.7 Reporter: Juraj H?ska When Popup Panel has dynamically rendered content, e.g. {{rich:dataTable}} with dynamically added rows, then its auto-size functionality cease to work. Please see the steps to reproduce. It is a regression against 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 05:28:44 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 3 Jun 2014 05:28:44 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13655) Popup Panel autosize does not work when its content is dynamically updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972737#comment-12972737 ] Michal Petrov commented on RF-13655: ------------------------------------ Note that in 4.3.6 the auto-resizing was done by browser - i.e. there is no code being executed - and it doesn't resize the panel shadow so we can't simply go back to that. In 4.3.7 we opted for assigning a fixed width so it doesn't change if the content changes (though it works fine for RF-13616). > Popup Panel autosize does not work when its content is dynamically updated > -------------------------------------------------------------------------- > > Key: RF-13655 > URL: https://issues.jboss.org/browse/RF-13655 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Juraj H?ska > Labels: regression > > When Popup Panel has dynamically rendered content, e.g. {{rich:dataTable}} with dynamically added rows, then its auto-size functionality cease to work. > Please see the steps to reproduce. It is a regression against 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 05:52:16 2014 From: issues at jboss.org (=?UTF-8?Q?Andr=C3=A9_Faber_=28JIRA=29?=) Date: Tue, 3 Jun 2014 05:52:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: Andr? Faber created RF-13656: -------------------------------- Summary: Table collapse after tab change Key: RF-13656 URL: https://issues.jboss.org/browse/RF-13656 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.7 Reporter: Andr? Faber I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 05:54:17 2014 From: issues at jboss.org (=?UTF-8?Q?Andr=C3=A9_Faber_=28JIRA=29?=) Date: Tue, 3 Jun 2014 05:54:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andr? Faber closed RF-13656. ---------------------------- Resolution: Done > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: 4.3.7, colapse, rich:extenedDataTable, rich:tabPanel, richfaces > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 06:04:15 2014 From: issues at jboss.org (=?UTF-8?Q?Andr=C3=A9_Faber_=28JIRA=29?=) Date: Tue, 3 Jun 2014 06:04:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andr? Faber reopened RF-13656: ------------------------------ > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: 4.3.7, colapse, rich:extenedDataTable, rich:tabPanel, richfaces > Attachments: screenshot-1.jpg > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 06:04:16 2014 From: issues at jboss.org (=?UTF-8?Q?Andr=C3=A9_Faber_=28JIRA=29?=) Date: Tue, 3 Jun 2014 06:04:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andr? Faber updated RF-13656: ----------------------------- Attachment: screenshot-1.jpg At the begin all looks good > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: 4.3.7, colapse, rich:extenedDataTable, rich:tabPanel, richfaces > Attachments: screenshot-1.jpg > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 06:06:16 2014 From: issues at jboss.org (=?UTF-8?Q?Andr=C3=A9_Faber_=28JIRA=29?=) Date: Tue, 3 Jun 2014 06:06:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andr? Faber updated RF-13656: ----------------------------- Attachment: screenshot-2.jpg After changing the tab, the table is "collapsed" (also if I switch back, the other table is shown the same way) > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: 4.3.7, colapse, rich:extenedDataTable, rich:tabPanel, richfaces > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 08:20:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 3 Jun 2014 08:20:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13648: ----------------------------- Labels: (was: waiting_on_user) > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 08:30:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 3 Jun 2014 08:30:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972814#comment-12972814 ] Juraj H?ska commented on RF-13648: ---------------------------------- Thank you [~tony.cramer] for the reproducer. However, I need to repeat my previous conclusion. The behavior is expected, and it is defined in EL specification. It worked prior Tomcat 8.0.8 because there was a [bug|https://issues.apache.org/bugzilla/show_bug.cgi?id=56522#c1] in jasper, which is now fixed and meets the EL spec. There is an [issue|https://java.net/jira/browse/EL_SPEC-18] filed for EL spec though, which should address your problem. This is not a RichFaces bug. > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 08:30:17 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 3 Jun 2014 08:30:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska resolved RF-13648. ------------------------------ Resolution: Rejected > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 08:32:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 3 Jun 2014 08:32:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972815#comment-12972815 ] Juraj H?ska commented on RF-13648: ---------------------------------- You can workaround the problem in your example project for example by altering the setter method for the {{swift}} bean property, like: {code} public void setSwiftCode(String swiftCode) { if(swiftCode == null || swiftCode.isEmpty()) { this.swiftCode = null; } else { this.swiftCode = swiftCode; } } {code} > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 08:32:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 3 Jun 2014 08:32:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972815#comment-12972815 ] Juraj H?ska edited comment on RF-13648 at 6/3/14 8:31 AM: ---------------------------------------------------------- You can workaround the problem in your example project for example by altering the setter method for the {{swift}} bean property, like: {code} public void setSwiftCode(String swiftCode) { if(swiftCode == null || swiftCode.isEmpty()) { this.swiftCode = null; } else { this.swiftCode = swiftCode; } } {code} was (Author: jhuska): You can workaround the problem in your example project for example by altering the setter method for the {{swift}} bean property, like: {code} public void setSwiftCode(String swiftCode) { if(swiftCode == null || swiftCode.isEmpty()) { this.swiftCode = null; } else { this.swiftCode = swiftCode; } } {code} > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 10:34:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 10:34:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13654) Port photoalbum changes from 4.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13654: ------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > Port photoalbum changes from 4.3.x > ---------------------------------- > > Key: RF-13654 > URL: https://issues.jboss.org/browse/RF-13654 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha4 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 10:34:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 10:34:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13654) Port photoalbum changes from 4.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13654: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 3 > Port photoalbum changes from 4.3.x > ---------------------------------- > > Key: RF-13654 > URL: https://issues.jboss.org/browse/RF-13654 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha4 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 10:34:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 10:34:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12950) Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12950: ------------------------------- Fix Version/s: 4.5.0.Beta1 (was: 4.5.0.Alpha3) > Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests > ------------------------------------------------------------------------------------------------------ > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Juraj H?ska > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 11:10:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 11:10:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13648) Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972881#comment-12972881 ] Brian Leathem commented on RF-13648: ------------------------------------ Nice work [~jhuska]! > Graph Validator + Tomcat 8.0.8: interpret empty strings as null is ignored > -------------------------------------------------------------------------- > > Key: RF-13648 > URL: https://issues.jboss.org/browse/RF-13648 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64 > Reporter: Tony Cramer > Assignee: Juraj H?ska > Attachments: rf-demo.zip > > > {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph validating. > Some debugging info: > Object being validated ({{value}} argument) in method {{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings (""). > Expected behavior: There should be nulls in properties, because interpreting empty strings as null is enabled. > This causes validation to not pass. > Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5. If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works. > Tomcat bug or RF bug? > Edit: > It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec. > https://issues.apache.org/bugzilla/show_bug.cgi?id=56522 > Edit: > Simple project for reproducing the issue attached (rf-demo.zip). > - Build WAR with Maven (3.2.1 tested) > - Get a clean Tomcat 8.0.8, unpack > - Place WAR into webapps > - Run tomcat > - Open http://localhost:8080/rf-demo-1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 11:12:16 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 3 Jun 2014 11:12:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13657) Remove bootstrap and font-awesome from 4.5 In-Reply-To: References: Message-ID: Pavol Pitonak created RF-13657: ---------------------------------- Summary: Remove bootstrap and font-awesome from 4.5 Key: RF-13657 URL: https://issues.jboss.org/browse/RF-13657 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: client-lib Affects Versions: 4.5.0.Alpha2 Reporter: Pavol Pitonak Remove bootstrap and font-awesome from RichFaces 4.5.x branch: * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 11:16:19 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 11:16:19 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13655) Popup Panel autosize does not work when its content is dynamically updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972885#comment-12972885 ] Brian Leathem commented on RF-13655: ------------------------------------ Prioir to 4.3.6, that resize only worked before the popup was moved. After it was moved the popup was no longer resized automatically (that was RF-13616 the original issue we were trying to address). In resolving that issue, the popupPanel was augmented to listen for resize events of it's children and re-calculate it's width. We should be able to resolve this issue by having the dataTable trigger a resize event as appropriate. A workaround would be for the user to fire a resize even on a div within the popupPanel. > Popup Panel autosize does not work when its content is dynamically updated > -------------------------------------------------------------------------- > > Key: RF-13655 > URL: https://issues.jboss.org/browse/RF-13655 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.3.8 > > > When Popup Panel has dynamically rendered content, e.g. {{rich:dataTable}} with dynamically added rows, then its auto-size functionality cease to work. > Please see the steps to reproduce. It is a regression against 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 11:16:19 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 11:16:19 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13655) Popup Panel autosize does not work when its content is dynamically updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13655: ------------------------------- Fix Version/s: 4.3.8 > Popup Panel autosize does not work when its content is dynamically updated > -------------------------------------------------------------------------- > > Key: RF-13655 > URL: https://issues.jboss.org/browse/RF-13655 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.3.8 > > > When Popup Panel has dynamically rendered content, e.g. {{rich:dataTable}} with dynamically added rows, then its auto-size functionality cease to work. > Please see the steps to reproduce. It is a regression against 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 11:18:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 11:18:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972886#comment-12972886 ] Brian Leathem commented on RF-13656: ------------------------------------ [~mundi] would you please provide some simple-as-possible sample code we can use to reproduce this issue? > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: waiting_on_user > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 11:18:17 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 11:18:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13656: ------------------------------- Component/s: component-output > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: waiting_on_user > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 11:18:18 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 11:18:18 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13656: ------------------------------- Labels: waiting_on_user (was: 4.3.7 colapse rich:extenedDataTable rich:tabPanel richfaces) > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: waiting_on_user > Attachments: screenshot-1.jpg, screenshot-2.jpg > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 11:20:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 11:20:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13657) Remove bootstrap and font-awesome from 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13657: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes Fix Version/s: 4.5.0.Alpha3 Assignee: Michal Petrov Sprint: 4.5.0.Alpha3 - Sprint 3 > Remove bootstrap and font-awesome from 4.5 > ------------------------------------------ > > Key: RF-13657 > URL: https://issues.jboss.org/browse/RF-13657 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: client-lib > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Remove bootstrap and font-awesome from RichFaces 4.5.x branch: > * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf > * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf > * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 11:20:17 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 11:20:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13018) a4j:commandButton wrong actions performed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13018: ------------------------------- Comment: was deleted (was: _deleted_ (jira took my comment twice)) > a4j:commandButton wrong actions performed > ----------------------------------------- > > Key: RF-13018 > URL: https://issues.jboss.org/browse/RF-13018 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Environment: Server: Fedora 17, Jboss AS 7.1.1.Final, Jboss EAP 6.1.0.Beta, Java 1.7.0_15 > Browsers: Chrome 26 and Chrome 27 on (Linux & Windows 7), Firefox 20.0 (Linux & Windows 7), IE 9 > Reporter: Rob Hare > Assignee: Michal Petrov > Labels: 45x > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > Attachments: RF-13018.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When an a4j commponent (a4j:commandButton, a4j:jsFunction) is activated, actions of other a4j:commandButtons on the page with type=button will be fired. > For example, pressing either button in the following code will cause both richBean.function1() and richBean.function2() actions. > {noformat} > > action="#{richBean.function1}" /> > action="#{richBean.function2}" /> > > {noformat} > Note, if one of the a4j:commandButton is marked immediate, then only one action (possibly the wrong action) will be performed and block others. For instance if an a4j:jsFunction action was being triggered, the a4j:commandButton action may occur making appear that the a4j:jsFunction failed. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 20:16:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 20:16:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973073#comment-12973073 ] Brian Leathem commented on RF-13652: ------------------------------------ Creating an uber-patch with every commit from the RF 4.3/4.5 fork to HEAD proved unsuccessful, as the patch application mechanism does not fail gracefully when patch has already been applied. > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 3 20:18:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 3 Jun 2014 20:18:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973074#comment-12973074 ] Brian Leathem commented on RF-13652: ------------------------------------ A second attempt at resolving this issue centred around synchronizing the (appropriately mapped) RF 4.3 files to their RF 4.5 counterparts. This proved unsuccessful as the rf 4.3 and 4.5 code-bases have sufficiently diverged (eg. attribute interfaces) such that the resulting diff was too large to make sense of. > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 05:00:15 2014 From: issues at jboss.org (Jonathan Bullock (JIRA)) Date: Wed, 4 Jun 2014 05:00:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-9922) Whitespace issue in Suggestion box In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-9922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973154#comment-12973154 ] Jonathan Bullock commented on RF-9922: -------------------------------------- I've just recently come across this same issue in 3.3.4.Final and after some research this seems to be a bug in the Tidy parser, a workaround is to use the Neko parser instead: http://docs.jboss.org/richfaces/latest_3_3_X/en/devguide/html/ArchitectureOverview.html#FilterConfiguration > Whitespace issue in Suggestion box > ---------------------------------- > > Key: RF-9922 > URL: https://issues.jboss.org/browse/RF-9922 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.2.GA > Environment: JBOSS 4.2.* > Reporter: thirunavukkarasu kirubanandam > Fix For: 3.Future > > > rich:suggestion box trims the multiple whitespaces to a single whitespace between words. e.g. In search pages if we want to search for john smith, suggestion box lists with john smith with single whitespace between words. Search fails due to this. Tried using the solution given in this forum(using pre tag). The list displays the name John Smith with multiple white space characters. On selection of the item the selected data the multiple white space characters gets trimmed to single white space character. Because of this the right set of data is not retrieved. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 07:52:15 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 4 Jun 2014 07:52:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13654) Port photoalbum changes from 4.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13654. -------------------------------- Resolution: Done > Port photoalbum changes from 4.3.x > ---------------------------------- > > Key: RF-13654 > URL: https://issues.jboss.org/browse/RF-13654 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha4 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 08:04:16 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Jun 2014 08:04:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12132) Richfaces queue not cleared after js error in oncomplete attribute In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-12132. ---------------------------- Verified. Metamer test created. > Richfaces queue not cleared after js error in oncomplete attribute > ------------------------------------------------------------------ > > Key: RF-12132 > URL: https://issues.jboss.org/browse/RF-12132 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final, 4.3.7 > Environment: Myfaces 2.1.6 > Tomcat 6.0.35 > Reporter: Michael Heinen > Assignee: Michal Petrov > Labels: gss > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > > Richfaces queue not cleared after js-error in oncomplete attribute > Submit a with oncomplete="myNotExistingFuncrtion();" > The ajax response arrives but the queue is not cleaned up after this due to the javascript error > Starting from now no further ajax requests are possible because richfaces waits for previous submit results. > Sample from the richfaces log: > {code} > debug[17:10:10.587]: New request added to queue. Queue requestGroupingId changed to j_id_5:j_id_b > debug[17:10:10.615]: Queue will wait 0ms before submit > debug[17:10:10.644]: richfaces.queue: will submit request NOW > info [17:10:10.671]: Received 'begin' event from > info [17:10:10.707]: Received 'beforedomupdate' event from > debug[17:10:10.729]: Server returned responseText: Content List: []]]>myNotExistingFuncrtion();; > info [17:10:10.758]: Listing content of response changes element: > Element update for id=j_id_5:details > Content List: []]]> > Element update for id=javax.faces.ViewState > > Element extension for id=org.richfaces.extension > myNotExistingFuncrtion();; > debug[17:10:19.143]: New request added to queue. Queue requestGroupingId changed to j_id_5:j_id_a > debug[17:10:19.171]: Queue will wait 0ms before submit > debug[17:10:19.201]: richfaces.queue: Waiting for previous submit results > {code} > A request without javascript error ends with: > {code} > debug[17:20:22.033]: richfaces.queue: ajax submit successfull > debug[17:20:22.075]: richfaces.queue: Nothing to submit > info [17:20:22.117]: Received 'success' event from > info [17:20:22.155]: Received 'complete' event from > {code} > I expect that the queue is cleaned up independent of javascript errors during oncomplete. > Otherwise applications are not useable anymore. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 08:16:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 4 Jun 2014 08:16:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13657) Remove bootstrap, font-awesome and richwidgets from 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13657: ------------------------------- Summary: Remove bootstrap, font-awesome and richwidgets from 4.5 (was: Remove bootstrap and font-awesome from 4.5) > Remove bootstrap, font-awesome and richwidgets from 4.5 > ------------------------------------------------------- > > Key: RF-13657 > URL: https://issues.jboss.org/browse/RF-13657 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: client-lib > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Remove bootstrap and font-awesome from RichFaces 4.5.x branch: > * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf > * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf > * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 08:18:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 4 Jun 2014 08:18:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13657) Remove bootstrap, font-awesome and richwidgets from 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13657: ------------------------------- Description: Remove bootstrap and font-awesome from RichFaces 4.5.x branch: * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css * core/src/main/js/bower.json * core/src/main/js/Gruntfile.js * core/src/main/js/package.json * core/src/main/README.adoc was: Remove bootstrap and font-awesome from RichFaces 4.5.x branch: * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css > Remove bootstrap, font-awesome and richwidgets from 4.5 > ------------------------------------------------------- > > Key: RF-13657 > URL: https://issues.jboss.org/browse/RF-13657 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: client-lib > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Remove bootstrap and font-awesome from RichFaces 4.5.x branch: > * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf > * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf > * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css > * core/src/main/js/bower.json > * core/src/main/js/Gruntfile.js > * core/src/main/js/package.json > * core/src/main/README.adoc -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 08:18:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 4 Jun 2014 08:18:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13657) Remove bootstrap, font-awesome and richwidgets from 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13657: ------------------------------- Description: Remove bootstrap and font-awesome from RichFaces 4.5.x branch: * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css * core/src/main/js/bower.json * core/src/main/js/Gruntfile.js * core/src/main/js/package.json * core/src/main/js/README.adoc was: Remove bootstrap and font-awesome from RichFaces 4.5.x branch: * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css * core/src/main/js/bower.json * core/src/main/js/Gruntfile.js * core/src/main/js/package.json * core/src/main/README.adoc > Remove bootstrap, font-awesome and richwidgets from 4.5 > ------------------------------------------------------- > > Key: RF-13657 > URL: https://issues.jboss.org/browse/RF-13657 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: client-lib > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Remove bootstrap and font-awesome from RichFaces 4.5.x branch: > * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf > * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf > * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css > * core/src/main/js/bower.json > * core/src/main/js/Gruntfile.js > * core/src/main/js/package.json > * core/src/main/js/README.adoc -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 08:22:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 4 Jun 2014 08:22:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13657) Remove bootstrap, font-awesome and richwidgets from 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973231#comment-12973231 ] Michal Petrov commented on RF-13657: ------------------------------------ I've found some remaining code for RichWidgets, will remove that as well. The fileUpload progressbar was using bootstrap but I've copied the necessary styles over to fileupload.ecss. > Remove bootstrap, font-awesome and richwidgets from 4.5 > ------------------------------------------------------- > > Key: RF-13657 > URL: https://issues.jboss.org/browse/RF-13657 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: client-lib > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Remove bootstrap and font-awesome from RichFaces 4.5.x branch: > * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf > * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf > * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css > * core/src/main/js/bower.json > * core/src/main/js/Gruntfile.js > * core/src/main/js/package.json > * core/src/main/js/README.adoc -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 08:32:15 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 4 Jun 2014 08:32:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13657) Remove bootstrap, font-awesome and richwidgets from 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13657. -------------------------------- Resolution: Done > Remove bootstrap, font-awesome and richwidgets from 4.5 > ------------------------------------------------------- > > Key: RF-13657 > URL: https://issues.jboss.org/browse/RF-13657 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: client-lib > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Remove bootstrap and font-awesome from RichFaces 4.5.x branch: > * core/src/main/resources/META-INF/resources/bootstrap/bootstrap.css > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.woff > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.eot > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.svg > * core/src/main/resources/META-INF/resources/font-awesome/font/fontawesome-webfont.ttf > * core/src/main/resources/META-INF/resources/font-awesome/font/FontAwesome.otf > * core/src/main/resources/META-INF/resources/font-awesome/font-awesome.css > * core/src/main/js/bower.json > * core/src/main/js/Gruntfile.js > * core/src/main/js/package.json > * core/src/main/js/README.adoc -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 09:18:16 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 4 Jun 2014 09:18:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12132) Richfaces queue not cleared after js error in oncomplete attribute In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973262#comment-12973262 ] Pavol Pitonak commented on RF-12132: ------------------------------------ [~jstefek], can you confirm that all tests are passing, i.e. it doesn't cause any regression in ajax-enabled components? > Richfaces queue not cleared after js error in oncomplete attribute > ------------------------------------------------------------------ > > Key: RF-12132 > URL: https://issues.jboss.org/browse/RF-12132 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final, 4.3.7 > Environment: Myfaces 2.1.6 > Tomcat 6.0.35 > Reporter: Michael Heinen > Assignee: Michal Petrov > Labels: gss > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > > Richfaces queue not cleared after js-error in oncomplete attribute > Submit a with oncomplete="myNotExistingFuncrtion();" > The ajax response arrives but the queue is not cleaned up after this due to the javascript error > Starting from now no further ajax requests are possible because richfaces waits for previous submit results. > Sample from the richfaces log: > {code} > debug[17:10:10.587]: New request added to queue. Queue requestGroupingId changed to j_id_5:j_id_b > debug[17:10:10.615]: Queue will wait 0ms before submit > debug[17:10:10.644]: richfaces.queue: will submit request NOW > info [17:10:10.671]: Received 'begin' event from > info [17:10:10.707]: Received 'beforedomupdate' event from > debug[17:10:10.729]: Server returned responseText: Content List: []]]>myNotExistingFuncrtion();; > info [17:10:10.758]: Listing content of response changes element: > Element update for id=j_id_5:details > Content List: []]]> > Element update for id=javax.faces.ViewState > > Element extension for id=org.richfaces.extension > myNotExistingFuncrtion();; > debug[17:10:19.143]: New request added to queue. Queue requestGroupingId changed to j_id_5:j_id_a > debug[17:10:19.171]: Queue will wait 0ms before submit > debug[17:10:19.201]: richfaces.queue: Waiting for previous submit results > {code} > A request without javascript error ends with: > {code} > debug[17:20:22.033]: richfaces.queue: ajax submit successfull > debug[17:20:22.075]: richfaces.queue: Nothing to submit > info [17:20:22.117]: Received 'success' event from > info [17:20:22.155]: Received 'complete' event from > {code} > I expect that the queue is cleaned up independent of javascript errors during oncomplete. > Otherwise applications are not useable anymore. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 09:18:16 2014 From: issues at jboss.org (=?UTF-8?Q?Andr=C3=A9_Faber_=28JIRA=29?=) Date: Wed, 4 Jun 2014 09:18:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andr? Faber updated RF-13656: ----------------------------- Attachment: TestBean.java test.xhtml > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: waiting_on_user > Attachments: screenshot-1.jpg, screenshot-2.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 09:22:15 2014 From: issues at jboss.org (=?UTF-8?Q?Andr=C3=A9_Faber_=28JIRA=29?=) Date: Wed, 4 Jun 2014 09:22:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andr? Faber updated RF-13656: ----------------------------- Attachment: screenshot-3.jpg > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: waiting_on_user > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 09:22:16 2014 From: issues at jboss.org (=?UTF-8?Q?Andr=C3=A9_Faber_=28JIRA=29?=) Date: Wed, 4 Jun 2014 09:22:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andr? Faber updated RF-13656: ----------------------------- Attachment: screenshot-4.jpg > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: waiting_on_user > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 09:24:16 2014 From: issues at jboss.org (=?UTF-8?Q?Andr=C3=A9_Faber_=28JIRA=29?=) Date: Wed, 4 Jun 2014 09:24:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973270#comment-12973270 ] Andr? Faber commented on RF-13656: ---------------------------------- I've added some simple code and new screenshots. Another strange thing is that if I switch back (in my example) from the second to the first tab everything is fine again until I reload the page and change to the second tab again. > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Labels: waiting_on_user > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 10:20:19 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 4 Jun 2014 10:20:19 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12132) Richfaces queue not cleared after js error in oncomplete attribute In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973313#comment-12973313 ] Ji?? ?tefek commented on RF-12132: ---------------------------------- [~ppitonak], I can confirm that whole Metamer tests suite with RF 4.3.x on EAP 6.3 is passing. I'll recheck the other branches. > Richfaces queue not cleared after js error in oncomplete attribute > ------------------------------------------------------------------ > > Key: RF-12132 > URL: https://issues.jboss.org/browse/RF-12132 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.0.Final, 4.3.7 > Environment: Myfaces 2.1.6 > Tomcat 6.0.35 > Reporter: Michael Heinen > Assignee: Michal Petrov > Labels: gss > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > > Richfaces queue not cleared after js-error in oncomplete attribute > Submit a with oncomplete="myNotExistingFuncrtion();" > The ajax response arrives but the queue is not cleaned up after this due to the javascript error > Starting from now no further ajax requests are possible because richfaces waits for previous submit results. > Sample from the richfaces log: > {code} > debug[17:10:10.587]: New request added to queue. Queue requestGroupingId changed to j_id_5:j_id_b > debug[17:10:10.615]: Queue will wait 0ms before submit > debug[17:10:10.644]: richfaces.queue: will submit request NOW > info [17:10:10.671]: Received 'begin' event from > info [17:10:10.707]: Received 'beforedomupdate' event from > debug[17:10:10.729]: Server returned responseText: Content List: []]]>myNotExistingFuncrtion();; > info [17:10:10.758]: Listing content of response changes element: > Element update for id=j_id_5:details > Content List: []]]> > Element update for id=javax.faces.ViewState > > Element extension for id=org.richfaces.extension > myNotExistingFuncrtion();; > debug[17:10:19.143]: New request added to queue. Queue requestGroupingId changed to j_id_5:j_id_a > debug[17:10:19.171]: Queue will wait 0ms before submit > debug[17:10:19.201]: richfaces.queue: Waiting for previous submit results > {code} > A request without javascript error ends with: > {code} > debug[17:20:22.033]: richfaces.queue: ajax submit successfull > debug[17:20:22.075]: richfaces.queue: Nothing to submit > info [17:20:22.117]: Received 'success' event from > info [17:20:22.155]: Received 'complete' event from > {code} > I expect that the queue is cleaned up independent of javascript errors during oncomplete. > Otherwise applications are not useable anymore. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 10:48:17 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 4 Jun 2014 10:48:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: Michal Petrov created RF-13658: ---------------------------------- Summary: Component issues in 4.5 Key: RF-13658 URL: https://issues.jboss.org/browse/RF-13658 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5.0.Alpha3 Reporter: Michal Petrov Fix For: 4.5.0.Alpha3 I've checked showcase and photoalbum and discovered several issues: * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} ** this completely breaks photoalbum * data retrieval from server doesn't seem to work (there are no errors on either server or client) ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) ** extendedDataTable with enabled ajax loading does not load any data ** progressbar does not work ** togglePanel does not switch ** dynamic tabPanels do not switch ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 13:46:16 2014 From: issues at jboss.org (Alexandre Palmeira (JIRA)) Date: Wed, 4 Jun 2014 13:46:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11280) showcase - rich:autocomplete - samples Autocompletion Modes, Custom Popup Layouts - it does not work when it is in Ajax or lazy mode on IE9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973437#comment-12973437 ] Alexandre Palmeira commented on RF-11280: ----------------------------------------- The problem persists, I'm using IE 11.09600.17017. The problem occurs on my system and on demo: http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=autocomplete&sample=clientFilter&skin=blueSky > showcase - rich:autocomplete - samples Autocompletion Modes, Custom Popup Layouts - it does not work when it is in Ajax or lazy mode on IE9 > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11280 > URL: https://issues.jboss.org/browse/RF-11280 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Milestone1 > Environment: richfaces-showcase-4.1.0.20110805-M1-jee6.war > container - JBoss AS 6.0.0.Final > browser - IE 9 > Reporter: Juraj H?ska > Labels: ie9_normal_jq151 > > When rich:autocomplete is in Ajax or lazy client mode it does not show any suggestions. It works fine when it is in client mode. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 13:54:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Jun 2014 13:54:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973439#comment-12973439 ] Brian Leathem commented on RF-13652: ------------------------------------ A third attempt at resolving this issue involves looking at the commit history of the two branches since they forked, and identifying which jira issues are fixed in 4.3 but not in 4.5. The list of 4.3 commits was retrieved using the command (for the components repository): {code} git rev-list --pretty=oneline 4.3.7.20140523-Final ^4.3.2.20130513-Final {code} The list of 4.5 commits was retrieved with the command: {code} git rev-list --pretty=oneline 4.5.x ^4.5.x-START~1 ^2d7f107eeb3e8a22b6084935ccab8a9cd6b38665 ^4791fe039c27d3826cb5ec89d133fdf3efd9576b ^b32deba90c1a423bd3f58e773b7fc0d4ee8f1a87 ^f0e8896471bafb0c84ac50589cf72726e6da5b90 ^c851c22d9c638509fce2c42c8eb615b8ff59f771 {code} Comparing the two commit lists shows: || Fixed in RF43 || Fixed in both || Fixed in RF45 || | | | RF-11275 | | RF-11417 | | | | RF-11469 | | | | RF-11691 | | | | | | RF-11736 | | | | RF-11973 | | | RF-12132 | | | | RF-12214 | | | | RF-12224 | | | RF-12345 | | | | | | RF-12675 | | RF-12741 | | | | | RF-12765 | | | | RF-12784 | | | | RF-12786 | | | | | RF-12813 | | | RF-12843 | | | | RF-12849 | | | | | RF-12850 | | | | RF-12853 | | RF-12929 | | | | | RF-12933 | | | | RF-12940 | | | | RF-12941 | | | | | RF-12943 | | | RF-12964 | | | RF-12975 | | | | | | RF-12989 | | | | RF-13010 | | | | RF-13018 | | | RF-13027 | | | | | RF-13038 | | | | RF-13046 | | | RF-13053 | | | | | RF-13060 | | | RF-13078 | | | | | RF-13087 | | | RF-13090 | | | | | RF-13094 | | | | RF-13095 | | | RF-13097 | | | | | RF-13102 | | | | RF-13107 | | | RF-13114 | | | | | RF-13117 | | | | RF-13125 | | | | RF-13133 | | | | RF-13136 | | | | RF-13137 | | | | RF-13140 | | | RF-13147 | | | | RF-13150 | | | RF-13155 | | | | | RF-13160 | | | | | RF-13161 | | RF-13172 | | | | | RF-13186 | | | RF-13189 | | | | RF-13208 | | | | | RF-13210 | | | | RF-13213 | | | | RF-13214 | | | | RF-13223 | | | | RF-13224 | | | | RF-13229 | | | | | RF-13239 | | | RF-13265 | | | RF-13277 | | | | | RF-13278 | | | | RF-13280 | | | | RF-13282 | | | | | RF-13287 | | RF-13292 | | | | RF-13305 | | | | RF-13306 | | | | | | RF-13314 | | | RF-13330 | | | | RF-13334 | | | | | RF-13358 | | | RF-13362 | | | | RF-13374 | | | | RF-13394 | | | | RF-13395 | | | RF-13453 | | | | | | RF-13455 | | | RF-13472 | | | RF-13478 | | | | | RF-13494 | | | | RF-13495 | | | | RF-13496 | | | | RF-13505 | | | | RF-13506 | | | | RF-13507 | | | | RF-13508 | | | | RF-13514 | | | RF-13531 | | | | | | RF-13559 | | RF-13564 | | | | | RF-13565 | | | | RF-13571 | | | | RF-13581 | | | | RF-13582 | | | | RF-13585 | | | | RF-13586 | | | | RF-13591 | | | RF-13592 | | | | | RF-13597 | | | | RF-13608 | | | | RF-13609 | | | | RF-13610 | | | | RF-13611 | | | | RF-13612 | | | RF-13613 | | | | | RF-13614 | | | RF-13616 | | | | | RF-13620 | | | | RF-13623 | | | | RF-13626 | | | | RF-13627 | | | RF-13629 | | | | | RF-13630 | | | | RF-13631 | | | | RF-13632 | | | | RF-13634 | | | | RF-13637 | | | | RF-13638 | | | | RF-13641 | | | | RF-13646 | | | | RF-13647 | | | | RF-13650 | | | | RF-13653 | | | | RF-13654 | | | | RF-13851 | | | | RF-13930 | | | | RF-13936 | | | | RF-13951 | | > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 13:58:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Jun 2014 13:58:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973439#comment-12973439 ] Brian Leathem edited comment on RF-13652 at 6/4/14 1:56 PM: ------------------------------------------------------------ A third attempt at resolving this issue involves looking at the commit history of the two branches since they forked, and identifying which jira issues are fixed in 4.3 but not in 4.5. The list of 4.3 commits was retrieved using the command (for the components repository): {code} git rev-list --pretty=oneline 4.3.7.20140523-Final ^4.3.2.20130513-Final {code} The list of 4.5 commits was retrieved with the command: {code} git rev-list --pretty=oneline 4.5.x ^4.5.x-START~1 ^2d7f107eeb3e8a22b6084935ccab8a9cd6b38665 ^4791fe039c27d3826cb5ec89d133fdf3efd9576b ^b32deba90c1a423bd3f58e773b7fc0d4ee8f1a87 ^f0e8896471bafb0c84ac50589cf72726e6da5b90 ^c851c22d9c638509fce2c42c8eb615b8ff59f771 {code} Comparing the two commit lists shows: || Fixed in RF43 || Fixed in RF45 || Fixed in both || | | | RF-11275 | | RF-11417 | | | | RF-11469 | | | | RF-11691 | | | | | | RF-11736 | | | | RF-11973 | | | RF-12132 | | | | RF-12214 | | | | RF-12224 | | | RF-12345 | | | | | | RF-12675 | | RF-12741 | | | | | RF-12765 | | | | RF-12784 | | | | RF-12786 | | | | | RF-12813 | | | RF-12843 | | | | RF-12849 | | | | | RF-12850 | | | | RF-12853 | | RF-12929 | | | | | RF-12933 | | | | RF-12940 | | | | RF-12941 | | | | | RF-12943 | | | RF-12964 | | | RF-12975 | | | | | | RF-12989 | | | | RF-13010 | | | | RF-13018 | | | RF-13027 | | | | | RF-13038 | | | | RF-13046 | | | RF-13053 | | | | | RF-13060 | | | RF-13078 | | | | | RF-13087 | | | RF-13090 | | | | | RF-13094 | | | | RF-13095 | | | RF-13097 | | | | | RF-13102 | | | | RF-13107 | | | RF-13114 | | | | | RF-13117 | | | | RF-13125 | | | | RF-13133 | | | | RF-13136 | | | | RF-13137 | | | | RF-13140 | | | RF-13147 | | | | RF-13150 | | | RF-13155 | | | | | RF-13160 | | | | | RF-13161 | | RF-13172 | | | | | RF-13186 | | | RF-13189 | | | | RF-13208 | | | | | RF-13210 | | | | RF-13213 | | | | RF-13214 | | | | RF-13223 | | | | RF-13224 | | | | RF-13229 | | | | | RF-13239 | | | RF-13265 | | | RF-13277 | | | | | RF-13278 | | | | RF-13280 | | | | RF-13282 | | | | | RF-13287 | | RF-13292 | | | | RF-13305 | | | | RF-13306 | | | | | | RF-13314 | | | RF-13330 | | | | RF-13334 | | | | | RF-13358 | | | RF-13362 | | | | RF-13374 | | | | RF-13394 | | | | RF-13395 | | | RF-13453 | | | | | | RF-13455 | | | RF-13472 | | | RF-13478 | | | | | RF-13494 | | | | RF-13495 | | | | RF-13496 | | | | RF-13505 | | | | RF-13506 | | | | RF-13507 | | | | RF-13508 | | | | RF-13514 | | | RF-13531 | | | | | | RF-13559 | | RF-13564 | | | | | RF-13565 | | | | RF-13571 | | | | RF-13581 | | | | RF-13582 | | | | RF-13585 | | | | RF-13586 | | | | RF-13591 | | | RF-13592 | | | | | RF-13597 | | | | RF-13608 | | | | RF-13609 | | | | RF-13610 | | | | RF-13611 | | | | RF-13612 | | | RF-13613 | | | | | RF-13614 | | | RF-13616 | | | | | RF-13620 | | | | RF-13623 | | | | RF-13626 | | | | RF-13627 | | | RF-13629 | | | | | RF-13630 | | | | RF-13631 | | | | RF-13632 | | | | RF-13634 | | | | RF-13637 | | | | RF-13638 | | | | RF-13641 | | | | RF-13646 | | | | RF-13647 | | | | RF-13650 | | | | RF-13653 | | | | RF-13654 | | | | RF-13851 | | | | RF-13930 | | | | RF-13936 | | | | RF-13951 | | was (Author: bleathem): A third attempt at resolving this issue involves looking at the commit history of the two branches since they forked, and identifying which jira issues are fixed in 4.3 but not in 4.5. The list of 4.3 commits was retrieved using the command (for the components repository): {code} git rev-list --pretty=oneline 4.3.7.20140523-Final ^4.3.2.20130513-Final {code} The list of 4.5 commits was retrieved with the command: {code} git rev-list --pretty=oneline 4.5.x ^4.5.x-START~1 ^2d7f107eeb3e8a22b6084935ccab8a9cd6b38665 ^4791fe039c27d3826cb5ec89d133fdf3efd9576b ^b32deba90c1a423bd3f58e773b7fc0d4ee8f1a87 ^f0e8896471bafb0c84ac50589cf72726e6da5b90 ^c851c22d9c638509fce2c42c8eb615b8ff59f771 {code} Comparing the two commit lists shows: || Fixed in RF43 || Fixed in both || Fixed in RF45 || | | | RF-11275 | | RF-11417 | | | | RF-11469 | | | | RF-11691 | | | | | | RF-11736 | | | | RF-11973 | | | RF-12132 | | | | RF-12214 | | | | RF-12224 | | | RF-12345 | | | | | | RF-12675 | | RF-12741 | | | | | RF-12765 | | | | RF-12784 | | | | RF-12786 | | | | | RF-12813 | | | RF-12843 | | | | RF-12849 | | | | | RF-12850 | | | | RF-12853 | | RF-12929 | | | | | RF-12933 | | | | RF-12940 | | | | RF-12941 | | | | | RF-12943 | | | RF-12964 | | | RF-12975 | | | | | | RF-12989 | | | | RF-13010 | | | | RF-13018 | | | RF-13027 | | | | | RF-13038 | | | | RF-13046 | | | RF-13053 | | | | | RF-13060 | | | RF-13078 | | | | | RF-13087 | | | RF-13090 | | | | | RF-13094 | | | | RF-13095 | | | RF-13097 | | | | | RF-13102 | | | | RF-13107 | | | RF-13114 | | | | | RF-13117 | | | | RF-13125 | | | | RF-13133 | | | | RF-13136 | | | | RF-13137 | | | | RF-13140 | | | RF-13147 | | | | RF-13150 | | | RF-13155 | | | | | RF-13160 | | | | | RF-13161 | | RF-13172 | | | | | RF-13186 | | | RF-13189 | | | | RF-13208 | | | | | RF-13210 | | | | RF-13213 | | | | RF-13214 | | | | RF-13223 | | | | RF-13224 | | | | RF-13229 | | | | | RF-13239 | | | RF-13265 | | | RF-13277 | | | | | RF-13278 | | | | RF-13280 | | | | RF-13282 | | | | | RF-13287 | | RF-13292 | | | | RF-13305 | | | | RF-13306 | | | | | | RF-13314 | | | RF-13330 | | | | RF-13334 | | | | | RF-13358 | | | RF-13362 | | | | RF-13374 | | | | RF-13394 | | | | RF-13395 | | | RF-13453 | | | | | | RF-13455 | | | RF-13472 | | | RF-13478 | | | | | RF-13494 | | | | RF-13495 | | | | RF-13496 | | | | RF-13505 | | | | RF-13506 | | | | RF-13507 | | | | RF-13508 | | | | RF-13514 | | | RF-13531 | | | | | | RF-13559 | | RF-13564 | | | | | RF-13565 | | | | RF-13571 | | | | RF-13581 | | | | RF-13582 | | | | RF-13585 | | | | RF-13586 | | | | RF-13591 | | | RF-13592 | | | | | RF-13597 | | | | RF-13608 | | | | RF-13609 | | | | RF-13610 | | | | RF-13611 | | | | RF-13612 | | | RF-13613 | | | | | RF-13614 | | | RF-13616 | | | | | RF-13620 | | | | RF-13623 | | | | RF-13626 | | | | RF-13627 | | | RF-13629 | | | | | RF-13630 | | | | RF-13631 | | | | RF-13632 | | | | RF-13634 | | | | RF-13637 | | | | RF-13638 | | | | RF-13641 | | | | RF-13646 | | | | RF-13647 | | | | RF-13650 | | | | RF-13653 | | | | RF-13654 | | | | RF-13851 | | | | RF-13930 | | | | RF-13936 | | | | RF-13951 | | > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 14:14:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Jun 2014 14:14:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973449#comment-12973449 ] Brian Leathem commented on RF-13652: ------------------------------------ As can be seen from the comment above, some git commit messages reference invalid JIRA issues. This will take some investigation and cleanup to resolve. > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 14:16:17 2014 From: issues at jboss.org (Alexandre Palmeira (JIRA)) Date: Wed, 4 Jun 2014 14:16:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13659) Autocomplete cannot select option on IE11 In-Reply-To: References: Message-ID: Alexandre Palmeira created RF-13659: --------------------------------------- Summary: Autocomplete cannot select option on IE11 Key: RF-13659 URL: https://issues.jboss.org/browse/RF-13659 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.3.7, 4.3.6, 4.3.5 Environment: Internet Explorer 11 Reporter: Alexandre Palmeira Components: autocomplete, select, inplaceSelect. Works on IE 10. Issues: User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. however clicking on the item will select the option correctly. EXCEPT autocomplete (RF4), where it will not select anything. workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. User cannot select option with keyboard. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 15:20:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Jun 2014 15:20:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973449#comment-12973449 ] Brian Leathem edited comment on RF-13652 at 6/4/14 3:18 PM: ------------------------------------------------------------ As can be seen from the comment above, some git commit messages reference invalid JIRA issues. -This will take some investigation and cleanup to resolve.- These errors are however unique to the RF45 commits, and so can be ignored for the sake of resolving this issue. was (Author: bleathem): As can be seen from the comment above, some git commit messages reference invalid JIRA issues. This will take some investigation and cleanup to resolve. > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 15:34:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Jun 2014 15:34:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973468#comment-12973468 ] Brian Leathem commented on RF-13652: ------------------------------------ Analysing the above list of issues shows that the following RF 4.3 commits _may_ need to be applied to RF 4.5: {quote} fad2e300d162b2533898017c3af9969cb0031485 RF-12975: EDT - get columnOrder attribute value when ValueExpression isn't set c185af0d46b056b6bc1ab2b78b4b513b1312f58c RF-12929 - PickList change event not firing correctly when ordering objects in target area 512867a21f394b9de710144d695ebd276b3c6db4 RF-11691 - rich:select value disappears if you click between list and value 68cc702657a25a1c31d8b2d45c30cbe13712bab2 RF-12741: fixed VDL doc for rich:element/rich:jQuery functions 1f62dd669a4cd4e69039b6e75a89015883f27c5a RF-12345 - JS error when pressing ESC on an open inplaceSelect in IE 4da217bd181ecdf0783dbe55701b2e956373499a RF-13155: Added an id attribute to the fileupload input element bc56acdb3c376d0f6cdc51a1ab5a78020f889e40 RF-13189: Replaced jquery-atmosphere.js with the 1.0.17 version 93431ea22e58a6639974427c508be67f842f2a13 RF-13189: Removed trailing whitespace from the 1.0.17 version of jquery-atmosphere.js 69fe8c990d1333e4425f97094d567584acde2a55 RF-11469: autocomplete method does not resolve bean if ui:included and only one parameter provided c2bdfda5f9a70537eb11124bd99390902a655b05 RF-13155: Reverted the change "Added an id attribute to the fileupload input element" due to the creation of duplicate DOM ids when multiple files are uploaded. a2c5f0ffe50b818cc523d8b39d6686fb0c8c0f7f RF-13277: upgrade Atmosphere to 1.0.18 e10cfb2c418a231089e7ec52e0f4b008e3883321 RF-13292: fix arrow key handling in Opera 12.10+ 414a320369d85c3a5f41e2ace42470d6fdc28e03 fixes issue RF-13172 58194d5207af7aa7a36d393a46bc70f82fcf823c RF-13310: aligned with API changes after Arquillian extensions upgrade 3827291756002a8bad0969ab243fe87daa930bde RF-13310: ignored FileUpload test temporarily 5caad81da32f96da7a10228405594b360d70aca5 RF-13306: Autocomplete: initialize value from DOM b3e6d833e55317f973855dbe05ee3e6d843463c6 RF-13305: Autocomplete - always populate suggestions when input is empty 79684f57251d7a9f2ebd082f51aef3da0684637e RF-13208: Push: make message transport format a valid XML 6691e98b63daf7d17241aa989c9a4763bb7e372a Merge pull request #89 from positiveCoder/feature/RF-13453 150d76e53c088f9700532b9d89390e60931546b5 RF-13531: Replaced the mouseenter/leave event handlers with a top-level delegating event handler 5931f8c3a475d39bc746dad6893da7f1e32b6241 RF-13531: Replaced the mouseenter/leave event handlers with a top-level delegating event handler for autocomplete 869ab8cf75f464d0d8f83b34d7fe17ed50a3f7ae RF-13531: Removed use of the keypress event for listening for "special" keys 771435325be1f3b8f5bb4254d4878457d00adc2e RF-13613: fix contextMenu showEvent cc985dbeb3c9ac81fde3d1ebe83e29ff28cd419f RF-11417: Made the abstract toggle panel broadcast events to active children. Immediate attribute functionality remains. Action is invoked in the necessary phase. 01568441eef4a95cbd8f180f505d73a416fcdd2c RF-11417: Fixed checkstyle issues 24053a4267cf2b271ab75c7256f70b6d5dc40fb7 RF-13478: Fixed the vdl issues 220fd4ce1fd3d6c8c735a4d2513cff2bdbc597f0 RF-13564: Removed the picklist outline present when the mouse is pressed down f0db0143f40dfa53a9f4b45e7fc4b704db960c40 RF-13592: reset the lastMessageNumber when the RichFaces.Push#disconnect function is invoked. 32fa85ffc84e37154fa7efef3a9645617a75f7ee RF-13616: Skipped the width calculation in the doResizeOrMove function when options.autosized is true 2a462d2d08b99750565d74ac989d690df3c6deb3 Revert "RF-13616: Skipped the width calculation in the doResizeOrMove function when options.autosized is true" 1fbeaee65688b67defffe6856a7aa4b712330ff9 RF-13616: Changed the togglePanel to trigger a resize event when it's contents are toggled aa2ab4c60520ec928787ad6d4be0702d280d6309 RF-13616: Fixed the popupPanel implementation to respond to resize events of it's contents, and to respect minWidth and maxWidth values when autosizing b0eb8e4f7facb03e3e836f8293a0d1f1b7a2ca35 RF-13629: Applied the same changes to the height handling as were applied to the width handling in RF-13616 b0eb8e4f7facb03e3e836f8293a0d1f1b7a2ca35 RF-13629: Applied the same changes to the height handling as were applied to the width handling in RF-13616 a1560aecece24d582bc379c83365fed6a800382b RF-13629: Prevented width and height resets when the popup is moved and not resized 621cad45630f41bd318c0c2ee7f046f65bd103f8 RF-13616: Dynamically calculated the scrollbar height used in the popupPanel height calculation 66aa413159cb2ade48e05d72d43e0a11baa5c20e RF-13616: Replaced the scrollbar height cacluclation with a cache of the shadow/scroller height difference 8302e880e669fcf43fa4b31f69f8bbada9fbe35a RF-13629: Made the move/resize inference more aggressivle apply the resize logic 6ab82a619dea0358b1a3066355cac26f78257b32 RF-13629: reset dimensions according to current window 31ae35b0862e32fcd857081083565be1b1c875fb RF-13629: reset position before resizing {quote} > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 16:58:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Jun 2014 16:58:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973501#comment-12973501 ] Brian Leathem edited comment on RF-13652 at 6/4/14 4:57 PM: ------------------------------------------------------------ RF-12975 was applied with this commit {{[7f622f|https://github.com/richfaces/richfaces/commit/7f622fa22bac9613ef25489822d6bd4ec1c66227]}}. This is 6 commits before where I inferred the {{4.3}}/{{4.5}} fork point was. was (Author: bleathem): RF-12975 was pplied with this commit {{[7f622f|https://github.com/richfaces/richfaces/commit/7f622fa22bac9613ef25489822d6bd4ec1c66227]}}. This is 6 commits before where I inferred the {{4.3}}/{{4.5}} fork point was. > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 16:58:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Jun 2014 16:58:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973501#comment-12973501 ] Brian Leathem commented on RF-13652: ------------------------------------ RF-12975 was pplied with this commit {{[7f622f|https://github.com/richfaces/richfaces/commit/7f622fa22bac9613ef25489822d6bd4ec1c66227]}}. This is 6 commits before where I inferred the {{4.3}}/{{4.5}} fork point was. > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 4 17:28:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 4 Jun 2014 17:28:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973511#comment-12973511 ] Brian Leathem commented on RF-13652: ------------------------------------ 4da217bd181ecdf0783dbe55701b2e956373499a was reverted by c2bdfda5f9a70537eb11124bd99390902a655b05, so both can be excluded from the commit list. > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 02:28:20 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 02:28:20 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973560#comment-12973560 ] Brian Leathem commented on RF-13652: ------------------------------------ In the end I applied a patch for the commits associated with the following issues: RF-11417/RF-11427 RF-11469 RF-13172 RF-13208 RF-13292 RF-13305 RF-13310 RF-13478 RF-13531 RF-13564 RF-13592 RF-13616 RF-13629. The fix for RF-13613 was half-applied, I finished the fix automatically. > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 02:28:20 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 02:28:20 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973560#comment-12973560 ] Brian Leathem edited comment on RF-13652 at 6/5/14 2:27 AM: ------------------------------------------------------------ In the end I applied a patch for the commits associated with the following issues: RF-11417/RF-11427 RF-11469 RF-13172 RF-13208 RF-13292 RF-13305 RF-13310 RF-13478 RF-13531 RF-13564 RF-13592 RF-13616 RF-13629. The fix for RF-13613 was half-applied, I finished the fix manually. was (Author: bleathem): In the end I applied a patch for the commits associated with the following issues: RF-11417/RF-11427 RF-11469 RF-13172 RF-13208 RF-13292 RF-13305 RF-13310 RF-13478 RF-13531 RF-13564 RF-13592 RF-13616 RF-13629. The fix for RF-13613 was half-applied, I finished the fix automatically. > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 02:28:20 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 02:28:20 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13652. -------------------------------- Labels: needs-qe (was: ) Resolution: Done > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 02:36:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 02:36:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13659) Autocomplete cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13659: ---------------------------------- Assignee: Pavol Pitonak QE please verify and assess whether it is a duplicate of RF-13640. > Autocomplete cannot select option on IE11 > ----------------------------------------- > > Key: RF-13659 > URL: https://issues.jboss.org/browse/RF-13659 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5, 4.3.6, 4.3.7 > Environment: Internet Explorer 11 > Reporter: Alexandre Palmeira > Assignee: Pavol Pitonak > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > Issues: > User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > however clicking on the item will select the option correctly. EXCEPT autocomplete (RF4), where it will not select anything. > workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > User cannot select option with keyboard. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 02:36:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 02:36:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13656: ---------------------------------- Assignee: Pavol Pitonak QE please verify > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Pavol Pitonak > Labels: waiting_on_user > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 02:38:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 02:38:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11280) showcase - rich:autocomplete - samples Autocompletion Modes, Custom Popup Layouts - it does not work when it is in Ajax or lazy mode on IE9 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973565#comment-12973565 ] Brian Leathem commented on RF-11280: ------------------------------------ [~apalmeira] this is in fact a new problem that re-curred. It is being tracked via RF-13640. > showcase - rich:autocomplete - samples Autocompletion Modes, Custom Popup Layouts - it does not work when it is in Ajax or lazy mode on IE9 > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11280 > URL: https://issues.jboss.org/browse/RF-11280 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.1.0.Milestone1 > Environment: richfaces-showcase-4.1.0.20110805-M1-jee6.war > container - JBoss AS 6.0.0.Final > browser - IE 9 > Reporter: Juraj H?ska > Labels: ie9_normal_jq151 > > When rich:autocomplete is in Ajax or lazy client mode it does not show any suggestions. It works fine when it is in client mode. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 02:38:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 02:38:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13658: ------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 02:38:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 02:38:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13658: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 3 > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 05:28:15 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 5 Jun 2014 05:28:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-13656: ------------------------------- Labels: regression (was: waiting_on_user) > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Pavol Pitonak > Labels: regression > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 05:28:15 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 5 Jun 2014 05:28:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973620#comment-12973620 ] Pavol Pitonak commented on RF-13656: ------------------------------------ I could reproduce the bug with 4.3.7.Final. As reported, it worked fine in 4.3.6.Final. I added a reproducer to Metamer, you can find it on http://localhost:8080/metamer/faces/components/richExtendedDataTable/rf-13656.xhtml > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Pavol Pitonak > Labels: regression > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 06:48:15 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 5 Jun 2014 06:48:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13659) Autocomplete cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13659: ---------------------------------- Assignee: Juraj H?ska (was: Pavol Pitonak) > Autocomplete cannot select option on IE11 > ----------------------------------------- > > Key: RF-13659 > URL: https://issues.jboss.org/browse/RF-13659 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5, 4.3.6, 4.3.7 > Environment: Internet Explorer 11 > Reporter: Alexandre Palmeira > Assignee: Juraj H?ska > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > Issues: > User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > however clicking on the item will select the option correctly. EXCEPT autocomplete (RF4), where it will not select anything. > workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > User cannot select option with keyboard. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 06:50:16 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 5 Jun 2014 06:50:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13660) RichFaces 4.5 integration tests - error after test execution In-Reply-To: References: Message-ID: Matej Novotny created RF-13660: ---------------------------------- Summary: RichFaces 4.5 integration tests - error after test execution Key: RF-13660 URL: https://issues.jboss.org/browse/RF-13660 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 4.5.0.Alpha2 Environment: AS: Wildfly Browser: PhantomJS Reporter: Matej Novotny This issue originated from RF-13591. There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/src/test/integration/org/richfaces/integration/resource/ITResourceMapping.java]. The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines and I think (not verified yet) that this might cause a build failure in Chrome and FF. Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5/56/console]. The exception in server console is: {code} 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:] at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:] at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:] at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:] at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 06:56:15 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 5 Jun 2014 06:56:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13591) RichFaces 4.5 integration tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973683#comment-12973683 ] Matej Novotny commented on RF-13591: ------------------------------------ I created RF-13660 to adress the issue with error in server console while building core with smoke tests. This might also be one of the causes while chrome/FF tests and Jnekins fail to build it. > RichFaces 4.5 integration tests are failing > ------------------------------------------- > > Key: RF-13591 > URL: https://issues.jboss.org/browse/RF-13591 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > RichFaces 4.5 cannot be build because of compilation errors in integration tests: > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on project richfaces: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[9,30] error: cannot find symbol > [ERROR] package org.richfaces.ui.toggle > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[10,39] error: package org.richfaces.ui.toggle.tabPanel does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[18,12] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[19,27] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[21,28] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[25,11] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[29,35] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[33,16] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusDefaults.java:[48,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcing.java:[38,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcingOverridesFocusSettings.java:[31,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcingOverridesFocusSettings.java:[32,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusCandidates.java:[34,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusCandidates.java:[35,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[31,26] error: cannot find symbol > [ERROR] package org.richfaces.model > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[44,12] error: cannot find symbol > [ERROR] class IterationBuiltInBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[45,12] error: cannot find symbol > [ERROR] class IterationBuiltInBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[57,11] error: cannot find symbol > [ERROR] class IterationBuiltInBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[61,11] error: cannot find symbol > [ERROR] class IterationBuiltInBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[65,29] error: cannot find symbol > [ERROR] class IterationBuiltInBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusSubmissionMethods.java:[50,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[31,26] error: cannot find symbol > [ERROR] package org.richfaces.model > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[49,12] error: cannot find symbol > [ERROR] class IterationTableStateBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[50,12] error: cannot find symbol > [ERROR] class IterationTableStateBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[85,11] error: cannot find symbol > [ERROR] class IterationTableStateBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[89,11] error: cannot find symbol > [ERROR] class IterationTableStateBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[93,29] error: cannot find symbol > [ERROR] class IterationTableStateBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusValidationAware.java:[56,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusValidationAware.java:[57,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[63,51] error: package org.richfaces.ui.iteration.extendedDataTable does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[64,51] error: package org.richfaces.ui.iteration.extendedDataTable does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusDefaults.java:[100,16] error: cannot find symbol > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcing.java:[62,19] error: cannot find symbol > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcingOverridesFocusSettings.java:[49,8] error: cannot find symbol > [ERROR] class VerifyFocusEnforcingOverridesFocusSettings > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcingOverridesFocusSettings.java:[50,8] error: cannot find symbol > [ERROR] > [ERROR] E extends HtmlElement declared in method getElementById(String) > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusCandidates.java:[77,8] error: cannot find symbol > [ERROR] class VerifyFocusCandidates > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusCandidates.java:[78,8] error: cannot find symbol > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusValidationAware.java:[153,16] error: cannot find symbol > [ERROR] class AbstractFocus > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusValidationAware.java:[154,16] error: cannot find symbol > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[136,16] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[136,55] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[140,16] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[140,58] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[141,16] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[141,56] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[187,20] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[187,62] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[188,20] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[188,60] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[228,20] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[228,62] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[229,20] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[229,60] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[268,16] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[268,58] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[269,16] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[269,56] error: cannot find symbol > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 09:16:18 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 5 Jun 2014 09:16:18 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13660) RichFaces 4.5 integration tests - error after test execution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny updated RF-13660: ------------------------------- Description: This issue originated from RF-13591. There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/src/test/integration/org/richfaces/integration/resource/ITResourceMapping.java]. The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines. Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5/56/console]. The exception in server console is: {code} 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:] at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:] at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:] at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:] at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] {code} was: This issue originated from RF-13591. There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/src/test/integration/org/richfaces/integration/resource/ITResourceMapping.java]. The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines and I think (not verified yet) that this might cause a build failure in Chrome and FF. Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5/56/console]. The exception in server console is: {code} 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:] at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:] at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:] at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:] at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] {code} > RichFaces 4.5 integration tests - error after test execution > ------------------------------------------------------------ > > Key: RF-13660 > URL: https://issues.jboss.org/browse/RF-13660 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Environment: AS: Wildfly > Browser: PhantomJS > Reporter: Matej Novotny > > This issue originated from RF-13591. > There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/src/test/integration/org/richfaces/integration/resource/ITResourceMapping.java]. > The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines. > Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5/56/console]. > The exception in server console is: > {code} > 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException > at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:] > at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:] > at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:] > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] > at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:] > at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 09:48:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 5 Jun 2014 09:48:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13520) mediaOutput: NPE is thrown when used with CDI beans and JSF 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13520: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > mediaOutput: NPE is thrown when used with CDI beans and JSF 2.2 > --------------------------------------------------------------- > > Key: RF-13520 > URL: https://issues.jboss.org/browse/RF-13520 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha3 > Environment: WildFly 8.0.0.Final-SNAPSHOT > WildFly 8.0.0.CR1 > Reporter: Juraj H?ska > Assignee: Brian Leathem > Priority: Critical > Labels: 45x, jsf22 > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > > When {{mediaOutput}} is bound via {{value}} attribute to a *CDI* bean, following NPE is thrown: > {code} > 15:32:20,443 ERROR [io.undertow.request] (default task-16) UT005023: Exception handling request to /metamer/faces/rfRes/org.richfaces.ui.output.mediaOutput.MediaOutputResource: java.lang.NullPointerException > at org.richfaces.ui.output.mediaOutput.MediaOutputResource.encode(MediaOutputResource.java:66) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:69) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:69) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.SessionRestoringHandler.handleRequest(SessionRestoringHandler.java:101) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:685) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] > {code} > Note that everything works with JSF 2.1.x (AS 7.1.1.Final) and when Managed Beans are used. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 09:50:15 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 5 Jun 2014 09:50:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13518) Action Listener - invoking from composite component does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13518: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Action Listener - invoking from composite component does not work > ----------------------------------------------------------------- > > Key: RF-13518 > URL: https://issues.jboss.org/browse/RF-13518 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha3 > Environment: WildFly 8.0.0.Final-SNAPSHOT > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Priority: Critical > Labels: 45x, jsf22 > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > > Invoking Action Listener from composite component does not work. Please see the steps to reproduce the issue. > Note that it works with JSF 2.1.x. It is similar to issue RF-10585, but that one is for MyFaces. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 09:52:16 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 5 Jun 2014 09:52:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13651) Integration tests failing in chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973768#comment-12973768 ] Matej Novotny commented on RF-13651: ------------------------------------ I used Chrome and Firefox for testing and I tried running {code}mvn clean install -Dintegration=wildfly80-remote Dbrowser=chrome -Dsmoke=true{code} separately on core, a4j components and rich components. Chrome results: * rich components ** Build success * a4j components ** Test error in warp test marked with @BeforePhase(RENDER_RESPONSE) [ITRegionRichAjax.testExecuteRegion|https://github.com/richfaces/richfaces/blob/4.5.x/components/a4j/src/test/integration/org/richfaces/component/region/ITRegionRichAjax.java#L82] ** All other @Smoke tests pass ** The exception in server console is following: {code} 14:43:56,036 ERROR [stderr] (default task-2) java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.ObjectNotAssociatedException 14:43:56,039 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.jsf.FacesContextFactory$WarpFacesContext.release(FacesContextFactory.java:102) 14:43:56,039 ERROR [stderr] (default task-2) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:665) 14:43:56,039 ERROR [stderr] (default task-2) at org.richfaces.webapp.ResourceServlet.httpService(ResourceServlet.java:129) 14:43:56,040 ERROR [stderr] (default task-2) at org.richfaces.webapp.ResourceServlet.service(ResourceServlet.java:123) 14:43:56,040 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) 14:43:56,040 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) 14:43:56,040 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.execution.HttpRequestProcessor.processHttpRequest(HttpRequestProcessor.java:73) 14:43:56,041 ERROR [stderr] (default task-2) at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source) 14:43:56,041 ERROR [stderr] (default task-2) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 14:43:56,041 ERROR [stderr] (default task-2) at java.lang.reflect.Method.invoke(Method.java:606) 14:43:56,042 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 14:43:56,042 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) 14:43:56,042 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) 14:43:56,042 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:90) 14:43:56,043 ERROR [stderr] (default task-2) at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source) 14:43:56,043 ERROR [stderr] (default task-2) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 14:43:56,043 ERROR [stderr] (default task-2) at java.lang.reflect.Method.invoke(Method.java:606) 14:43:56,044 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 14:43:56,044 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) 14:43:56,044 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) 14:43:56,044 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) 14:43:56,045 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) 14:43:56,045 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) 14:43:56,045 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) 14:43:56,046 ERROR [stderr] (default task-2) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) 14:43:56,046 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) 14:43:56,046 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) 14:43:56,047 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) 14:43:56,047 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) 14:43:56,047 ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) 14:43:56,047 ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) 14:43:56,048 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) 14:43:56,048 ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) 14:43:56,048 ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) 14:43:56,049 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) 14:43:56,049 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) 14:43:56,049 ERROR [stderr] (default task-2) at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) 14:43:56,050 ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) 14:43:56,050 ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) 14:43:56,050 ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) 14:43:56,051 ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) 14:43:56,051 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) 14:43:56,051 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) 14:43:56,051 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) 14:43:56,052 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) 14:43:56,052 ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) 14:43:56,052 ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) 14:43:56,053 ERROR [stderr] (default task-2) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 14:43:56,053 ERROR [stderr] (default task-2) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 14:43:56,053 ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:724) 14:43:56,054 ERROR [stderr] (default task-2) Caused by: org.jboss.arquillian.warp.spi.exception.ObjectNotAssociatedException 14:43:56,054 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.obtain(LifecycleManagerStoreImpl.java:63) 14:43:56,054 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.spi.LifecycleManagerStore.get(LifecycleManagerStore.java:69) 14:43:56,055 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.jsf.FacesContextFactory$WarpFacesContext.release(FacesContextFactory.java:97) 14:43:56,055 ERROR [stderr] (default task-2) ... 49 more 14:43:56,056 ERROR [stderr] (default task-2) java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException 14:43:56,057 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) 14:43:56,057 ERROR [stderr] (default task-2) at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source) 14:43:56,057 ERROR [stderr] (default task-2) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 14:43:56,058 ERROR [stderr] (default task-2) at java.lang.reflect.Method.invoke(Method.java:606) 14:43:56,058 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 14:43:56,058 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) 14:43:56,058 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) 14:43:56,058 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) 14:43:56,059 ERROR [stderr] (default task-2) at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source) 14:43:56,059 ERROR [stderr] (default task-2) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 14:43:56,059 ERROR [stderr] (default task-2) at java.lang.reflect.Method.invoke(Method.java:606) 14:43:56,059 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 14:43:56,059 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) 14:43:56,059 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) 14:43:56,060 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) 14:43:56,060 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) 14:43:56,060 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) 14:43:56,060 ERROR [stderr] (default task-2) at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source) 14:43:56,060 ERROR [stderr] (default task-2) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 14:43:56,060 ERROR [stderr] (default task-2) at java.lang.reflect.Method.invoke(Method.java:606) 14:43:56,061 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) 14:43:56,061 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) 14:43:56,061 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) 14:43:56,061 ERROR [stderr] (default task-2) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) 14:43:56,061 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) 14:43:56,062 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) 14:43:56,062 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) 14:43:56,062 ERROR [stderr] (default task-2) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) 14:43:56,062 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) 14:43:56,062 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) 14:43:56,062 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) 14:43:56,063 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) 14:43:56,063 ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) 14:43:56,063 ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) 14:43:56,063 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) 14:43:56,063 ERROR [stderr] (default task-2) at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) 14:43:56,063 ERROR [stderr] (default task-2) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) 14:43:56,064 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) 14:43:56,064 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) 14:43:56,064 ERROR [stderr] (default task-2) at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) 14:43:56,064 ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) 14:43:56,064 ERROR [stderr] (default task-2) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) 14:43:56,065 ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) 14:43:56,065 ERROR [stderr] (default task-2) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) 14:43:56,065 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) 14:43:56,065 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) 14:43:56,065 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) 14:43:56,066 ERROR [stderr] (default task-2) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) 14:43:56,066 ERROR [stderr] (default task-2) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) 14:43:56,066 ERROR [stderr] (default task-2) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) 14:43:56,067 ERROR [stderr] (default task-2) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 14:43:56,067 ERROR [stderr] (default task-2) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 14:43:56,067 ERROR [stderr] (default task-2) at java.lang.Thread.run(Thread.java:724) 14:43:56,068 ERROR [stderr] (default task-2) Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException 14:43:56,068 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) 14:43:56,068 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) 14:43:56,068 ERROR [stderr] (default task-2) at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) 14:43:56,069 ERROR [stderr] (default task-2) ... 52 more 14:43:56,069 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /ITRegionRichAjax/org.richfaces.resources/javax.faces.resource/org.richfaces/richfaces-queue.js: java.lang.IllegalStateException: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:69) [arquillian-warp.jar:] at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source) [:1.7.0_25] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25] at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) [arquillian-core.jar:] at org.jboss.arquillian.warp.impl.server.test.LifecycleTestClassExecutor.afterRequest(LifecycleTestClassExecutor.java:78) [arquillian-warp.jar:] at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source) [:1.7.0_25] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25] at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) [arquillian-core.jar:] at org.jboss.arquillian.warp.impl.server.request.RequestContextHandler.handleRequestContext(RequestContextHandler.java:93) [arquillian-warp.jar:] at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source) [:1.7.0_25] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25] at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) [arquillian-core.jar:] at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) [arquillian-core.jar:] at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterWarp(WarpFilter.java:151) [arquillian-warp.jar:] at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilterHttp(WarpFilter.java:120) [arquillian-warp.jar:] at org.jboss.arquillian.warp.impl.server.execution.WarpFilter.doFilter(WarpFilter.java:93) [arquillian-warp.jar:] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) [undertow-core-1.0.0.Final.jar:1.0.0.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] Caused by: org.jboss.arquillian.warp.spi.exception.StoreHasAssociatedObjectsException at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerStoreImpl.checkUnbound(LifecycleManagerStoreImpl.java:126) [arquillian-warp.jar:] at org.jboss.arquillian.warp.spi.LifecycleManager.checkUnbound(LifecycleManager.java:158) [arquillian-warp.jar:] at org.jboss.arquillian.warp.impl.server.lifecycle.LifecycleManagerObserver.finalizeManager(LifecycleManagerObserver.java:67) [arquillian-warp.jar:] ... 52 more {code} ** And the one shown as a result of test execution: {code} testExecuteRegion(org.richfaces.component.region.ITRegionRichAjax) Time elapsed: 6.332 sec <<< ERROR! org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) at com.sun.proxy.$Proxy33.responsePost(Unknown Source) at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) at java.lang.Thread.run(Thread.java:724) {code} * core ** Again there is a similar failure as with a4j components. Problematic test is [ITJavaScriptServiceAjax|https://github.com/richfaces/richfaces/blob/4.5.x/components/a4j/src/test/integration/org/richfaces/component/region/ITRegionRichAjax.java#L82titjavascriptservice] ** When I mark this test as Failing, the build is successful - no other test errors are present ** In this case there is no error in server console, only the one from test execution which is similar to the one mentioned above. Furthermore I ran these tests with Firefox with following results: * rich components ** Error in ITFileUpload, but the test is currently marked as FailingOnPhantomJS, so I suppose we can mark it just as Failing until we first fix it for PhantomJS * a4j components ** Build success * core ** Same problem as with Chrome Summary: As for smoke tests we only have 2 problematic classes to resolve, both of which are warp tests and might be failing for same reason(s). I did not test IE so far, I suppose I will do it after we resolve the problems in chrome and ff. I will try to find out more information about the cause of failure (there are other warp tests using similar approach and those are passing). > Integration tests failing in chrome > ----------------------------------- > > Key: RF-13651 > URL: https://issues.jboss.org/browse/RF-13651 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > The framework tests pass in phantomjs but some fail in chrome. > Resolution of this issue involves running and stabilizing the tests in all supported browsers. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 10:32:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 10:32:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13660) RichFaces 4.5 integration tests - error after test execution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13660: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > RichFaces 4.5 integration tests - error after test execution > ------------------------------------------------------------ > > Key: RF-13660 > URL: https://issues.jboss.org/browse/RF-13660 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Environment: AS: Wildfly > Browser: PhantomJS > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > This issue originated from RF-13591. > There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/src/test/integration/org/richfaces/integration/resource/ITResourceMapping.java]. > The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines. > Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5/56/console]. > The exception in server console is: > {code} > 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException > at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:] > at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:] > at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:] > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] > at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:] > at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 14:04:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 14:04:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13656: ------------------------------- Fix Version/s: 4.3.8 > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Pavol Pitonak > Labels: regression > Fix For: 4.3.8 > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:38:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:38:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13446) Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13446: ------------------------------- Fix Version/s: 3.Future > Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-13446 > URL: https://issues.jboss.org/browse/RF-13446 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.1.SP3 > Reporter: Masafumi Miura > Assignee: Brian Leathem > Fix For: 3.Future > > Attachments: RF-13446.patch > > > *Description of problem:* > Unspecified javascript error occurs when clicking a4j:commandButton to rerender rich:scrollableDataTable inside rich:simpleTogglePanel. And same javascript error also happens when resizing IE browser window after clicking the a4j:commandButton. > *Version-Release number of selected component (if applicable):* > Richfaces 3.3.1.SP3 and also one-off patch applied BZ#982322. > *Steps to Reproduce:* > 1. Modify the following two files of richfaces-demo.war: > - Edit WAR/templates/main.xhtml and change from: > {code} > class="content_container" width="100%"> > > > > > > >
>
> 		> > Body > > > >
class="footer-text">#{environment.version}
> >
> {code} > to: > {code} > Body > {code} > - Edit WAR/richfaces/scrollableDataTable/examples/scrollableDataTable.xhtml and add rich:simpleTogglePanel and a4j:commandButton which rerender the > rich:scrollableDataTable. Please note that the original template uses a html table to wrap the facelet body. The error won't show if the facelet body is wrapped with the html body until you resize the browser window. > 2. Deploy modified richfaces-demo.war to EAP 5.1.2 > 3. Go to http://:/richfaces-demo/richfaces/scrollableDataTable.jsf on Internet Explorer 9 (Document mode: Internet Explorer 8) > 4. Click the button "test" at the bottom of the page. > *Actual results:* > It show the following "Unspecified error" in the IE console. And it will also showe same javascript error when resizing IE browser window after clicking the "test" button. > {code} > SCRIPT16389: Unspecified error > controls-scrollable-data-table.js, line 62 character 23 > {code} > *Expected results:* > No javascript error happens. > *Additional info:* > The reported customer is using one-off patch was created from BZ#982322 branch. > http://anonsvn.jboss.org/repos/richfaces/branches/enterprise/3.3.1.SP3_BZ-982322/ -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:38:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:38:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13593) IE8 Unspecified error. jquery-atmosphere.js.xhtml?ln=net.java.dev.atmosphere, line 1578 character 33 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13593. -------------------------------- Resolution: Won't Fix > IE8 Unspecified error. jquery-atmosphere.js.xhtml?ln=net.java.dev.atmosphere, line 1578 character 33 > ----------------------------------------------------------------------------------------------------- > > Key: RF-13593 > URL: https://issues.jboss.org/browse/RF-13593 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.3.5 > Environment: JBoss EAP 6.2 > Browser: IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Brian Leathem > Attachments: error.png, error_debug.png > > > On each "long-polling" request we get javascript error in IE 8.0 (see screenshots in attachment) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:40:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:40:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12554) in a doesn't work in composite components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12554. -------------------------------- Labels: (was: waiting_on_user) Resolution: Cannot Reproduce Bug Feel free to re-open the issue with details on how to reproduce the issue. > in a doesn't work in composite components > ------------------------------------------------------------------------ > > Key: RF-12554 > URL: https://issues.jboss.org/browse/RF-12554 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final > Reporter: Bojan Antonovic > Assignee: Ji?? ?tefek > Priority: Minor > Attachments: RF-12554.zip > > > To make it work, you have to write once the dummy > {code} > > {code} > then you can use as often as you wish: > {code} > > ... > > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:42:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:42:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12694) throwing a warning: "Cannot set header. Response already committed." In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12694. -------------------------------- Labels: (was: richfaces waiting_on_user) Resolution: Cannot Reproduce Bug Feel free to re-open the issue with details on how to reproduce the issue. > throwing a warning: "Cannot set header. Response already committed." > ---------------------------------------------------------------------------------------- > > Key: RF-12694 > URL: https://issues.jboss.org/browse/RF-12694 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.3.Final > Environment: Tested in Galssfish3.1 and WAS8 > Reporter: Srinivas Reddy Malipeddi > Priority: Minor > > When rich component like {quote} > com.ibm.ws.webcontainer.srt.SRTServletResponse setIntHeader SRVE8094W: WARNING: Cannot set header. Response already committed. > {quote} > Project details: JSF2.0, Myfaces implementation, richfaces 4.2.3 jars > My project have only one page index.xhtml with one component like below. If richfaces component is not used then the warning is not coming. > {code:title=index.xhtml} > > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:rich="http://richfaces.org/rich"> > > > > > > > > > > > {code} > {code:title=Web.xml} > > xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"> > TestWeb > > > The location where state information is saved. > Valid values are 'server' (typically saved in HttpSession) and 'client' (typically > saved as a hidden field in the form. > Default is server. > javax.faces.STATE_SAVING_METHOD > server > > > > Comma-delimited list of context-relative resource paths under which the JSF implementation > will look for application configuration resources, before loading a configuration resource > named /WEB-INF/faces-config.xml (if such a resource exists). > javax.faces.CONFIG_FILES > > > > > The default suffix for extension-mapped resources that contain JSF components. > Default is '.jsp'. > javax.faces.DEFAULT_SUFFIX > .xhtml > > > > A human readable string describing where this particular JSF application is > in the software development lifecycle. > Valid values are 'Development', 'UnitTest', 'SystemTest' and 'Production'. > Default is 'Production'. > This parameter is not available in JSF 1.x. > javax.faces.PROJECT_STAGE > Development > > > > Monitors Faces JSP files for modifications and synchronizes a running server with > the changes without restarting the server. If this parameter is set to false or > removed from the deployment descriptor, any changes made to Faces JSP files may > not be seen by the server until it is restarted. This parameter is usually set > to true while the Faces JSP files are being developed and debugged in order to > improve the performance of the development environment. > com.ibm.ws.jsf.JSP_UPDATE_CHECK > true > > > > Load JSF runtime when the application server starts up. If this parameter is set to false or removed, > JSF runtime will be loaded and initialized when the first JSF request is processed. > This may disable custom JSF extensions, such as factories defined in the project. > com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP > true > > > > Faces Servlet > javax.faces.webapp.FacesServlet > -1 > true > false > > > Faces Servlet > *.xhtml > > > Faces Servlet > > *.faces > > > Faces Servlet > > /faces/* > > > index.xhtml > > > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:42:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:42:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12916) a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-12916. -------------------------------- Resolution: Incomplete Description > a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS) > ------------------------------------------------------------------------------------------------------ > > Key: RF-12916 > URL: https://issues.jboss.org/browse/RF-12916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Luan Cestari > Labels: waiting_on_user > Attachments: proj_jms_rich.zip > > > The customer is using JBoss in cluster and he have a Richfaces 4. The web client is using websocket using Richfaces/Atmosphere. The problem is that the customer have heavy asynchronous process that need to notify all websockets from all users (using a JMS, for example) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:42:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:42:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13101) rich:select Method getSelectInputLabel is not working when using objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13101. -------------------------------- Resolution: Rejected > rich:select Method getSelectInputLabel is not working when using objects > ------------------------------------------------------------------------ > > Key: RF-13101 > URL: https://issues.jboss.org/browse/RF-13101 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, component-selects > Affects Versions: 4.3.2, 5.0.0.Alpha1 > Reporter: J W > Labels: rich:select, select, waiting_on_user > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The condition of the if-statement in org.richfaces.renderkit.SelectHelper.getSelectInputLabel(FacesContext facesContext, UIComponent component) is not working with the string-representations of the items. If using cloned objects the equals method will return false, even if the items are the same, because the IDs are different. > The method should use only the strings of the objects, similiar to how MyFaces has solved this (check workarround). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:44:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:44:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13207) Table having multiple sub-rows within a main row in extended datatable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13207. -------------------------------- Labels: (was: waiting_on_user) Resolution: Rejected > Table having multiple sub-rows within a main row in extended datatable > ---------------------------------------------------------------------- > > Key: RF-13207 > URL: https://issues.jboss.org/browse/RF-13207 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk, component-tables > Affects Versions: 4.3.1 > Environment: windows 7 , JRE 7 > Reporter: sathiyan venkatesh > -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:44:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:44:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13101) rich:select Method getSelectInputLabel is not working when using objects In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13101: ------------------------------- Labels: rich:select select (was: rich:select select waiting_on_user) > rich:select Method getSelectInputLabel is not working when using objects > ------------------------------------------------------------------------ > > Key: RF-13101 > URL: https://issues.jboss.org/browse/RF-13101 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, component-selects > Affects Versions: 4.3.2, 5.0.0.Alpha1 > Reporter: J W > Labels: rich:select, select > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The condition of the if-statement in org.richfaces.renderkit.SelectHelper.getSelectInputLabel(FacesContext facesContext, UIComponent component) is not working with the string-representations of the items. If using cloned objects the equals method will return false, even if the items are the same, because the IDs are different. > The method should use only the strings of the objects, similiar to how MyFaces has solved this (check workarround). -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:44:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:44:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12916) a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12916: ------------------------------- Labels: (was: waiting_on_user) > a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS) > ------------------------------------------------------------------------------------------------------ > > Key: RF-12916 > URL: https://issues.jboss.org/browse/RF-12916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Luan Cestari > Attachments: proj_jms_rich.zip > > > The customer is using JBoss in cluster and he have a Richfaces 4. The web client is using websocket using Richfaces/Atmosphere. The problem is that the customer have heavy asynchronous process that need to notify all websockets from all users (using a JMS, for example) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:44:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:44:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12907) render="@form" problem with a4jCommand Button / Link / @all In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12907: ------------------------------- Labels: (was: waiting_on_user) > render="@form" problem with a4jCommand Button / Link / @all > ----------------------------------------------------------- > > Key: RF-12907 > URL: https://issues.jboss.org/browse/RF-12907 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final, 4.3.1 > Environment: JSF Mojarra 2.1.21 or 2.1.20 - Glassfish 3.1.2 or WAS 8.0.0.x Servlet 3.0 or 2.5 > Reporter: Jean ANDRE > Attachments: ITBH-Maven.zip, ITBH-Maven.zip, Nested-2.1.Finale.zip, Nested-Spring-3.2.2.zip, NestedEar-CDI.zip > > > Please see the report at: http://java.net/jira/browse/JAVASERVERFACES-2016 > It seems that that there is a problem with a4j button and the value of @form/render attribute. > The symptom we got is after refreshing the panel for building a list. Click on link form the result lisk does not trigger the action. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:44:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:44:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13427) ED, Datatable: table needs to define the number of rows itself when using dataScroller In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13427. -------------------------------- Labels: (was: waiting_on_user) Resolution: Incomplete Description > ED, Datatable: table needs to define the number of rows itself when using dataScroller > -------------------------------------------------------------------------------------- > > Key: RF-13427 > URL: https://issues.jboss.org/browse/RF-13427 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.3 > Reporter: Anton Bogoslavskyi > Attachments: data-3.png, datatable-1.png > > > I need using pagination for extendedDataTable control. > My row's height depends on the data it contains. > I need the table to be constant height, so I specify the height in css. > I actually use the pagination to avoid scrollers on my screen, but the tables do not support calculation of the rows number per page - "rows" attribute need to be specified to enable using datascroller. > So, anyway, my e.g. "8" rows can either fit the half of the table while there is enough place for 16 rows, or can expand down and not fit the table so the scroller appears. > Both situations are not user friendly. > Actually on each page I need the maximum rows number to fit the height. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:46:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:46:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13602) Problem with ajax request in Internet Explorer 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13602. -------------------------------- Labels: ie11 (was: ie11 waiting_on_user) Resolution: Cannot Reproduce Bug Feel free to re-open the issue with details on how to reproduce the issue. > Problem with ajax request in Internet Explorer 11 > ------------------------------------------------- > > Key: RF-13602 > URL: https://issues.jboss.org/browse/RF-13602 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.0.0.Final > Environment: Windows 2008, JBoss AS 7.x > Reporter: Walter Maidub > Assignee: Juraj H?ska > Labels: ie11 > Attachments: Dear Juraj H?ska.docx, ie11-1.png, ie11-2.png, ie11-3.png > > > I have a form with a FileUploader component (disabled) and a rich: select and this one is populated with 3 options, when one of them is selected in the managed bean a boolean variable is set to "true" and the FileUploader panel is updated to enable it. > {code} > required="true" listWidth="320px" styleClass="rf-select-large-width"> > > execute="@this" > render="upload,seccionCarga" > listener="#{Bean.activarPanelCarga}" /> > > > > > > > > > > > > >
> styleClass="top" > . > . > . > {code} > > The problem is that the FileUploader remains disabled, it is as if the panel had not been updated. > > Generally requests fail, this only in IE 11.0.4 (KB2925418) > > Currently there is a filter to ensure compatibility with IE 8. > > When the page is loaded in developer tools (F12) the IE8 compatibility option is set correctly. > > The configuration of the environment is: > Richfaces 4.0.0. > IE11 > JSF2 > Eclipse Kepler > > Is there any way to correct the problems with these ajax requests? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:46:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:46:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13625) org.ajax4jsf.model.SequenceRange is not serializable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13625: ------------------------------- Labels: (was: waiting_on_user) > org.ajax4jsf.model.SequenceRange is not serializable > ---------------------------------------------------- > > Key: RF-13625 > URL: https://issues.jboss.org/browse/RF-13625 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.6 > Reporter: Marco Rossi > > {code} > Caused by: org.infinispan.marshall.NotSerializableException: org.ajax4jsf.model.SequenceRange > Caused by: an exception which occurred: > in field cachedRange > in field bean > in object java.util.HashMap at 0 > in object org.jboss.as.clustering.SimpleMarshalledValue at 0 > in object org.infinispan.atomic.PutOperation at 0 > in object java.util.LinkedList at 0 > in object org.infinispan.atomic.AtomicHashMapDelta at 3e01b8 > in object org.infinispan.commands.write.PutKeyValueCommand at 514bdbf9 > in object org.infinispan.commands.tx.PrepareCommand at 8bb71fb > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 17:46:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 17:46:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13625) org.ajax4jsf.model.SequenceRange is not serializable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13625: ------------------------------- Fix Version/s: 4.5-Tracking > org.ajax4jsf.model.SequenceRange is not serializable > ---------------------------------------------------- > > Key: RF-13625 > URL: https://issues.jboss.org/browse/RF-13625 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.6 > Reporter: Marco Rossi > Fix For: 4.5-Tracking > > > {code} > Caused by: org.infinispan.marshall.NotSerializableException: org.ajax4jsf.model.SequenceRange > Caused by: an exception which occurred: > in field cachedRange > in field bean > in object java.util.HashMap at 0 > in object org.jboss.as.clustering.SimpleMarshalledValue at 0 > in object org.infinispan.atomic.PutOperation at 0 > in object java.util.LinkedList at 0 > in object org.infinispan.atomic.AtomicHashMapDelta at 3e01b8 > in object org.infinispan.commands.write.PutKeyValueCommand at 514bdbf9 > in object org.infinispan.commands.tx.PrepareCommand at 8bb71fb > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:22:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:22:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13341) Charts: implement AjaxProps In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13341: ------------------------------- Fix Version/s: 4.5-Tracking > Charts: implement AjaxProps > --------------------------- > > Key: RF-13341 > URL: https://issues.jboss.org/browse/RF-13341 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Luk?? Macko > Priority: Minor > Fix For: 4.5-Tracking > > > I think AbstractChart should implements AjaxProps since it uses server-side listeners. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:24:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:24:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13440) Photoalbum - fix packing of resources In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13440. -------------------------------- Resolution: Out of Date > Photoalbum - fix packing of resources > ------------------------------------- > > Key: RF-13440 > URL: https://issues.jboss.org/browse/RF-13440 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Reporter: Michal Petrov > > The resource plugin configuration needs to be updated to work with the changes done to RF 5 resources. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:26:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:26:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13524) the tooltip freezes when changing page. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13524: ------------------------------- Labels: waiting_on_user (was: jboss richfaces tooltip) > the tooltip freezes when changing page. > --------------------------------------- > > Key: RF-13524 > URL: https://issues.jboss.org/browse/RF-13524 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.0.0.CR1, 4.2.2.Final > Environment: Windows Vista, Web Sphere 8.5, Java jdk 1.5, maven > Reporter: Carlos Mauro C?rdenas Fern?ndez > Labels: waiting_on_user > > I have a tooltip implemented on a main page, but when you click the link tooltip box gets stuck on next page > > {code} > > > onhide="false" hideEvent="mouseleave"> > > > {code} > problem.png > > I tried to change the tooltip parameter but didnt find the solution. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:26:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:26:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13524) the tooltip freezes when changing page. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973904#comment-12973904 ] Brian Leathem commented on RF-13524: ------------------------------------ Can you please provide a simple-as-possible yet runnable sample to reproduce this issue? > the tooltip freezes when changing page. > --------------------------------------- > > Key: RF-13524 > URL: https://issues.jboss.org/browse/RF-13524 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.0.0.CR1, 4.2.2.Final > Environment: Windows Vista, Web Sphere 8.5, Java jdk 1.5, maven > Reporter: Carlos Mauro C?rdenas Fern?ndez > Labels: waiting_on_user > > I have a tooltip implemented on a main page, but when you click the link tooltip box gets stuck on next page > > {code} > > > onhide="false" hideEvent="mouseleave"> > > > {code} > problem.png > > I tried to change the tooltip parameter but didnt find the solution. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:26:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:26:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13533) Port the jQuery noConlfict fixes back to RF 4.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13533. -------------------------------- Resolution: Won't Fix This has been addressed in RichFaces 4.5 > Port the jQuery noConlfict fixes back to RF 4.3.x > ------------------------------------------------- > > Key: RF-13533 > URL: https://issues.jboss.org/browse/RF-13533 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7, RichFaces 4.2.3.Final, Debian Wheezy x86_64 > Reporter: Mark Cave-Ayland > > jQuery usage by RichFaces was corrected to work properly with jQuery noConclift in RF 4.5/5.0 with the resolution of RF-12936. This issue addresses backporting those changes into the 4.3.x branch. > ---- > Summary was: rich:fileUpload doesn't work with jQuery in noConflict mode > Hi all, > For compatibility with other components used within our application, we manually include a copy of jQuery in noConflict mode within our page header template rather than let RichFaces include its own. > This works fine for us, except when using the component which throws a Javascript error. Casual inspection of the source shows that this is due to a typing error where $ is used directly within fileupload.js rather than using the passed-in parameter. The following diff fixes the error for us: > {code} > $ diff -u fileupload.js.orig fileupload.js > --- fileupload.js.orig 2014-02-04 15:07:05.000000000 +0000 > +++ fileupload.js 2014-02-04 15:08:32.000000000 +0000 > @@ -98,7 +98,7 @@ > > richfaces.BaseComponent.extend(richfaces.ui.FileUpload); > > - $.extend(richfaces.ui.FileUpload.prototype, (function () { > + jQuery.extend(richfaces.ui.FileUpload.prototype, (function () { > > return { > name: "FileUpload", > {code} > The bug was found during the development of our main application under RF 4.2.3.Final, however a quick test with RF 4.3.5 JARs shows that the bug is still present. > Many thanks, > Mark. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:28:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:28:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13545) Simpleapp: Support for servlets/Java EE containers at generation time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13545: ------------------------------- Fix Version/s: 4.5-Tracking > Simpleapp: Support for servlets/Java EE containers at generation time > --------------------------------------------------------------------- > > Key: RF-13545 > URL: https://issues.jboss.org/browse/RF-13545 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: archetype > Affects Versions: 5.0.0.Alpha3 > Environment: simpleapp archetype > Reporter: Juraj H?ska > Priority: Minor > Fix For: 4.5-Tracking > > > In [this|https://community.jboss.org/message/857393#857393] discussion [~bleathem] wrote: > {quote} > I'd like to see us support both servlet and EE containers with our archetypes at generation time. We'd build in the archetype conditional asking the user if the generated project should target EE or servlet containers. This should also be done in our Forge plugin. > {quote} > {quote} > Taking a profile approach leaves a lot of unnecessary clutter in their pom.xml. whereas asking at archetype evaluation time we can trim the unnecessary pieces out of the pom.xml. > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:28:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:28:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13546) Forge plugin: support for Servlet or JavaEE containers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13546: ------------------------------- Fix Version/s: 4.5-Tracking > Forge plugin: support for Servlet or JavaEE containers > ------------------------------------------------------ > > Key: RF-13546 > URL: https://issues.jboss.org/browse/RF-13546 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Juraj H?ska > Priority: Minor > Fix For: 4.5-Tracking > > > There should be taken similar approach as in RF-13545 for RichFaces Forge plugin. > That is to ask whether an user wants Servlet or Java EE container, and then create a profile for it. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:28:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:28:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13561) Remove PushFilter deprecated in RF 4.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13561: ------------------------------- Fix Version/s: 4.5-Tracking > Remove PushFilter deprecated in RF 4.1 > -------------------------------------- > > Key: RF-13561 > URL: https://issues.jboss.org/browse/RF-13561 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha3 > Reporter: Luk?? Fry? > Fix For: 4.5-Tracking > > > {code} > private void logPushFilterWarning(ServletContext servletContext) { > String message; > if (servletContext.getMajorVersion() >= 3) { > message = "PushFilter has been deprecated, you can remove its declaration in Servlets 3 environment"; > } else { > message = "PushFilter has been deprecated, you should use PushServlet instead"; > } > LOGGER.warn(message); > } > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:28:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:28:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13562) New showcase throws an NPE when reading the taglib In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13562: ------------------------------- Fix Version/s: 5-Tracking > New showcase throws an NPE when reading the taglib > -------------------------------------------------- > > Key: RF-13562 > URL: https://issues.jboss.org/browse/RF-13562 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Luk?? Macko > Priority: Minor > Fix For: 5-Tracking > > > When new showcase is deployed to WildFly usage of ui:repeat in table showing VDL docs https://github.com/richfaces/richfaces/blob/RF-12901-showcase/examples/bootstrap-showcase/src/main/webapp/resources/fragment/attributesRepeat.xhtml#L7 > throws an Exception > {code} > {{16:28:08,647 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (default task-3) Error Rendering View[/component/autocomplete/index.xhtml]: javax.el.ELException: //home/lmacko/workspace/richfaces/examples/bootstrap-showcase/target/m2e-wtp/web-resources/resources/fragment/attributesRepeat.xhtml @7,64 value="#{attributesList}": //home/lmacko/workspace/richfaces/examples/bootstrap-showcase/target/m2e-wtp/web-resources/resources/taglib.xhtml @81,106 value="#{taglibReader.getDefaultAttributes(tag)}": java.lang.NullPointerException > at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:114) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.facelets.component.UIRepeat.getValue(UIRepeat.java:279) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.facelets.component.UIRepeat.getDataModel(UIRepeat.java:255) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.facelets.component.UIRepeat.setIndex(UIRepeat.java:523) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.facelets.component.UIRepeat.doVisitChildren(UIRepeat.java:790) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.facelets.component.UIRepeat.visitTree(UIRepeat.java:748) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.facelets.component.UIRepeat.visitTree(UIRepeat.java:754) [jsf-impl-2.2.5-jbossorg-3.jar:] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.application.view.FormOmittedChecker.check(FormOmittedChecker.java:91) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:445) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:133) [jsf-impl-2.2.5-jbossorg-3.jar:] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219) [jsf-impl-2.2.5-jbossorg-3.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:647) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40] > Caused by: javax.el.ELException: //home/lmacko/workspace/richfaces/examples/bootstrap-showcase/target/m2e-wtp/web-resources/resources/taglib.xhtml @81,106 value="#{taglibReader.getDefaultAttributes(tag)}": java.lang.NullPointerException > at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:114) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:112) [javax.el-3.0.0.jar:3.0.0] > at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:226) [javax.el-3.0.0.jar:3.0.0] > at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] > at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] > at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) [jsf-impl-2.2.5-jbossorg-3.jar:] > ... 41 more > Caused by: javax.el.ELException: java.lang.NullPointerException > at javax.el.ELUtil.invokeMethod(ELUtil.java:330) [javax.el-3.0.0.jar:3.0.0] > at javax.el.BeanELResolver.invoke(BeanELResolver.java:536) [javax.el-3.0.0.jar:3.0.0] > at javax.el.CompositeELResolver.invoke(CompositeELResolver.java:256) [javax.el-3.0.0.jar:3.0.0] > at com.sun.el.parser.AstValue.getValue(AstValue.java:136) [javax.el-3.0.0.jar:3.0.0] > at com.sun.el.parser.AstValue.getValue(AstValue.java:204) [javax.el-3.0.0.jar:3.0.0] > at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:226) [javax.el-3.0.0.jar:3.0.0] > at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] > at org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] > at com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109) [jsf-impl-2.2.5-jbossorg-3.jar:] > ... 46 more > Caused by: java.lang.NullPointerException > at org.richfaces.bootstrap.demo.TaglibReader.getAllAttributesFromTagName(TaglibReader.java:120) [:] > at org.richfaces.bootstrap.demo.TaglibReader.initAttributesForTagName(TaglibReader.java:124) [:] > at org.richfaces.bootstrap.demo.TaglibReader.getDefaultAttributes(TaglibReader.java:100) [:] > at sun.reflect.GeneratedMethodAccessor711.invoke(Unknown Source) [:1.7.0_40] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_40] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_40] > at javax.el.ELUtil.invokeMethod(ELUtil.java:326) [javax.el-3.0.0.jar:3.0.0] > ... 54 more}} > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:28:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:28:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13577) Handling non existing resource on WildFly causes NPE when there is custom error page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13577: ------------------------------- Fix Version/s: 4.5-Tracking > Handling non existing resource on WildFly causes NPE when there is custom error page > ------------------------------------------------------------------------------------ > > Key: RF-13577 > URL: https://issues.jboss.org/browse/RF-13577 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha4 > Environment: richfaces 5.0.0-SNAPSHOT & 5.Alpha3 & 5.Alpha2 > WildFly 8.0.0.Final & 8.0.0.CR1 > Reporter: Juraj H?ska > Fix For: 4.5-Tracking > > > When an application has custom error page for HTML error code 404, then handling of 404 can cause NPE on WildFly server. > The NPE being thrown is: > {code} > [31m21:15:59,981 ERROR [io.undertow.request] (default task-7) UT005023: Exception handling request to /metamer/faces/error/404.xhtml: javax.servlet.ServletException > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:659) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) [undertow-core-1.0.0.Final.jar:1.0.0.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] > Caused by: java.lang.NullPointerException > at javax.faces.component.UIComponent.getCurrentComponent(UIComponent.java:2138) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at javax.faces.event.ComponentSystemEvent.processListener(ComponentSystemEvent.java:111) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247) [jsf-impl-2.2.5-jbossorg-3.jar:] > at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:299) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:107) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219) [jsf-impl-2.2.5-jbossorg-3.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:647) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > {code} > When there is no custom error page, no exception is thrown to the server console. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:28:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:28:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13578) RF5 Editor Showcase console errors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13578: ------------------------------- Fix Version/s: 5-Tracking > RF5 Editor Showcase console errors > ---------------------------------- > > Key: RF-13578 > URL: https://issues.jboss.org/browse/RF-13578 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha4 > Reporter: Matej Novotny > Fix For: 5-Tracking > > > When accessing RF 5 showcase (for instance latest showcase [here|http://showcase-latest.richfaces.org/], you can notice that in web console there is following error: > {code} > ReferenceError: CKEDITOR is not defined ui.js:8774 > {code} > I believe this error started to appear after latest editor update and it might refer to [this|https://github.com/richfaces/richfaces/blob/master/framework/src/main/resources/META-INF/resources/io.richwidgets/input/editor.js#L268] code. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:30:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:30:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973906#comment-12973906 ] Brian Leathem commented on RF-13600: ------------------------------------ Is this still an issue? > metamer: malformedXML error on each ajax request on WildFly > ----------------------------------------------------------- > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5, 4.3.6 > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, (works on EAP 6.2) > Reporter: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3.x . > On every ajax request there is malformedXML error and the metamer status is set to ERROR. But all the outputs are updated and it seems that all is working (except the status and autocomplete) as expected. > # open e.g. http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml > # click on the submit button > # see the status 'ERROR' > # open log, at the end you can see: > {code} > error[09:58:23.320]: Received 'error at malformedXML' event from > error[09:58:23.322]: [status=200] During update: javax.faces.ViewState not found > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:30:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:30:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13607) Tables/Menus logged warnings for invalid children In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13607. -------------------------------- Resolution: Incomplete Description > Tables/Menus logged warnings for invalid children > ------------------------------------------------- > > Key: RF-13607 > URL: https://issues.jboss.org/browse/RF-13607 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-menu, component-tables > Affects Versions: 4.3.4 > Environment: JBoss EAP 6.1.1 > Reporter: Michael Colin > > Whenever you put an invalid child into a component like the rich:extendedDataTable I would expect to get an exception or a warning at the very least. Currently the component just seems to ignore those false children which makes debugging difficult (when trying to create a composite component of rich:column, for example) and might lead to false code to just stay where it is because it doesn't generate an error and is simply "forgotten". > Wrong code should generate harsh exceptions so it shows and can be fixed in a timely manner. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:30:17 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:30:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13644) Rich:editor JS Error in IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13644: ---------------------------------- Assignee: Pavol Pitonak QE can you verify this issue was resolved in 4.5.0-SNAPSHOT with the recent CKeditor upgrade? > Rich:editor JS Error in IE11 > ---------------------------- > > Key: RF-13644 > URL: https://issues.jboss.org/browse/RF-13644 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Internet Explorer 11. Websphere implementation of MyFaces > Reporter: Dmitry Volkov > Assignee: Pavol Pitonak > > CKEditor throws JS exception in IE11: > O=G.$.createEvent('KeyEvents'); > NotSupportedError > The issue is also described here: http://ckeditor.com/forums/CKEditor/3.6.6.1-error-in-IE11 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:50:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:50:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13600: ------------------------------- Assignee: Ji?? ?tefek > metamer: malformedXML error on each ajax request on WildFly > ----------------------------------------------------------- > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5, 4.3.6 > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, (works on EAP 6.2) > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3.x . > On every ajax request there is malformedXML error and the metamer status is set to ERROR. But all the outputs are updated and it seems that all is working (except the status and autocomplete) as expected. > # open e.g. http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml > # click on the submit button > # see the status 'ERROR' > # open log, at the end you can see: > {code} > error[09:58:23.320]: Received 'error at malformedXML' event from > error[09:58:23.322]: [status=200] During update: javax.faces.ViewState not found > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:50:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:50:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13391) jsf.ajax.addOnEvent not fired after r:ajax completes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973912#comment-12973912 ] Brian Leathem commented on RF-13391: ------------------------------------ Is this still an issue? > jsf.ajax.addOnEvent not fired after r:ajax completes > ---------------------------------------------------- > > Key: RF-13391 > URL: https://issues.jboss.org/browse/RF-13391 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha2 > Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 > Wildfly 8.0.0.Beta2-SNAPSHOT > Mojarra 2.2.4-jbossorg-1 20131017-1524 > Reporter: Cody Lerum > Labels: waiting_on_user > > Unsure if this is a bug or a limiation of using the r:ajax but with f:ajax I am able to listen for jsf.ajax events and for example > {code} > jsf.ajax.addOnEvent(function(data) { > if (data.status == 'success') > addFormGroupClasses(); > }); > {code} > This code is called after completion of an f:ajax but not for an r:ajax -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:54:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:54:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13203) a4j:queue should have status attribute In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13203: ------------------------------- Fix Version/s: 4.5-Tracking (was: 5-Tracking) > a4j:queue should have status attribute > -------------------------------------- > > Key: RF-13203 > URL: https://issues.jboss.org/browse/RF-13203 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.2 > Reporter: Jon?? Trantina > Labels: gss, queue > Fix For: 4.5-Tracking > > Original Estimate: 2 days > Remaining Estimate: 2 days > > a4j:queue should have status attribute, so it can connect to a4j:status. Consider the following example: > {noformat} > > > >
> > > > > > > >
> > > > > > {noformat} > By using the status attr. of a4j:queue, it would be possible to connect "slow" queue to "slowStatus" and thus every component that would be connected to the queue, would also be connected to the status. > Note in this example it would be simpler to set status attr. on the components themselves, but imagine there are more components connected to the queue. > I was also informed, that this functionality was present in RF 3.3. > Workarounds: > - set status attr on every component instead of on the queue- in larger applications this is not doable. > - use a4j:status JS API and a4j:queues' onsubmit and oncomplete methods- onsubmit and oncomplete a4j:queue are not implemented, so not working now -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:56:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:56:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13168. -------------------------------- Resolution: Done > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Luk?? Fry? > Labels: interop, jsf22 > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, Jira-WFLY-UT.tar, xaa, xaa, xab, xab, xac, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:56:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:56:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12783) Upgrade compiler plugin to >3.1 (once released) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12783: ------------------------------- Assignee: (was: Luk?? Fry?) > Upgrade compiler plugin to >3.1 (once released) > ----------------------------------------------- > > Key: RF-12783 > URL: https://issues.jboss.org/browse/RF-12783 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > As tracked in JBBUILD-725, it was necessary to downgrade compiler plugin version from 3.0 to 2.3.2. > We need to upgrade to 3.1 (once released) or upgrade JBoss Parent (if upgrade will be available there). > Upstream issue: http://jira.codehaus.org/browse/MCOMPILER-187 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:58:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:58:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12783) Upgrade compiler plugin to >3.1 (once released) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973914#comment-12973914 ] Brian Leathem commented on RF-12783: ------------------------------------ {{[MCOMPILER-205|https://jira.codehaus.org/browse/MCOMPILER-205]}} is still open, scheduling this to 4.5-Tracking for follow-up. > Upgrade compiler plugin to >3.1 (once released) > ----------------------------------------------- > > Key: RF-12783 > URL: https://issues.jboss.org/browse/RF-12783 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Fix For: 4.5-Tracking > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > As tracked in JBBUILD-725, it was necessary to downgrade compiler plugin version from 3.0 to 2.3.2. > We need to upgrade to 3.1 (once released) or upgrade JBoss Parent (if upgrade will be available there). > Upstream issue: http://jira.codehaus.org/browse/MCOMPILER-187 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:58:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:58:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12783) Upgrade compiler plugin to >3.1 (once released) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12783: ------------------------------- Fix Version/s: 4.5-Tracking > Upgrade compiler plugin to >3.1 (once released) > ----------------------------------------------- > > Key: RF-12783 > URL: https://issues.jboss.org/browse/RF-12783 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Fix For: 4.5-Tracking > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > As tracked in JBBUILD-725, it was necessary to downgrade compiler plugin version from 3.0 to 2.3.2. > We need to upgrade to 3.1 (once released) or upgrade JBoss Parent (if upgrade will be available there). > Upstream issue: http://jira.codehaus.org/browse/MCOMPILER-187 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:58:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:58:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13251: ------------------------------- Labels: waiting_on_user (was: ) Assignee: (was: Luk?? Fry?) > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Priority: Minor > Labels: waiting_on_user > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Thu Jun 5 18:58:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 5 Jun 2014 18:58:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13477) Framework tests - welcomeFile does not work correctly on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13477. -------------------------------- Assignee: (was: Luk?? Fry?) Resolution: Rejected > Framework tests - welcomeFile does not work correctly on WildFly > ---------------------------------------------------------------- > > Key: RF-13477 > URL: https://issues.jboss.org/browse/RF-13477 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha3 > Reporter: Luk?? Fry? > > tests were configured to use following welcome file configuration: > {code} > .welcomeFile("faces/index.xhtml") > .welcomeFile("index.jsf") > {code} > but wildfly didn't accept anything else than > {code} > index.jsf > {code} > and JBoss AS didn't work on anythung else than > {code} > faces/index.xhtml > {code} > https://github.com/richfaces/richfaces/blob/master/build/build-resources/src/main/java/org/richfaces/deployment/Deployment.java#L93 > ---- > as a workaround, I have made the usage of welcomefile conditional. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 02:56:15 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 6 Jun 2014 02:56:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13659) Autocomplete cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973973#comment-12973973 ] Juraj H?ska commented on RF-13659: ---------------------------------- I can not reproduce this issue. The only issue I am able to reproduce is RF-13640. > Autocomplete cannot select option on IE11 > ----------------------------------------- > > Key: RF-13659 > URL: https://issues.jboss.org/browse/RF-13659 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5, 4.3.6, 4.3.7 > Environment: Internet Explorer 11 > Reporter: Alexandre Palmeira > Assignee: Juraj H?ska > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > Issues: > User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > however clicking on the item will select the option correctly. EXCEPT autocomplete (RF4), where it will not select anything. > workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > User cannot select option with keyboard. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 04:08:15 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 6 Jun 2014 04:08:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov reassigned RF-13658: ---------------------------------- Assignee: Michal Petrov > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 04:10:15 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 6 Jun 2014 04:10:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973993#comment-12973993 ] Michal Petrov commented on RF-13658: ------------------------------------ I tried resetting to [49fe32a3ac1390665aaafa5d3b6e3ec55b9f26e9|https://github.com/richfaces/richfaces/commit/49fe32a3ac1390665aaafa5d3b6e3ec55b9f26e9] (before the EPVC merge/update); the trees do not work but the ajax updates do. Will investigate further. > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 10:38:17 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Jun 2014 10:38:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13659) Autocomplete cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974193#comment-12974193 ] Brian Leathem commented on RF-13659: ------------------------------------ [~apalmeira] please provide sample code and instructions to reproduce. > Autocomplete cannot select option on IE11 > ----------------------------------------- > > Key: RF-13659 > URL: https://issues.jboss.org/browse/RF-13659 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5, 4.3.6, 4.3.7 > Environment: Internet Explorer 11 > Reporter: Alexandre Palmeira > Assignee: Juraj H?ska > Labels: waiting_on_user > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > Issues: > User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > however clicking on the item will select the option correctly. EXCEPT autocomplete (RF4), where it will not select anything. > workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > User cannot select option with keyboard. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 10:38:17 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Jun 2014 10:38:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13659) Autocomplete cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13659: ------------------------------- Labels: waiting_on_user (was: ) > Autocomplete cannot select option on IE11 > ----------------------------------------- > > Key: RF-13659 > URL: https://issues.jboss.org/browse/RF-13659 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5, 4.3.6, 4.3.7 > Environment: Internet Explorer 11 > Reporter: Alexandre Palmeira > Assignee: Juraj H?ska > Labels: waiting_on_user > > Components: autocomplete, select, inplaceSelect. > Works on IE 10. > Issues: > User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class. > however clicking on the item will select the option correctly. EXCEPT autocomplete (RF4), where it will not select anything. > workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller. > User cannot select option with keyboard. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 11:24:17 2014 From: issues at jboss.org (=?UTF-8?Q?Christophe_Port=C3=A9_=28JIRA=29?=) Date: Fri, 6 Jun 2014 11:24:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12764) rich:select - javascript error when using myfaces with french locale In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974215#comment-12974215 ] Christophe Port? commented on RF-12764: --------------------------------------- This issue affects also the current 4.3.7 version, and is quite critical, as when the failing javascript is added to the current page, major part of the page fails and become unusable (no more ajax calls) > rich:select - javascript error when using myfaces with french locale > -------------------------------------------------------------------- > > Key: RF-12764 > URL: https://issues.jboss.org/browse/RF-12764 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR2 > Reporter: Dupont Dupont > Labels: patch_proposed > Fix For: 5-Tracking > > > Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error : > {code} > Uncaught SyntaxError: Unexpected identifier. > {code} > It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote. > To reproduce it, just add the following line in your jsf messages properties : > {code} > javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide. > {code} > And add a rich:select in your JSF page. > We end up with the javascript : > {code} > RichFaces.csv.addMessage({ 'UISELECTONE_INVALID': {detail:'{0} : Erreur de validation : la valeur n'est pas valide.',summary:'{0} : Erreur de validation : la valeur n'est pas valide.',severity:2} }); > {code} > This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes). > Resolved locally by modifying AddCSVMessageScript#appendcript > But perhaps I've missed some side effects. > {code:java} > @Override > public void appendScript(Appendable target) throws IOException { > String summary = facesMessage.getSummary(); > String detail = facesMessage.getDetail(); > int severity = facesMessage.getSeverity().getOrdinal(); > StringBuilder builder = new StringBuilder(); > ScriptUtils.appendEncodedString(builder, summary); > summary = builder.toString(); > builder = new StringBuilder(); > ScriptUtils.appendEncodedString(builder, detail); > detail = builder.toString(); > > String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity); > target.append(script); > } > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 17:42:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Jun 2014 17:42:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12764) rich:select - javascript error when using myfaces with french locale In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974375#comment-12974375 ] Brian Leathem commented on RF-12764: ------------------------------------ A github pull request with the proposed patch would be welcome. We can then review the patch and run our tests to check for regressions. > rich:select - javascript error when using myfaces with french locale > -------------------------------------------------------------------- > > Key: RF-12764 > URL: https://issues.jboss.org/browse/RF-12764 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR2 > Reporter: Dupont Dupont > Labels: patch_proposed > Fix For: 4.5-Tracking > > > Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error : > {code} > Uncaught SyntaxError: Unexpected identifier. > {code} > It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote. > To reproduce it, just add the following line in your jsf messages properties : > {code} > javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide. > {code} > And add a rich:select in your JSF page. > We end up with the javascript : > {code} > RichFaces.csv.addMessage({ 'UISELECTONE_INVALID': {detail:'{0} : Erreur de validation : la valeur n'est pas valide.',summary:'{0} : Erreur de validation : la valeur n'est pas valide.',severity:2} }); > {code} > This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes). > Resolved locally by modifying AddCSVMessageScript#appendcript > But perhaps I've missed some side effects. > {code:java} > @Override > public void appendScript(Appendable target) throws IOException { > String summary = facesMessage.getSummary(); > String detail = facesMessage.getDetail(); > int severity = facesMessage.getSeverity().getOrdinal(); > StringBuilder builder = new StringBuilder(); > ScriptUtils.appendEncodedString(builder, summary); > summary = builder.toString(); > builder = new StringBuilder(); > ScriptUtils.appendEncodedString(builder, detail); > detail = builder.toString(); > > String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity); > target.append(script); > } > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Fri Jun 6 17:42:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 6 Jun 2014 17:42:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12764) rich:select - javascript error when using myfaces with french locale In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-12764: ------------------------------- Fix Version/s: 4.5-Tracking (was: 5-Tracking) > rich:select - javascript error when using myfaces with french locale > -------------------------------------------------------------------- > > Key: RF-12764 > URL: https://issues.jboss.org/browse/RF-12764 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.CR2 > Reporter: Dupont Dupont > Labels: patch_proposed > Fix For: 4.5-Tracking > > > Using RF 4.3.0.CR2, using rich:select with french locale on Myfaces produces the following javascript error : > {code} > Uncaught SyntaxError: Unexpected identifier. > {code} > It appears when javax.faces.component.UISelectOne.INVALID error message has a value containing a single quote. > To reproduce it, just add the following line in your jsf messages properties : > {code} > javax.faces.component.UISelectOne.INVALID = {0} : Erreur de validation : la valeur n''est pas valide. > {code} > And add a rich:select in your JSF page. > We end up with the javascript : > {code} > RichFaces.csv.addMessage({ 'UISELECTONE_INVALID': {detail:'{0} : Erreur de validation : la valeur n'est pas valide.',summary:'{0} : Erreur de validation : la valeur n'est pas valide.',severity:2} }); > {code} > This error impacts users of Websphere 8 (tested on 8.0.0.3) with french locale (myfaces provides a default message containing simple quotes). > Resolved locally by modifying AddCSVMessageScript#appendcript > But perhaps I've missed some side effects. > {code:java} > @Override > public void appendScript(Appendable target) throws IOException { > String summary = facesMessage.getSummary(); > String detail = facesMessage.getDetail(); > int severity = facesMessage.getSeverity().getOrdinal(); > StringBuilder builder = new StringBuilder(); > ScriptUtils.appendEncodedString(builder, summary); > summary = builder.toString(); > builder = new StringBuilder(); > ScriptUtils.appendEncodedString(builder, detail); > detail = builder.toString(); > > String script = MessageFormat.format(MESSAGE_OBJECT, messageId, summary, detail, severity); > target.append(script); > } > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 02:50:15 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 9 Jun 2014 02:50:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974452#comment-12974452 ] Ji?? ?tefek commented on RF-13600: ---------------------------------- Problem still occurs in 4.3.x Metamer on WildFly (tried 8.0.0.Final and 8.1.0.Final). But I can't reproduce this behavior with 5.0.x Metamer on AS 7.1.1. > metamer: malformedXML error on each ajax request on WildFly > ----------------------------------------------------------- > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5, 4.3.6 > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, (works on EAP 6.2) > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3.x . > On every ajax request there is malformedXML error and the metamer status is set to ERROR. But all the outputs are updated and it seems that all is working (except the status and autocomplete) as expected. > # open e.g. http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml > # click on the submit button > # see the status 'ERROR' > # open log, at the end you can see: > {code} > error[09:58:23.320]: Received 'error at malformedXML' event from > error[09:58:23.322]: [status=200] During update: javax.faces.ViewState not found > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 07:46:16 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 9 Jun 2014 07:46:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13644) Rich:editor JS Error in IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13644: ---------------------------------- Assignee: Ji?? ?tefek (was: Pavol Pitonak) > Rich:editor JS Error in IE11 > ---------------------------- > > Key: RF-13644 > URL: https://issues.jboss.org/browse/RF-13644 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Internet Explorer 11. Websphere implementation of MyFaces > Reporter: Dmitry Volkov > Assignee: Ji?? ?tefek > > CKEditor throws JS exception in IE11: > O=G.$.createEvent('KeyEvents'); > NotSupportedError > The issue is also described here: http://ckeditor.com/forums/CKEditor/3.6.6.1-error-in-IE11 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 09:24:16 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 9 Jun 2014 09:24:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13644) Rich:editor JS Error in IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974606#comment-12974606 ] Ji?? ?tefek commented on RF-13644: ---------------------------------- I can confirm, that there are no JS errors in browser console in 4.5.0-SNAPSHOT. Verified in Metamer. > Rich:editor JS Error in IE11 > ---------------------------- > > Key: RF-13644 > URL: https://issues.jboss.org/browse/RF-13644 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Internet Explorer 11. Websphere implementation of MyFaces > Reporter: Dmitry Volkov > Assignee: Ji?? ?tefek > Labels: IE11 > > CKEditor throws JS exception in IE11: > O=G.$.createEvent('KeyEvents'); > NotSupportedError > The issue is also described here: http://ckeditor.com/forums/CKEditor/3.6.6.1-error-in-IE11 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 09:24:16 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 9 Jun 2014 09:24:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13644) Rich:editor JS Error in IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13644: ----------------------------- Labels: IE11 (was: ) > Rich:editor JS Error in IE11 > ---------------------------- > > Key: RF-13644 > URL: https://issues.jboss.org/browse/RF-13644 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Internet Explorer 11. Websphere implementation of MyFaces > Reporter: Dmitry Volkov > Assignee: Ji?? ?tefek > Labels: IE11 > > CKEditor throws JS exception in IE11: > O=G.$.createEvent('KeyEvents'); > NotSupportedError > The issue is also described here: http://ckeditor.com/forums/CKEditor/3.6.6.1-error-in-IE11 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 12:51:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Jun 2014 12:51:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13644) Rich:editor JS Error in IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13644. -------------------------------- Assignee: Luk?? Fry? (was: Ji?? ?tefek) Fix Version/s: 4.5.0.Alpha3 Resolution: Done Resolved with CKeditor upgrade. > Rich:editor JS Error in IE11 > ---------------------------- > > Key: RF-13644 > URL: https://issues.jboss.org/browse/RF-13644 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Internet Explorer 11. Websphere implementation of MyFaces > Reporter: Dmitry Volkov > Assignee: Luk?? Fry? > Labels: IE11 > Fix For: 4.5.0.Alpha3 > > > CKEditor throws JS exception in IE11: > O=G.$.createEvent('KeyEvents'); > NotSupportedError > The issue is also described here: http://ckeditor.com/forums/CKEditor/3.6.6.1-error-in-IE11 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 12:53:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Jun 2014 12:53:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974687#comment-12974687 ] Brian Leathem commented on RF-13600: ------------------------------------ RichFaces 4.3 does not work with JSF 2.2 and isnot expected to work on WildFly - there is no sense in testing that configuration. WildFly should be tested with RichFaces 4.5 / 5.0 where we support JSF 2.2. > metamer: malformedXML error on each ajax request on WildFly > ----------------------------------------------------------- > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5, 4.3.6 > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, (works on EAP 6.2) > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3.x . > On every ajax request there is malformedXML error and the metamer status is set to ERROR. But all the outputs are updated and it seems that all is working (except the status and autocomplete) as expected. > # open e.g. http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml > # click on the submit button > # see the status 'ERROR' > # open log, at the end you can see: > {code} > error[09:58:23.320]: Received 'error at malformedXML' event from > error[09:58:23.322]: [status=200] During update: javax.faces.ViewState not found > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 13:49:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Jun 2014 13:49:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13661) De-couple the RichFaces.BaseComponent implementation from its JSF backend In-Reply-To: References: Message-ID: Brian Leathem created RF-13661: ---------------------------------- Summary: De-couple the RichFaces.BaseComponent implementation from its JSF backend Key: RF-13661 URL: https://issues.jboss.org/browse/RF-13661 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.5-Tracking Investigate whether we can de-couple a RichFaces.BaseComponent based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 14:55:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Jun 2014 14:55:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13661) De-couple the RichFaces.BaseComponent implementation from its JSF backend In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974699#comment-12974699 ] Brian Leathem commented on RF-13661: ------------------------------------ Fortunately {{RichFaces.BaseComponent}} itself doesn't contain any jsf.js integration. De-coupling a component for its JSF backend then should simply involve replacing direct {{RichFaces.ajax}} calls with an event mechanism. On a related note, much of the {{RichFaces.BaseComponent}} merely wraps some specific jQuery functionality. The client-side codebase could conceivably be simplified by removing the unused and redundant abstractions. > De-couple the RichFaces.BaseComponent implementation from its JSF backend > ------------------------------------------------------------------------- > > Key: RF-13661 > URL: https://issues.jboss.org/browse/RF-13661 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5-Tracking > > > Investigate whether we can de-couple a RichFaces.BaseComponent based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 14:55:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Jun 2014 14:55:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13661) De-couple the RichFaces.BaseComponent implementation from its JSF backend In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13661: ------------------------------- Description: Investigate whether we can de-couple a {{RichFaces.BaseComponent}} based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC. (was: Investigate whether we can de-couple a RichFaces.BaseComponent based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC.) > De-couple the RichFaces.BaseComponent implementation from its JSF backend > ------------------------------------------------------------------------- > > Key: RF-13661 > URL: https://issues.jboss.org/browse/RF-13661 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5-Tracking > > > Investigate whether we can de-couple a {{RichFaces.BaseComponent}} based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 17:09:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Jun 2014 17:09:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13585) Re-factor the components demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13585: ------------------------------- Summary: Re-factor the components demo (was: Drop the components demo) > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > Drop the components demo from the RichFaces 4.5 framework build. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 17:09:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Jun 2014 17:09:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13585) Re-factor the components demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13585: ------------------------------- Description: Re-factor the components demo to work with RichFaces 4.5 (was: Drop the components demo from the RichFaces 4.5 framework build.) > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > Re-factor the components demo to work with RichFaces 4.5 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 17:09:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Jun 2014 17:09:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13585) Re-factor the components demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13585: ---------------------------------- Assignee: Brian Leathem (was: Michal Petrov) > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > Re-factor the components demo to work with RichFaces 4.5 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 17:11:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 9 Jun 2014 17:11:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13585) Re-factor the components demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974714#comment-12974714 ] Brian Leathem commented on RF-13585: ------------------------------------ This issue originally addressed removing the components-demo altogether, however in bringing richfaces 4.5 to a release ready state I realized the components-demos are handy to have around to reproduce issues with individual components. > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > Re-factor the components demo to work with RichFaces 4.5 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 18:15:17 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 9 Jun 2014 18:15:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974721#comment-12974721 ] Juraj H?ska commented on RF-13658: ---------------------------------- I am adding some of my findings, leaving the issues which [~michpetrov] already found. *tabPanel*: can not be switched * reproducible e.g. in Metamer welcome page * it is occuring when switchType == ajax * it is switched to the next panel when refreshed *togglePanel*: the same apply as above *collapsiblePanel*: same *accordion*: can not be switched neither when ajax mode nor in client mode *editor*: is not rendered * getting 404 on these resources: ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/skin.js ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor_gecko.css *autocomplete*: does not work in ajax mode *push*: does not work, does not recieve any pushes * following error is thrown * {code}23:58:59,784 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/metamer].[Faces Servlet]] (http--0.0.0.0-8080-6) Servlet.service() for servlet Faces Servlet threw exception: java.lang.IllegalArgumentException: pushTopic request parameter must be present at org.richfaces.resource.PushResource.encode(PushResource.java:85) [richfaces-a4j-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:184) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] {code} > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Mon Jun 9 18:35:15 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 9 Jun 2014 18:35:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974721#comment-12974721 ] Juraj H?ska edited comment on RF-13658 at 6/9/14 6:35 PM: ---------------------------------------------------------- I am adding some of my findings, leaving the issues which [~michpetrov] already found. *tabPanel*: can not be switched * reproducible e.g. in Metamer welcome page * it is occuring when switchType == ajax * it is switched to the next panel when refreshed *togglePanel*: the same apply as above *collapsiblePanel*: same *accordion*: can not be switched neither when ajax mode nor in client mode *editor*: is not rendered * getting 404 on these resources: ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/skin.js ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor_gecko.css ** cause by CKE Editor upgrade to 4.1.1 with [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit *autocomplete*: does not work in ajax mode *push*: does not work, does not recieve any pushes * following error is thrown * {code}23:58:59,784 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/metamer].[Faces Servlet]] (http--0.0.0.0-8080-6) Servlet.service() for servlet Faces Servlet threw exception: java.lang.IllegalArgumentException: pushTopic request parameter must be present at org.richfaces.resource.PushResource.encode(PushResource.java:85) [richfaces-a4j-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:184) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] {code} was (Author: jhuska): I am adding some of my findings, leaving the issues which [~michpetrov] already found. *tabPanel*: can not be switched * reproducible e.g. in Metamer welcome page * it is occuring when switchType == ajax * it is switched to the next panel when refreshed *togglePanel*: the same apply as above *collapsiblePanel*: same *accordion*: can not be switched neither when ajax mode nor in client mode *editor*: is not rendered * getting 404 on these resources: ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/skin.js ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor_gecko.css *autocomplete*: does not work in ajax mode *push*: does not work, does not recieve any pushes * following error is thrown * {code}23:58:59,784 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/metamer].[Faces Servlet]] (http--0.0.0.0-8080-6) Servlet.service() for servlet Faces Servlet threw exception: java.lang.IllegalArgumentException: pushTopic request parameter must be present at org.richfaces.resource.PushResource.encode(PushResource.java:85) [richfaces-a4j-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:184) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] {code} > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 01:39:15 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 10 Jun 2014 01:39:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974742#comment-12974742 ] Ji?? ?tefek commented on RF-13600: ---------------------------------- Thanks for clarification [~bleathem]. Rejecting. > metamer: malformedXML error on each ajax request on WildFly > ----------------------------------------------------------- > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5, 4.3.6 > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, (works on EAP 6.2) > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3.x . > On every ajax request there is malformedXML error and the metamer status is set to ERROR. But all the outputs are updated and it seems that all is working (except the status and autocomplete) as expected. > # open e.g. http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml > # click on the submit button > # see the status 'ERROR' > # open log, at the end you can see: > {code} > error[09:58:23.320]: Received 'error at malformedXML' event from > error[09:58:23.322]: [status=200] During update: javax.faces.ViewState not found > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 01:39:15 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 10 Jun 2014 01:39:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RF-13600. ------------------------------ Resolution: Rejected > metamer: malformedXML error on each ajax request on WildFly > ----------------------------------------------------------- > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5, 4.3.6 > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, (works on EAP 6.2) > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3.x . > On every ajax request there is malformedXML error and the metamer status is set to ERROR. But all the outputs are updated and it seems that all is working (except the status and autocomplete) as expected. > # open e.g. http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml > # click on the submit button > # see the status 'ERROR' > # open log, at the end you can see: > {code} > error[09:58:23.320]: Received 'error at malformedXML' event from > error[09:58:23.322]: [status=200] During update: javax.faces.ViewState not found > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 02:53:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 10 Jun 2014 02:53:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974721#comment-12974721 ] Juraj H?ska edited comment on RF-13658 at 6/10/14 2:52 AM: ----------------------------------------------------------- I am adding some of my findings, omitting issues which [~michpetrov] already found. *tabPanel*: can not be switched * reproducible e.g. in Metamer welcome page * it is occuring when switchType == ajax * it is switched to the next panel when refreshed *togglePanel*: the same apply as above *collapsiblePanel*: same *accordion*: can not be switched neither when ajax mode nor in client mode *editor*: is not rendered * getting 404 on these resources: ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/skin.js ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor_gecko.css ** caused by CKE Editor upgrade to 4.1.1 with [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit *autocomplete*: does not work in ajax mode *push*: does not work, does not recieve any pushes * following error is thrown * {code}23:58:59,784 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/metamer].[Faces Servlet]] (http--0.0.0.0-8080-6) Servlet.service() for servlet Faces Servlet threw exception: java.lang.IllegalArgumentException: pushTopic request parameter must be present at org.richfaces.resource.PushResource.encode(PushResource.java:85) [richfaces-a4j-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:184) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] {code} was (Author: jhuska): I am adding some of my findings, leaving the issues which [~michpetrov] already found. *tabPanel*: can not be switched * reproducible e.g. in Metamer welcome page * it is occuring when switchType == ajax * it is switched to the next panel when refreshed *togglePanel*: the same apply as above *collapsiblePanel*: same *accordion*: can not be switched neither when ajax mode nor in client mode *editor*: is not rendered * getting 404 on these resources: ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/skin.js ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor_gecko.css ** cause by CKE Editor upgrade to 4.1.1 with [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit *autocomplete*: does not work in ajax mode *push*: does not work, does not recieve any pushes * following error is thrown * {code}23:58:59,784 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/metamer].[Faces Servlet]] (http--0.0.0.0-8080-6) Servlet.service() for servlet Faces Servlet threw exception: java.lang.IllegalArgumentException: pushTopic request parameter must be present at org.richfaces.resource.PushResource.encode(PushResource.java:85) [richfaces-a4j-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:184) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] {code} > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 03:17:15 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 10 Jun 2014 03:17:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974758#comment-12974758 ] Ji?? ?tefek commented on RF-13658: ---------------------------------- The editor should be rendered now ([commit|https://github.com/richfaces/richfaces-qa/commit/dcb1259a69bb6c0055b43b9192d713d6e31c20b3]), with the upgrade of CKEditor there was a change of default skin ([line|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29#diff-62a6d4702518fa2f42f90e5aa53cd3acL67]). > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 04:43:17 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 10 Jun 2014 04:43:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974721#comment-12974721 ] Juraj H?ska edited comment on RF-13658 at 6/10/14 4:42 AM: ----------------------------------------------------------- I am adding some of my findings, omitting issues which [~michpetrov] already found. *tabPanel*: can not be switched * reproducible e.g. in Metamer welcome page * it is occuring when switchType == ajax * it is switched to the next panel when refreshed *togglePanel*: the same apply as above *collapsiblePanel*: same *accordion*: can not be switched neither when ajax mode nor in client mode -*editor*: is not rendered- * -getting 404 on these resources:- ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/skin.js ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor_gecko.css ** -caused by CKE Editor upgrade to 4.1.1 with [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit- * it is metamer issue, already fixed, thanks [~jstefek] *autocomplete*: does not work in ajax mode *push*: does not work, does not recieve any pushes * following error is thrown * {code}23:58:59,784 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/metamer].[Faces Servlet]] (http--0.0.0.0-8080-6) Servlet.service() for servlet Faces Servlet threw exception: java.lang.IllegalArgumentException: pushTopic request parameter must be present at org.richfaces.resource.PushResource.encode(PushResource.java:85) [richfaces-a4j-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:184) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] {code} was (Author: jhuska): I am adding some of my findings, omitting issues which [~michpetrov] already found. *tabPanel*: can not be switched * reproducible e.g. in Metamer welcome page * it is occuring when switchType == ajax * it is switched to the next panel when refreshed *togglePanel*: the same apply as above *collapsiblePanel*: same *accordion*: can not be switched neither when ajax mode nor in client mode *editor*: is not rendered * getting 404 on these resources: ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/skin.js ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor_gecko.css ** caused by CKE Editor upgrade to 4.1.1 with [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit *autocomplete*: does not work in ajax mode *push*: does not work, does not recieve any pushes * following error is thrown * {code}23:58:59,784 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/metamer].[Faces Servlet]] (http--0.0.0.0-8080-6) Servlet.service() for servlet Faces Servlet threw exception: java.lang.IllegalArgumentException: pushTopic request parameter must be present at org.richfaces.resource.PushResource.encode(PushResource.java:85) [richfaces-a4j-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:184) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] {code} > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 08:15:17 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 10 Jun 2014 08:15:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12292) "this" in oncomplete of a4j:commandButton returns window object. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-12292: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > "this" in oncomplete of a4j:commandButton returns window object. > ---------------------------------------------------------------- > > Key: RF-12292 > URL: https://issues.jboss.org/browse/RF-12292 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.2.Final > Environment: Windows XP SP3, Weblogic 10.3.5, JSF 2.0.4, RF 4.2.2 Final > Reporter: Nikolai Alexeev > Assignee: Luk?? Fry? > Priority: Minor > Labels: 45x, a4j_commandbutton > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > When using "this" operator in oncomplete attribute of a4j:commandButton user gets window object instead of expected button object. In RF3 everything was as expected. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 08:19:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 10 Jun 2014 08:19:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13307) Support java.util.Collection in iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13307: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Support java.util.Collection in iteration components > ---------------------------------------------------- > > Key: RF-13307 > URL: https://issues.jboss.org/browse/RF-13307 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Environment: Wildfly-8.0.0.Beta1 > Reporter: Matti Bickel > Assignee: Luk?? Fry? > Labels: 45x, jsf22 > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > JSF-2.2 now supports iteration over sets as in > {code:xml} > > #{elem.name} > > {code} > Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values. > Would be nice if RF catches up with JSF here. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 08:19:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 10 Jun 2014 08:19:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13200) Tree: Uncaught TypeError: Object # has no method '$' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13200: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Tree: Uncaught TypeError: Object # has no method '$' > ------------------------------------------------------------ > > Key: RF-13200 > URL: https://issues.jboss.org/browse/RF-13200 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss Application Server: Weld Integration 7.2.1.Final-redhat-10 > JBoss AS 7.2.1.Final-redhat-10 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 29.0.1547.65 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # deploy Metamer and open http://127.0.0.1:8080/metamer/faces/components/richTree/treeAdaptors.xhtml?templates=plain > # open node R-1 > # open node R-1.1 > # click on node R-1.1-M-V-1 > expected result: > * node should be selected > actual: > * exception in browser console: Uncaught TypeError: Object # has no method '$' > reason: > * response to Ajax request contains this code > {code} > RichFaces.$("form:richTree").__updateSelectionFromInput(); > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 08:39:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 10 Jun 2014 08:39:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13235) Tree - Row key conversion fails (UITree should not have generated @rowKeyConverter, since it is fully implemented in AbstractTree) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13235: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Tree - Row key conversion fails (UITree should not have generated @rowKeyConverter, since it is fully implemented in AbstractTree) > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-13235 > URL: https://issues.jboss.org/browse/RF-13235 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha2 > > > The row key generation for Tree stopped to work: > *got:*
> *expected:*
> ---- > The cause was that rowKeyConverter resolves to null, so plain toString on rowKey is used. > I was wondering why rowKeyConverter isn't resolved for Tree in Showcase - the problem is that CDK generates this attribute and thus its implementation in AbstractTree (which is the correct way of rowKeyResolution) isn't used at all. > I'm pretty sure this is caused by refactoring from tree-model-props.xml to use Java interfaces TreeProps and TreeCommonProps: > https://github.com/richfaces/richfaces/commit/62ab0fe3f00b44a166b522ecb71e1733897aeebe > However it's not clear why the rowKeyConverter wasn't generated in RF 4.3 when it wasn't marked as generate=false: > https://github.com/richfaces4/components/blob/master/iteration/ui/src/main/resources/META-INF/cdk/attributes/tree-model-props.xml#L48 > Note that in RF 5 it is generated because UIAdaptor has @Attribute which defaults to generate=true: > https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/ui/iteration/UIDataAdaptor.java#L612 > Workaround is marking rowKeyConverter as generate=false in AbstracTree (or maybe RowKeyConverter), but we should rather investigate why this issue happens. > ---- > This issue has bigger potential since during refactoring of properties, [~bleathem] could work with the same assumption as I did ^. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 09:03:17 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 10 Jun 2014 09:03:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974887#comment-12974887 ] Michal Petrov commented on RF-13658: ------------------------------------ The tree issue is fixed, I overlooked one backport from RF 5 (RF-13235). The ajax issue is caused by the EVPC update, prior to that we used our own visitContext (RenderExtendedVisitContext, now called ExtendedRenderVisitContext) when processing partial render during Render Response Phase, currently that context is not being created at the appropriate time and so the components that expect it don't provide the correct data for the response. [~lfryc], can you take a look at this? > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 10:13:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 10 Jun 2014 10:13:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13583) Backport the chart components to RichFaces 4.5 components module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13583: ------------------------------- Git Pull Request: https://github.com/richfaces/richfaces/pull/88 (was: https://github.com/richfaces/richfaces/pull/87) > Backport the chart components to RichFaces 4.5 components module > ---------------------------------------------------------------- > > Key: RF-13583 > URL: https://issues.jboss.org/browse/RF-13583 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Backport the chart components to RichFaces 4.5 components module -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 11:15:19 2014 From: issues at jboss.org (Ingo Weiss (JIRA)) Date: Tue, 10 Jun 2014 11:15:19 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12637) Zip exception when deploying RichFaces app with JSF 2.2 to JBoss AS 7.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ingo Weiss updated RF-12637: ---------------------------- Comment: was deleted (was: I am seeing this issue with JSF 2.1 as well. If I add: {code} com.sun.faces jsf-api 2.1.28 com.sun.faces jsf-impl 2.1.28 {code} and {code} org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL true {code} I can see JBoss using the bundled JSF: {code} 09:12:46,561 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 56) Initializing Mojarra 2.1.28 ( 20140303-1517 https://svn.java.net/svn/mojarra~svn/tags/2.1.28 at 12942) for context '/richfaces-photoalbum' {code} But then RichFaces fails: {code} 09:42:24,930 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 64) Unable to process annotations for url, vfs:/content/richfaces-photoalbum.war/WEB-INF/lib/richfaces-components-ui-4.3.5.Final-redhat-1.jar/META-INF/faces-config.xml. Reason: java.util.zip.ZipException: zip file is empty 09:42:24,930 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 64) : java.util.zip.ZipException: zip file is empty at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0-internal] at java.util.zip.ZipFile.(ZipFile.java:215) [rt.jar:1.7.0-internal] at java.util.zip.ZipFile.(ZipFile.java:145) [rt.jar:1.7.0-internal] at java.util.jar.JarFile.(JarFile.java:154) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.URLJarFile.(URLJarFile.java:88) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:221) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:216) [rt.jar:1.7.0-internal] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.URLJarFile.retrieve(URLJarFile.java:215) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:71) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:99) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:122) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:89) [rt.jar:1.7.0-internal] at com.sun.faces.config.JavaClassScanningAnnotationScanner.processClasspath(JavaClassScanningAnnotationScanner.java:166) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.JavaClassScanningAnnotationScanner.getAnnotatedClasses(JavaClassScanningAnnotationScanner.java:125) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.DelegatingAnnotationProvider.getAnnotatedClasses(DelegatingAnnotationProvider.java:85) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:841) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:793) [jsf-impl-2.1.28.jar:2.1.28] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0-internal] at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:351) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:216) [jsf-impl-2.1.28.jar:2.1.28] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0-internal] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0-internal] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0-internal] at org.jboss.threads.JBossThread.run(JBossThread.java:122) 09:42:24,958 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 64) Unable to process annotations for url, vfs:/content/richfaces-photoalbum.war/WEB-INF/lib/richfaces-core-impl-4.3.5.Final-redhat-1.jar/META-INF/faces-config.xml. Reason: java.util.zip.ZipException: zip file is empty 09:42:24,958 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 64) : java.util.zip.ZipException: zip file is empty at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0-internal] at java.util.zip.ZipFile.(ZipFile.java:215) [rt.jar:1.7.0-internal] at java.util.zip.ZipFile.(ZipFile.java:145) [rt.jar:1.7.0-internal] at java.util.jar.JarFile.(JarFile.java:154) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.URLJarFile.(URLJarFile.java:88) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:221) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:216) [rt.jar:1.7.0-internal] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.URLJarFile.retrieve(URLJarFile.java:215) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:71) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:99) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:122) [rt.jar:1.7.0-internal] at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:89) [rt.jar:1.7.0-internal] at com.sun.faces.config.JavaClassScanningAnnotationScanner.processClasspath(JavaClassScanningAnnotationScanner.java:166) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.JavaClassScanningAnnotationScanner.getAnnotatedClasses(JavaClassScanningAnnotationScanner.java:125) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.DelegatingAnnotationProvider.getAnnotatedClasses(DelegatingAnnotationProvider.java:85) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:841) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:793) [jsf-impl-2.1.28.jar:2.1.28] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0-internal] at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:351) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:216) [jsf-impl-2.1.28.jar:2.1.28] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0-internal] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0-internal] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0-internal] at org.jboss.threads.JBossThread.run(JBossThread.java:122) 09:42:24,997 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 64) Critical error during deployment: : com.sun.faces.config.ConfigurationException: Factory 'javax.faces.application.ApplicationFactory' was not configured properly. at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:305) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:219) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:361) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:216) [jsf-impl-2.1.28.jar:2.1.28] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0-internal] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0-internal] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0-internal] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: javax.faces.FacesException: org.jboss.as.weld.webtier.jsf.WeldApplicationFactory at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:645) [jsf-api-2.1.28.jar:2.1] at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:508) [jsf-api-2.1.28.jar:2.1] at javax.faces.FactoryFinder.access$400(FactoryFinder.java:138) [jsf-api-2.1.28.jar:2.1] at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:995) [jsf-api-2.1.28.jar:2.1] at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:342) [jsf-api-2.1.28.jar:2.1] at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:303) [jsf-impl-2.1.28.jar:2.1.28] ... 14 more Caused by: java.lang.InstantiationException: org.jboss.as.weld.webtier.jsf.WeldApplicationFactory at java.lang.Class.newInstance(Class.java:359) [rt.jar:1.7.0-internal] at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:643) [jsf-api-2.1.28.jar:2.1] ... 19 more 09:42:25,000 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/richfaces-photoalbum]] (ServerService Thread Pool -- 64) JBWEB000287: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: Factory 'javax.faces.application.ApplicationFactory' was not configured properly. at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:276) [jsf-impl-2.1.28.jar:2.1.28] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0-internal] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0-internal] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0-internal] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: com.sun.faces.config.ConfigurationException: Factory 'javax.faces.application.ApplicationFactory' was not configured properly. at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:305) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:219) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:361) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:216) [jsf-impl-2.1.28.jar:2.1.28] ... 11 more Caused by: javax.faces.FacesException: org.jboss.as.weld.webtier.jsf.WeldApplicationFactory at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:645) [jsf-api-2.1.28.jar:2.1] at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:508) [jsf-api-2.1.28.jar:2.1] at javax.faces.FactoryFinder.access$400(FactoryFinder.java:138) [jsf-api-2.1.28.jar:2.1] at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:995) [jsf-api-2.1.28.jar:2.1] at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:342) [jsf-api-2.1.28.jar:2.1] at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:303) [jsf-impl-2.1.28.jar:2.1.28] ... 14 more Caused by: java.lang.InstantiationException: org.jboss.as.weld.webtier.jsf.WeldApplicationFactory at java.lang.Class.newInstance(Class.java:359) [rt.jar:1.7.0-internal] at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:643) [jsf-api-2.1.28.jar:2.1] ... 19 more 09:42:25,002 ERROR [org.apache.catalina.core] (ServerService Thread Pool -- 64) JBWEB001103: Error detected during context /richfaces-photoalbum start, will stop it 09:42:25,004 SEVERE [javax.faces] (ServerService Thread Pool -- 64) Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup. 09:42:25,005 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 64) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.IllegalStateException: Could not find backup for factory javax.faces.application.ApplicationFactory. at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:1010) [jsf-api-2.1.28.jar:2.1] at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:342) [jsf-api-2.1.28.jar:2.1] at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:141) [jsf-impl-2.1.28.jar:2.1.28] at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.1.28.jar:2.1.28] at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3427) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3839) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0-internal] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0-internal] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0-internal] at org.jboss.threads.JBossThread.run(JBossThread.java:122) 09:42:25,007 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 64) MSC000001: Failed to start service jboss.web.deployment.default-host./richfaces-photoalbum: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./richfaces-photoalbum: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0-internal] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0-internal] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0-internal] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161) at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) ... 6 more 09:42:25,211 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "richfaces-photoalbum.war" was rolled back with the following failure message: {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./richfaces-photoalbum" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./richfaces-photoalbum: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}} {code}) > Zip exception when deploying RichFaces app with JSF 2.2 to JBoss AS 7.2 > ----------------------------------------------------------------------- > > Key: RF-12637 > URL: https://issues.jboss.org/browse/RF-12637 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.0.M2 > Environment: JBoss AS 7.2.0.Alpha1-SNAPSHOT (from 3 Dec 2012) > Mojarra 2.2.0-SNAPSHOT (after 2.2.0-m06) > RichFaces 4.3.0-SNAPSHOT > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > Labels: jsf22 > Attachments: jsf22.zip > > > # extract jsf22.zip > # open directory and build project with {{mvn clean package -Prelease}} > # download latest JBoss AS 7.2.0.Alpha1 from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/ > # add Mojarra 2.2.0-SNAPSHOT to JBoss AS as described in https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature > # deploy jsf22-jee6.war > result: > {quote} > 15:49:31,425 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "jsf22-jee6.war" > 15:49:32,644 WARN [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016012: Deployment deployment "jsf22-jee6.war" contains CDI annotations but beans.xml was not found. > 15:49:32,681 INFO [org.jboss.web] (ServerService Thread Pool -- 10) JBAS018210: Register web context: /jsf22-jee6 > 15:49:32,755 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 10) Initializing Mojarra 2.2.0 (-SNAPSHOT 20121204-0807 https://svn.java.net/svn/mojarra~svn/trunk at 11125) for context '/jsf22-jee6' > 15:49:34,438 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 10) Unable to process annotations for url, vfs:/content/jsf22-jee6.war/WEB-INF/lib/richfaces-components-ui-4.3.0-20121203.111732-232.jar/META-INF/faces-config.xml. Reason: java.util.zip.ZipException: zip file is empty > 15:49:34,439 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 10) : java.util.zip.ZipException: zip file is empty > 2.0-SNAPSHOT] > :2.2.0-SNAPSHOT] > OT] > ] > OT] > 15:49:34,445 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 10) Unable to process annotations for url, vfs:/content/jsf22-jee6.war/WEB-INF/lib/richfaces-core-impl-4.3.0-20121203.205629-130.jar/META-INF/faces-config.xml. Reason: java.util.zip.ZipException: zip file is empty > 15:49:34,445 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 10) : java.util.zip.ZipException: zip file is empty > at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_09-icedtea] > at java.util.zip.ZipFile.(ZipFile.java:214) [rt.jar:1.7.0_09-icedtea] > at java.util.zip.ZipFile.(ZipFile.java:144) [rt.jar:1.7.0_09-icedtea] > at java.util.jar.JarFile.(JarFile.java:152) [rt.jar:1.7.0_09-icedtea] > at sun.net.www.protocol.jar.URLJarFile.(URLJarFile.java:88) [rt.jar:1.7.0_09-icedtea] > at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:221) [rt.jar:1.7.0_09-icedtea] > at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:216) [rt.jar:1.7.0_09-icedtea] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_09-icedtea] > at sun.net.www.protocol.jar.URLJarFile.retrieve(URLJarFile.java:215) [rt.jar:1.7.0_09-icedtea] > at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:71) [rt.jar:1.7.0_09-icedtea] > at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:73) [rt.jar:1.7.0_09-icedtea] > at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:122) [rt.jar:1.7.0_09-icedtea] > at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:89) [rt.jar:1.7.0_09-icedtea] > at com.sun.faces.config.JavaClassScanningAnnotationScanner.processClasspath(JavaClassScanningAnnotationScanner.java:166) [jsf-impl-2.2.0-SNAPSHOT.jar:2.2.0-SNAPSHOT] > at com.sun.faces.config.JavaClassScanningAnnotationScanner.getAnnotatedClasses(JavaClassScanningAnnotationScanner.java:125) [jsf-impl-2.2.0-SNAPSHOT.jar:2.2.0-SNAPSHOT] > at com.sun.faces.config.DelegatingAnnotationProvider.getAnnotatedClasses(DelegatingAnnotationProvider.java:85) [jsf-impl-2.2.0-SNAPSHOT.jar:2.2.0-SNAPSHOT] > at com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:879) [jsf-impl-2.2.0-SNAPSHOT.jar:2.2.0-SNAPSHOT] > at com.sun.faces.config.ConfigManager$AnnotationScanTask.call(ConfigManager.java:831) [jsf-impl-2.2.0-SNAPSHOT.jar:2.2.0-SNAPSHOT] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_09-icedtea] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_09-icedtea] > at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:370) [jsf-impl-2.2.0-SNAPSHOT.jar:2.2.0-SNAPSHOT] > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:224) [jsf-impl-2.2.0-SNAPSHOT.jar:2.2.0-SNAPSHOT] > at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5] > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.0.Alpha5.jar:7.2.0.Alpha5] > at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_09-icedtea] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_09-icedtea] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_09-icedtea] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09-icedtea] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09-icedtea] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > 15:49:34,613 INFO [org.hibernate.validator.util.Version] (ServerService Thread Pool -- 10) Hibernate Validator 4.2.0.Final > 15:49:35,235 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 10) Monitoring jndi:/default-host/jsf22-jee6/WEB-INF/faces-config.xml for modifications > 15:49:35,418 INFO [org.richfaces.log.Cache] (ServerService Thread Pool -- 10) Selected fallback cache factory > 15:49:35,420 INFO [org.richfaces.log.Cache] (ServerService Thread Pool -- 10) Creating LRUMap cache instance using parameters: {org.jboss.jbossfaces.JSF_CONFIG_NAME=mojarra-2.2.0-SNAPSHOT, org.richfaces.resourceMapping.enabled=true, javax.faces.PROJECT_STAGE=Development, javax.faces.SKIP_COMMENTS=true, org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL=false} > 15:49:35,429 INFO [org.richfaces.log.Cache] (ServerService Thread Pool -- 10) Creating LRUMap cache instance of 512 items capacity > 15:49:35,446 INFO [org.richfaces.log.Application] (ServerService Thread Pool -- 10) RichFaces Core Implementation by JBoss by Red Hat, version 4.3.0-SNAPSHOT > 15:49:35,512 WARNING [org.richfaces.log.Application] (ServerService Thread Pool -- 10) JMS API was found on the classpath; if you want to enable RichFaces Push JMS integration, set context-param 'org.richfaces.push.jms.enabled' in web.xml > 15:49:35,650 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "jsf22-jee6.war" > {quote} > * richfaces-components-ui-4.3.0-20121203.111732-232.jar is definitely *not empty* > * application works fine with Tomcat 7.0.32 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 11:41:15 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 10 Jun 2014 11:41:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974954#comment-12974954 ] Michal Petrov commented on RF-13658: ------------------------------------ [~jhuska], push does work in showcase. Metamer is requesting a resource from a wrong URL so I'm guessing there are some settings that need to be changed. > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 21:05:15 2014 From: issues at jboss.org (Gurinder Randhawa (JIRA)) Date: Tue, 10 Jun 2014 21:05:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12554) in a doesn't work in composite components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975074#comment-12975074 ] Gurinder Randhawa commented on RF-12554: ---------------------------------------- I'm re-opening this issue, I had mentioned the problem was using a javascript plugin called tooltipster not which works fine but its not a desired solution as our content is HTML pulled from a CMS and cached in our JSF based web application. > in a doesn't work in composite components > ------------------------------------------------------------------------ > > Key: RF-12554 > URL: https://issues.jboss.org/browse/RF-12554 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final > Reporter: Bojan Antonovic > Assignee: Ji?? ?tefek > Priority: Minor > Attachments: RF-12554.zip > > > To make it work, you have to write once the dummy > {code} > > {code} > then you can use as often as you wish: > {code} > > ... > > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Tue Jun 10 21:05:16 2014 From: issues at jboss.org (Gurinder Randhawa (JIRA)) Date: Tue, 10 Jun 2014 21:05:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12554) in a doesn't work in composite components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975075#comment-12975075 ] Gurinder Randhawa commented on RF-12554: ---------------------------------------- http://iamceege.github.io/tooltipster/ > in a doesn't work in composite components > ------------------------------------------------------------------------ > > Key: RF-12554 > URL: https://issues.jboss.org/browse/RF-12554 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final > Reporter: Bojan Antonovic > Assignee: Ji?? ?tefek > Priority: Minor > Attachments: RF-12554.zip > > > To make it work, you have to write once the dummy > {code} > > {code} > then you can use as often as you wish: > {code} > > ... > > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 02:17:16 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 11 Jun 2014 02:17:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12554) in a doesn't work in composite components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975084#comment-12975084 ] Brian Leathem commented on RF-12554: ------------------------------------ [~randhawag] sounds like a problem with your plugin. From the perspective of the client-side, all a ar4/ui:repeat does is create a repeating set of div elements. If your jQuery plugin is having a problem selecting and operating on those elements it's likely a problem with the plugin. Check for jQuery conflicts, or jQuery plugin conflicts. Use your browser's javascript debugger to help pinpoint the problem. > in a doesn't work in composite components > ------------------------------------------------------------------------ > > Key: RF-12554 > URL: https://issues.jboss.org/browse/RF-12554 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final > Reporter: Bojan Antonovic > Assignee: Ji?? ?tefek > Priority: Minor > Attachments: RF-12554.zip > > > To make it work, you have to write once the dummy > {code} > > {code} > then you can use as often as you wish: > {code} > > ... > > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 04:23:17 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 11 Jun 2014 04:23:17 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13658: ------------------------------- Description: I've checked showcase and photoalbum and discovered several issues: -* trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} ** this completely breaks photoalbum- * data retrieval from server doesn't seem to work (there are no errors on either server or client) ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) ** extendedDataTable with enabled ajax loading does not load any data ** progressbar does not work ** togglePanel does not switch ** dynamic tabPanels do not switch ** tooltips that make a server call do not work (the tooltip is empty) was: I've checked showcase and photoalbum and discovered several issues: * trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} ** this completely breaks photoalbum * data retrieval from server doesn't seem to work (there are no errors on either server or client) ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) ** extendedDataTable with enabled ajax loading does not load any data ** progressbar does not work ** togglePanel does not switch ** dynamic tabPanels do not switch ** tooltips that make a server call do not work (the tooltip is empty) > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > -* trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} > ** this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 04:23:18 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 11 Jun 2014 04:23:18 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13658: ------------------------------- Description: I've checked showcase and photoalbum and discovered several issues: * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- ** -this completely breaks photoalbum- * data retrieval from server doesn't seem to work (there are no errors on either server or client) ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) ** extendedDataTable with enabled ajax loading does not load any data ** progressbar does not work ** togglePanel does not switch ** dynamic tabPanels do not switch ** tooltips that make a server call do not work (the tooltip is empty) was: I've checked showcase and photoalbum and discovered several issues: -* trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}} ** this completely breaks photoalbum- * data retrieval from server doesn't seem to work (there are no errors on either server or client) ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) ** extendedDataTable with enabled ajax loading does not load any data ** progressbar does not work ** togglePanel does not switch ** dynamic tabPanels do not switch ** tooltips that make a server call do not work (the tooltip is empty) > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 04:25:16 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 11 Jun 2014 04:25:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13658: ------------------------------- Description: I've checked showcase and photoalbum and discovered several issues: These issues appear on EAP but not on WildFly. * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- ** -this completely breaks photoalbum- * data retrieval from server doesn't seem to work (there are no errors on either server or client) ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) ** extendedDataTable with enabled ajax loading does not load any data ** progressbar does not work ** togglePanel does not switch ** dynamic tabPanels do not switch ** tooltips that make a server call do not work (the tooltip is empty) was: I've checked showcase and photoalbum and discovered several issues: * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- ** -this completely breaks photoalbum- * data retrieval from server doesn't seem to work (there are no errors on either server or client) ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) ** extendedDataTable with enabled ajax loading does not load any data ** progressbar does not work ** togglePanel does not switch ** dynamic tabPanels do not switch ** tooltips that make a server call do not work (the tooltip is empty) > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 04:45:19 2014 From: issues at jboss.org (=?UTF-8?Q?Martin_H=C3=B6ller_=28JIRA=29?=) Date: Wed, 11 Jun 2014 04:45:19 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13662) doesn't provide selection In-Reply-To: References: Message-ID: Martin H?ller created RF-13662: ---------------------------------- Summary: doesn't provide selection Key: RF-13662 URL: https://issues.jboss.org/browse/RF-13662 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 4.3.7 Reporter: Martin H?ller In RichFaces 3.x the component had a selection-Attribute. In RichFaces 4.x this is currently not supported and thus there is not way to obtain the selected entries. Please bring back this useful feature! -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 05:33:15 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 11 Jun 2014 05:33:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13662) doesn't provide selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975148#comment-12975148 ] Michal Petrov commented on RF-13662: ------------------------------------ The selection is available on client-side, via {{\#\{rich:component('oList')\}.getList().getSelectedItems()}} > doesn't provide selection > --------------------------------------------- > > Key: RF-13662 > URL: https://issues.jboss.org/browse/RF-13662 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.7 > Reporter: Martin H?ller > Labels: orderingList > > In RichFaces 3.x the component had a selection-Attribute. In RichFaces 4.x this is currently not supported and thus there is not way to obtain the selected entries. Please bring back this useful feature! -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Jun 11 07:39:45 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 11 Jun 2014 07:39:45 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13651) Integration tests failing in chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975215#comment-12975215 ] Matej Novotny commented on RF-13651: ------------------------------------ I did some more testing regarding @Warp tests in a4j. It seems that all @Warp tests using BeforePhase hooks fail with Chrome . But they all work correctly with Firefox and PhantomJS I suppose the tests were taken from RF 5, so I tried it there but it fails as well - I think we took already failing tests and added them here. Furthermore I downloaded Arq. warp extension repo and ran the integration tests there (there is a JSF lifecycle [test|https://github.com/arquillian/arquillian-extension-warp/blob/master/extension/jsf-ftest/src/test/java/org/jboss/arquillian/warp/jsf/ftest/lifecycle/TestJsfLifecycle.java]). The test passed correctly with identical setup (wildfly and chrome). Hence I suppose there is no bug in arquillian itself. I also tried changing dependecies version but with no luck, it still fails on chrome. Any idea what might cause this? > Integration tests failing in chrome > ----------------------------------- > > Key: RF-13651 > URL: https://issues.jboss.org/browse/RF-13651 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > The framework tests pass in phantomjs but some fail in chrome. > Resolution of this issue involves running and stabilizing the tests in all supported browsers. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 08:19:39 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 11 Jun 2014 08:19:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: Matej Novotny created RF-13663: ---------------------------------- Summary: Warp on Chrome Key: RF-13663 URL: https://issues.jboss.org/browse/RF-13663 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5.0.Alpha2 Environment: Chrome Wildfly 8.0 Reporter: Matej Novotny Assignee: Luk?? Fry? This issue originates from RF-13651. RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. This is the exception: {code} testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) at com.sun.proxy.$Proxy27.responsePost(Unknown Source) at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) at java.lang.Thread.run(Thread.java:724) {code} What I tried: * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) ** This test works, so I suppose warp works correctly * I tried to change dependencies to other version to see whether it would work ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 08:25:40 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 11 Jun 2014 08:25:40 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13651) Integration tests failing in chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975215#comment-12975215 ] Matej Novotny edited comment on RF-13651 at 6/11/14 8:25 AM: ------------------------------------------------------------- I did some more testing regarding @Warp tests in a4j. It seems that all @Warp tests using BeforePhase hooks fail with Chrome . But they all work correctly with Firefox and PhantomJS I suppose the tests were taken from RF 5, so I tried it there but it fails as well - I think we took already failing tests and added them here. Furthermore I downloaded Arq. warp extension repo and ran the integration tests there (there is a JSF lifecycle [test|https://github.com/arquillian/arquillian-extension-warp/blob/master/extension/jsf-ftest/src/test/java/org/jboss/arquillian/warp/jsf/ftest/lifecycle/TestJsfLifecycle.java]). The test passed correctly with identical setup (wildfly and chrome). Hence I suppose there is no bug in arquillian itself. I also tried changing dependecies version but with no luck, it still fails on chrome. EDIT: I created RF-13663 to track Chrome+Warp issue separately as it might be problem with Warp rather than RF itself was (Author: manovotn): I did some more testing regarding @Warp tests in a4j. It seems that all @Warp tests using BeforePhase hooks fail with Chrome . But they all work correctly with Firefox and PhantomJS I suppose the tests were taken from RF 5, so I tried it there but it fails as well - I think we took already failing tests and added them here. Furthermore I downloaded Arq. warp extension repo and ran the integration tests there (there is a JSF lifecycle [test|https://github.com/arquillian/arquillian-extension-warp/blob/master/extension/jsf-ftest/src/test/java/org/jboss/arquillian/warp/jsf/ftest/lifecycle/TestJsfLifecycle.java]). The test passed correctly with identical setup (wildfly and chrome). Hence I suppose there is no bug in arquillian itself. I also tried changing dependecies version but with no luck, it still fails on chrome. Any idea what might cause this? > Integration tests failing in chrome > ----------------------------------- > > Key: RF-13651 > URL: https://issues.jboss.org/browse/RF-13651 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > The framework tests pass in phantomjs but some fail in chrome. > Resolution of this issue involves running and stabilizing the tests in all supported browsers. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 09:29:38 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 11 Jun 2014 09:29:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975278#comment-12975278 ] Michal Petrov commented on RF-13656: ------------------------------------ On the first request the first table is being processed as the panels switch, on subsequent requests only the table that is being switched to is processed. The tables share a CSS style object (which they shouldn't) and that causes the collapse. > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Pavol Pitonak > Labels: regression > Fix For: 4.3.8 > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 10:58:43 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 11 Jun 2014 10:58:43 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974721#comment-12974721 ] Juraj H?ska edited comment on RF-13658 at 6/11/14 10:57 AM: ------------------------------------------------------------ I am adding some of my findings, omitting issues which [~michpetrov] already found. *tabPanel*: can not be switched * reproducible e.g. in Metamer welcome page * it is occuring when switchType == ajax * it is switched to the next panel when refreshed *togglePanel*: the same apply as above *collapsiblePanel*: same *accordion*: can not be switched neither when ajax mode nor in client mode -*editor*: is not rendered- * -getting 404 on these resources:- ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/skin.js ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor_gecko.css ** -caused by CKE Editor upgrade to 4.1.1 with [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit- * it is metamer issue, already fixed, thanks [~jstefek] *autocomplete*: does not work in ajax mode -*push*: does not work, does not recieve any pushes- * -following error is thrown- * it was a metamer issues as [~michpetrov] pointed out, now fixed was (Author: jhuska): I am adding some of my findings, omitting issues which [~michpetrov] already found. *tabPanel*: can not be switched * reproducible e.g. in Metamer welcome page * it is occuring when switchType == ajax * it is switched to the next panel when refreshed *togglePanel*: the same apply as above *collapsiblePanel*: same *accordion*: can not be switched neither when ajax mode nor in client mode -*editor*: is not rendered- * -getting 404 on these resources:- ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/skin.js ** org.richfaces.resources/javax.faces.resource/org.richfaces.ckeditor/skins/richfaces/editor_gecko.css ** -caused by CKE Editor upgrade to 4.1.1 with [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit- * it is metamer issue, already fixed, thanks [~jstefek] *autocomplete*: does not work in ajax mode *push*: does not work, does not recieve any pushes * following error is thrown * {code}23:58:59,784 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/metamer].[Faces Servlet]] (http--0.0.0.0-8080-6) Servlet.service() for servlet Faces Servlet threw exception: java.lang.IllegalArgumentException: pushTopic request parameter must be present at org.richfaces.resource.PushResource.encode(PushResource.java:85) [richfaces-a4j-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:184) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:2.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] {code} > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 11:00:44 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 11 Jun 2014 11:00:44 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975340#comment-12975340 ] Juraj H?ska commented on RF-13658: ---------------------------------- Yes [~michpetrov], you are right, Metamer is missing push depchain. Thanks. Fixed now. > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 12:44:38 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 11 Jun 2014 12:44:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13656. -------------------------------- Assignee: Michal Petrov (was: Pavol Pitonak) Resolution: Done I've removed what seemed like unnecessary parsing of all CSS rules on the page (the result was only used to change width and display). Now we're simply changing the style properties with jQuery. > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Michal Petrov > Labels: regression > Fix For: 4.3.8 > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 14:52:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 11 Jun 2014 14:52:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13664) EDT firstChild call will return a text element when the source code is formatted to have one element per line In-Reply-To: References: Message-ID: Brian Leathem created RF-13664: ---------------------------------- Summary: EDT firstChild call will return a text element when the source code is formatted to have one element per line Key: RF-13664 URL: https://issues.jboss.org/browse/RF-13664 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-tables Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.5.0.Alpha3 Formatting the generated html and viewing the result in chrome leads to an error in the EDT call: {{this.frozenHeaderPartElement.firstChild.rows}}. This is because when the element is followed by a newline, a text element is returned from the firstChild call. Some solutions to this are discussed in the stackoverflow question: http://stackoverflow.com/questions/2299807/element-firstchild-is-returning-textnode-instead-of-an-object-in-ff I recommend we use jQuery here to resolve the first child in a cross-browser way. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 16:32:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 11 Jun 2014 16:32:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975468#comment-12975468 ] Brian Leathem commented on RF-13658: ------------------------------------ {quote} These issues appear on EAP but not on WildFly. {quote} There is a Mojarra bug that breaks the new EPVC ({{[JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]}}). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also [patched|https://github.com/jbossas/jboss-eap/pull/1026], but I believe this patched mojarra didn't land in EAP until 6.3. [~fjuma] can you confirm the EAP version that contains the Mojarra version with this patch? [~michpetrov] and [~jhuska] please make sure you are testing with the patched EAP. We _should_ have some code in place to _fail fast_ if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in JAVASERVERFACES-3151. Please file a {{RF}} issue if this _fail fast_ feature is not present. > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 16:46:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 11 Jun 2014 16:46:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13664) EDT firstChild call will return a text element when the source code is formatted to have one element per line In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975472#comment-12975472 ] Brian Leathem commented on RF-13664: ------------------------------------ An alternative solution: {{element.firstChild}} is the same as {{element.childNodes\[0]}} and will return the problematic _text_ node. However {{element.children\[0]}} returns the expected child element. Since {{element.firstChild}} is used in multiple places in the _extendedDataTable.js_ source, replacing it's use by the {{element.children\[0]}} call is the least invasive solution. > EDT firstChild call will return a text element when the source code is formatted to have one element per line > ------------------------------------------------------------------------------------------------------------- > > Key: RF-13664 > URL: https://issues.jboss.org/browse/RF-13664 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Formatting the generated html and viewing the result in chrome leads to an error in the EDT call: > {{this.frozenHeaderPartElement.firstChild.rows}}. This is because when the element is followed by a newline, a text element is returned from the firstChild call. > Some solutions to this are discussed in the stackoverflow question: > http://stackoverflow.com/questions/2299807/element-firstchild-is-returning-textnode-instead-of-an-object-in-ff > I recommend we use jQuery here to resolve the first child in a cross-browser way. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 16:50:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 11 Jun 2014 16:50:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13664) EDT firstChild call will return a text element when the source code is formatted to have one element per line In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13664. -------------------------------- Resolution: Done Replaced firstChild calls with children[0] > EDT firstChild call will return a text element when the source code is formatted to have one element per line > ------------------------------------------------------------------------------------------------------------- > > Key: RF-13664 > URL: https://issues.jboss.org/browse/RF-13664 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Formatting the generated html and viewing the result in chrome leads to an error in the EDT call: > {{this.frozenHeaderPartElement.firstChild.rows}}. This is because when the element is followed by a newline, a text element is returned from the firstChild call. > Some solutions to this are discussed in the stackoverflow question: > http://stackoverflow.com/questions/2299807/element-firstchild-is-returning-textnode-instead-of-an-object-in-ff > I recommend we use jQuery here to resolve the first child in a cross-browser way. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 17:02:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 11 Jun 2014 17:02:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13661) De-couple the RichFaces.BaseComponent implementation from its JSF backend In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975475#comment-12975475 ] Brian Leathem commented on RF-13661: ------------------------------------ I created a branch [RF-13661-independent-js|https://github.com/richfaces/richfaces/tree/RF-13661-independent-js] where I added a examples/standalone-js example that can be use to create standalone html pages for various RF components. The jsf pages are stored in the {{jsf}} webapp folder, and the corresponding standalone html page is stored in the {{html}} folder. Note: the standalone html page is created by deploying the webapp, and viewing a component page in a browser. The html source of the component page is saved as an html file. Path changes are made to the html file to use the js resources of the components directly from the source tree. ---- Merging of this branch is pending discussion at the upcoming f2f meeting. > De-couple the RichFaces.BaseComponent implementation from its JSF backend > ------------------------------------------------------------------------- > > Key: RF-13661 > URL: https://issues.jboss.org/browse/RF-13661 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5-Tracking > > > Investigate whether we can de-couple a {{RichFaces.BaseComponent}} based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 17:08:40 2014 From: issues at jboss.org (Farah Juma (JIRA)) Date: Wed, 11 Jun 2014 17:08:40 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975477#comment-12975477 ] Farah Juma commented on RF-13658: --------------------------------- Both EAP 6.2.3 and EAP 6.3 contain Mojarra versions with the patch for this issue (both contain patched versions of Mojarra 2.1.28). > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 20:25:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 11 Jun 2014 20:25:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975495#comment-12975495 ] Brian Leathem commented on RF-13663: ------------------------------------ [~manovotn] can you reproduce this in a test without RichFaces? Should this instead be a ARQ (component:warp) issue? > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Luk?? Fry? > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 20:31:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 11 Jun 2014 20:31:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13662) doesn't provide selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975496#comment-12975496 ] Brian Leathem commented on RF-13662: ------------------------------------ from the [RichFaces 3 showcase|http://showcase-rf3.richfaces.org/richfaces/orderingList.jsf?tab=info&cid=18167]: * selection: _Collection which stores a set of selected items_ This is a facelet attribute and so could be bound to a managed bean property. However, this is not the intended use case for the ordering list. Instead the pickList component is intended to be used for use cases where you want to both _order_ and _select_ items. [~matinh] is there a reason why you do not want to use the pickList component for your use case? > doesn't provide selection > --------------------------------------------- > > Key: RF-13662 > URL: https://issues.jboss.org/browse/RF-13662 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.7 > Reporter: Martin H?ller > Labels: waiting_on_user > > In RichFaces 3.x the component had a selection-Attribute. In RichFaces 4.x this is currently not supported and thus there is not way to obtain the selected entries. Please bring back this useful feature! -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 11 20:31:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 11 Jun 2014 20:31:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13662) doesn't provide selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13662: ------------------------------- Labels: waiting_on_user (was: orderingList) > doesn't provide selection > --------------------------------------------- > > Key: RF-13662 > URL: https://issues.jboss.org/browse/RF-13662 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.7 > Reporter: Martin H?ller > Labels: waiting_on_user > > In RichFaces 3.x the component had a selection-Attribute. In RichFaces 4.x this is currently not supported and thus there is not way to obtain the selected entries. Please bring back this useful feature! -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 02:35:38 2014 From: issues at jboss.org (=?UTF-8?Q?Martin_H=C3=B6ller_=28JIRA=29?=) Date: Thu, 12 Jun 2014 02:35:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13662) doesn't provide selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975523#comment-12975523 ] Martin H?ller commented on RF-13662: ------------------------------------ It's exactly the same use case as [somebody asked/described|http://stackoverflow.com/questions/10515530/] on StackOverflow. Basically I have a list the I want to order. And I want to provide a possibility to delete items from the list via an external button. Thus, I need to know what is selected. I thought of using picklist instead, but that doesn't fit well into my UI (picklist is much bigger than orderingList) and adding/deleting items from the list is not the main purpose for my use-case. So I really hope to get this feature from RF3 back into RF4. Thx. > doesn't provide selection > --------------------------------------------- > > Key: RF-13662 > URL: https://issues.jboss.org/browse/RF-13662 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.7 > Reporter: Martin H?ller > Labels: waiting_on_user > > In RichFaces 3.x the component had a selection-Attribute. In RichFaces 4.x this is currently not supported and thus there is not way to obtain the selected entries. Please bring back this useful feature! -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 02:37:39 2014 From: issues at jboss.org (=?UTF-8?Q?Martin_H=C3=B6ller_=28JIRA=29?=) Date: Thu, 12 Jun 2014 02:37:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13662) doesn't provide selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975526#comment-12975526 ] Martin H?ller commented on RF-13662: ------------------------------------ @Michal Petrov: Thanks for the client-side API hint. Unfortunately there is no "onselectionchanged" event. If that would be available, I could use to submit the selection. > doesn't provide selection > --------------------------------------------- > > Key: RF-13662 > URL: https://issues.jboss.org/browse/RF-13662 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.7 > Reporter: Martin H?ller > Labels: waiting_on_user > > In RichFaces 3.x the component had a selection-Attribute. In RichFaces 4.x this is currently not supported and thus there is not way to obtain the selected entries. Please bring back this useful feature! -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 03:56:38 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 12 Jun 2014 03:56:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13665) RichFaces 4.5 should fail fast when used with un-pached Mojarra In-Reply-To: References: Message-ID: Juraj H?ska created RF-13665: -------------------------------- Summary: RichFaces 4.5 should fail fast when used with un-pached Mojarra Key: RF-13665 URL: https://issues.jboss.org/browse/RF-13665 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Affects Versions: 4.5.0.Alpha3 Reporter: Juraj H?ska [~bleathem] wrote [in|https://issues.jboss.org/browse/RF-13658?focusedCommentId=12975468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12975468]: ??There is a Mojarra bug that breaks the new EPVC ([JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also patched?? ??We should have some code in place to fail fast if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in [JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]?? And we are not failing fast. I would say that when application is about to use unpached Mojarra, the fail fast would be a runtime exception during deployment ? -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 03:56:38 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 12 Jun 2014 03:56:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13665) RichFaces 4.5 should fail fast when used with un-pached Mojarra In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13665: ----------------------------- Description: [~bleathem] wrote [in this comment|https://issues.jboss.org/browse/RF-13658?focusedCommentId=12975468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12975468] for RF-13658: ??There is a Mojarra bug that breaks the new EPVC ([JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also patched?? ??We should have some code in place to fail fast if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in [JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]?? And we are not failing fast. I would say that when application is about to use unpached Mojarra, the fail fast would be a runtime exception during deployment ? was: [~bleathem] wrote [in|https://issues.jboss.org/browse/RF-13658?focusedCommentId=12975468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12975468]: ??There is a Mojarra bug that breaks the new EPVC ([JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also patched?? ??We should have some code in place to fail fast if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in [JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]?? And we are not failing fast. I would say that when application is about to use unpached Mojarra, the fail fast would be a runtime exception during deployment ? > RichFaces 4.5 should fail fast when used with un-pached Mojarra > --------------------------------------------------------------- > > Key: RF-13665 > URL: https://issues.jboss.org/browse/RF-13665 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > > [~bleathem] wrote [in this comment|https://issues.jboss.org/browse/RF-13658?focusedCommentId=12975468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12975468] for RF-13658: > ??There is a Mojarra bug that breaks the new EPVC ([JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also patched?? > ??We should have some code in place to fail fast if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in [JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]?? > And we are not failing fast. I would say that when application is about to use unpached Mojarra, the fail fast would be a runtime exception during deployment ? > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 03:58:39 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 12 Jun 2014 03:58:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975541#comment-12975541 ] Juraj H?ska commented on RF-13658: ---------------------------------- Created RF-13665 feature request for failing fast when RF application is about to be used with un-pached Mojarra. > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 04:10:39 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 12 Jun 2014 04:10:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13658. -------------------------------- Resolution: Done Works in EAP 6.2.3, marking as resolved. > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 04:32:38 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Jun 2014 04:32:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975547#comment-12975547 ] Matej Novotny commented on RF-13663: ------------------------------------ [~bleathem] I made it RF issue because I cannot reproduce it otherwise. I am trying it with [this Arq. Warp test|https://github.com/arquillian/arquillian-extension-warp/blob/master/extension/jsf-ftest/src/test/java/org/jboss/arquillian/warp/jsf/ftest/lifecycle/TestJsfLifecycle.java] which I changed to call some bean methods in certain phases and do assertions etc., but it works correctly. I ran it with -Darquillian.debug and I can see that the phase does get executed. Hence I think the problem won't be in Arquillian. > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Luk?? Fry? > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 04:34:38 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 12 Jun 2014 04:34:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13656: ------------------------------- Fix Version/s: 4.5.0.Alpha3 5.0.0.Alpha4 > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Michal Petrov > Labels: regression > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 04:58:42 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 12 Jun 2014 04:58:42 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975563#comment-12975563 ] Juraj H?ska commented on RF-13658: ---------------------------------- I wanted to verify it with EAP 6.3.0.Beta1, however, it contains {{jsf-impl-2.1.27.redhat-9.jar}}, and therefore it does not work with it. EAP 6.3.0.ER4 contained {{jsf-impl-2.1.28.redhat-3.jar}}, [~fjuma] is this please expected ? Works with WildFly and its {{jsf-impl-2.2.5-jbossorg-3.jar}}. > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 05:56:38 2014 From: issues at jboss.org (=?UTF-8?Q?Martin_H=C3=B6ller_=28JIRA=29?=) Date: Thu, 12 Jun 2014 05:56:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-5635) extendedDataTable: css classes defined in "columnClasses" attribute don't influence on columns width. In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975585#comment-12975585 ] Martin H?ller commented on RF-5635: ----------------------------------- This issue also applies for RF 4.3.7. > extendedDataTable: css classes defined in "columnClasses" attribute don't influence on columns width. > ----------------------------------------------------------------------------------------------------- > > Key: RF-5635 > URL: https://issues.jboss.org/browse/RF-5635 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.3.0 > Environment: IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.CR3) > Reporter: Mikhail Vitenkov > Priority: Minor > Fix For: 3.Future > > Attachments: ExtendedDataTable.jsp > > > #1. Define css classes for component columns: > .leftColumn { > width: 50px; > height: 100%; > background-color: red; > } > .midColumn { > width: 250px; > height: 100%; > background-color: green; > } > .rightColumn { > width: 400px; > height: 100%; > background-color: yellow; > } > #2. Add extendedDataTable on the page, following way, as attachment. > #3. Set columnClasses="leftColumn, midColumn, rightColumn"(width attribute for component and it's columns shouldn't be defined) > #4. Navigate to page and verify extendedDataTable columns width. > Actual behavior: > Css classes(leftColumn, midColumn...) present in page code(see in firebug), but real width of columns remains the same as before columnClasses attribute using. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 06:22:38 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Jun 2014 06:22:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975594#comment-12975594 ] Matej Novotny commented on RF-13663: ------------------------------------ I tried to narrow the point of failure in the above mentioned test (ITExecuteRichAjax). Note: all the tests in that package fail for the same reason (they are similar) The test consist of 2 method calling: * {code}setupExecute("@this");{code} > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Luk?? Fry? > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 06:24:38 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Jun 2014 06:24:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny updated RF-13663: ------------------------------- Comment: was deleted (was: I tried to narrow the point of failure in the above mentioned test (ITExecuteRichAjax). Note: all the tests in that package fail for the same reason (they are similar) The test consist of 2 method calling: * {code}setupExecute("@this");{code}) > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Luk?? Fry? > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 06:32:38 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Jun 2014 06:32:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975596#comment-12975596 ] Matej Novotny commented on RF-13663: ------------------------------------ Some more information - I tried to narrow the point of failure in these tests: All the problematic methods consist of 2 warp initiate/inspect calls: * First is initiated by: browser.get(...) ** this works even with Chrome, the phase is called and executed ** it proves that some warp tests pass * Second is initiated by: button.click() ** here it fails ** I checked the number of requests sent by this click (in case there would be more we might need observer) but there is only one ** I tried to simplify this method to see if some other parts do not cause the problems (eg. @ArqResource FacesContext), but even if you leave the method blank you still get the 'Phase not executed' exception > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Luk?? Fry? > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 08:16:47 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Jun 2014 08:16:47 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny reassigned RF-13663: ---------------------------------- Assignee: Matej Novotny (was: Luk?? Fry?) > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Matej Novotny > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 08:18:38 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Jun 2014 08:18:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975622#comment-12975622 ] Matej Novotny commented on RF-13663: ------------------------------------ Ok after a lot of struggling I managed to resolve this. The problem is that in Chrome when there is a component (eg. button) which uses different background image (on hover for isntance) Chrome loads this image only when uses attempts to use this component. That means when the tests attempted to click the button, there were indeed 2 requests, first of which (and the inspected one) was image loading. The workaround is to first use activity which will hover over the button to force image loading and then start Warp activity. I will push this commit any time soon and resolve this issue. > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Matej Novotny > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 08:30:39 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Jun 2014 08:30:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny resolved RF-13663. -------------------------------- Resolution: Done > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Matej Novotny > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 09:29:51 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 09:29:51 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975650#comment-12975650 ] Brian Leathem commented on RF-13663: ------------------------------------ Nice catch [~manovotn]! Might be an interesting blog post in there is this isn't something widely known about in the testing community. > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Matej Novotny > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 09:45:39 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Jun 2014 09:45:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13651) Integration tests failing in chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975659#comment-12975659 ] Matej Novotny commented on RF-13651: ------------------------------------ With RF-13663 fixed I was able to make to apply identical fix to core warp test which was failing (ITJavaScriptServiceAjax). So what's left from smoke tests are rich components which are: * building successfully in chrome * failing in firefox on following tests: ** ITFileUpload *** This test is marked as @Smoke BUT also as @FailingOnPhantomJS so atm we do not tests FileUpload in 4.5 *** There was an issue with PhantomDriver causing this, I will see if update helps and will try to make it work for all browsers > Integration tests failing in chrome > ----------------------------------- > > Key: RF-13651 > URL: https://issues.jboss.org/browse/RF-13651 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > The framework tests pass in phantomjs but some fail in chrome. > Resolution of this issue involves running and stabilizing the tests in all supported browsers. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 09:45:41 2014 From: issues at jboss.org (Farah Juma (JIRA)) Date: Thu, 12 Jun 2014 09:45:41 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975662#comment-12975662 ] Farah Juma commented on RF-13658: --------------------------------- It should work with EAP 6.3.0.Beta1 since {{jsf-impl-2.1.27.redhat-9.jar}} also contains the fix for {{[JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]}} (see {{[BZ-1070349|https://bugzilla.redhat.com/show_bug.cgi?id=1070349]}}). We upgraded to {{jsf-impl-2.1.28.redhat-3.jar}} just after the EAP 6.3.0.Beta1 release to fix two other issues (see {{[BZ-1087564|https://bugzilla.redhat.com/show_bug.cgi?id=1087564]}} and {{[BZ-1093769|https://bugzilla.redhat.com/show_bug.cgi?id=1087564]}}). > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 09:45:41 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 12 Jun 2014 09:45:41 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13651) Integration tests failing in chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975659#comment-12975659 ] Matej Novotny edited comment on RF-13651 at 6/12/14 9:44 AM: ------------------------------------------------------------- With RF-13663 fixed I was able to apply identical fix to core warp test which was failing (ITJavaScriptServiceAjax). So what's left from smoke tests are rich components which are: * building successfully in chrome * failing in firefox on following tests: ** ITFileUpload *** This test is marked as @Smoke BUT also as @FailingOnPhantomJS so atm we do not tests FileUpload in 4.5 *** There was an issue with PhantomDriver causing this, I will see if update helps and will try to make it work for all browsers was (Author: manovotn): With RF-13663 fixed I was able to make to apply identical fix to core warp test which was failing (ITJavaScriptServiceAjax). So what's left from smoke tests are rich components which are: * building successfully in chrome * failing in firefox on following tests: ** ITFileUpload *** This test is marked as @Smoke BUT also as @FailingOnPhantomJS so atm we do not tests FileUpload in 4.5 *** There was an issue with PhantomDriver causing this, I will see if update helps and will try to make it work for all browsers > Integration tests failing in chrome > ----------------------------------- > > Key: RF-13651 > URL: https://issues.jboss.org/browse/RF-13651 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > The framework tests pass in phantomjs but some fail in chrome. > Resolution of this issue involves running and stabilizing the tests in all supported browsers. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 10:09:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 10:09:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13665) RichFaces 4.5 should fail fast when used with un-pached Mojarra In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13665: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > RichFaces 4.5 should fail fast when used with un-pached Mojarra > --------------------------------------------------------------- > > Key: RF-13665 > URL: https://issues.jboss.org/browse/RF-13665 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > > [~bleathem] wrote [in this comment|https://issues.jboss.org/browse/RF-13658?focusedCommentId=12975468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12975468] for RF-13658: > ??There is a Mojarra bug that breaks the new EPVC ([JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also patched?? > ??We should have some code in place to fail fast if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in [JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]?? > And we are not failing fast. I would say that when application is about to use unpached Mojarra, the fail fast would be a runtime exception during deployment ? > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 10:19:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 10:19:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13232) Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13232: ------------------------------- Fix Version/s: 4.5-Tracking > Enable flexible changing of the deployed archive name for general deployments, e.g. CoreDeployment > -------------------------------------------------------------------------------------------------- > > Key: RF-13232 > URL: https://issues.jboss.org/browse/RF-13232 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Minor > Fix For: 4.5-Tracking > > > This should be added to support *[multiple deployments|https://docs.jboss.org/author/display/ARQ/Multiple+Deployments]* feature of Arquillian. > It matters to the {{CoreDeployment}} and to the similar. > Currently, {{Deployment}} class decide what name the deployed archive would have. It uses the passed {{class}} object to determine this. In the particular test, one needs to pass some class, which would be part of the name. The good practice is to pass the name of the test class. > Here comes the problem with multiple deployments, when each deployed archive has to have different name. > Proposed solution: > Add overloaded constructor method, which would take a name for the deployed archive. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 10:21:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 10:21:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13604) rich:editor is flickering on mouse hover In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13604: ------------------------------- Assignee: (was: Matej Novotny) > rich:editor is flickering on mouse hover > ---------------------------------------- > > Key: RF-13604 > URL: https://issues.jboss.org/browse/RF-13604 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Environment: Windows 7, Glassfish 4, Java 1.7, JSF2.2, Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659) > Reporter: Serge Rogatch > Labels: editor, glassfish, jsf22 > Attachments: TutRichf1.zip > > > Initially the rich:editor component didn't render, throwing some errors in JavaScript ( https://community.jboss.org/message/867978 ), however afterwards I was not able to reproduce that in a newly created project. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 10:23:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 10:23:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13457) Failing Warp test throws exception while trying to take a screenshot In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975685#comment-12975685 ] Brian Leathem commented on RF-13457: ------------------------------------ [~jhuska] would you please re-formulate this PR for RichFaces 4.5? > Failing Warp test throws exception while trying to take a screenshot > -------------------------------------------------------------------- > > Key: RF-13457 > URL: https://issues.jboss.org/browse/RF-13457 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Fix For: 5.0.0.Alpha4 > > > Here are the test results: > {code} > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 7.69 sec <<< FAILURE! - in org.richfaces.ui.toggle.panelMenu.ITPanelMenu > test_disabled_menu_item(org.richfaces.ui.toggle.panelMenu.ITPanelMenu) Time elapsed: 7.532 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.execution.WarpSynchronizationException: The Warp failed to observe requests or match them with response. > There were no requests matched by observer [null] > If Warp enriched a wrong request, use observe(...) method to select appropriate request which should be enriched instead. > Otherwise check the server-side log and enable Arquillian debugging mode on both, test and server VM by passing -Darquillian.debug=true. > at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155) > at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionInitializer.provideWarpContext(WarpExecutionInitializer.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpRequestSpecifier.execute(DefaultWarpRequestSpecifier.java:98) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpRequestSpecifier.inspect(DefaultWarpRequestSpecifier.java:76) > at org.richfaces.ui.toggle.panelMenu.ITPanelMenu.test_disabled_menu_item(ITPanelMenu.java:91) > test_disabled_menu_item(org.richfaces.ui.toggle.panelMenu.ITPanelMenu) Time elapsed: 7.534 sec <<< ERROR! > java.lang.RuntimeException: unexpected invocation exception during invocation of org.openqa.selenium.TakesScreenshot#getScreenshotAs(), on target 'ReusableRemoteWebDriver: chrome on LINUX (799229cc-608d-49d7-91d3-74d9f487fce3)': org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver.getScreenshotAs(org.openqa.selenium.OutputType) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:135) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver$$EnhancerByGraphene$$94b0812e.getScreenshotAs() > at org.richfaces.arquillian.browser.FailureScreenshot.takeScreenshotOnFailure(FailureScreenshot.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:141) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:114) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:86) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NoSuchMethodException: org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver.getScreenshotAs(org.openqa.selenium.OutputType) > at java.lang.Class.getDeclaredMethod(Class.java:1956) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:124) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver$$EnhancerByGraphene$$94b0812e.getScreenshotAs() > at org.richfaces.arquillian.browser.FailureScreenshot.takeScreenshotOnFailure(FailureScreenshot.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:141) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:114) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:86) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > 13847 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Shutting down proxy > 13853 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Closing all channels... > 13878 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Stopping timer > 13887 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Done shutting down proxy > Results : > Tests in error: > ITPanelMenu.test_disabled_menu_item:91 ? WarpSynchronization The Warp failed t... > ITPanelMenu.test_disabled_menu_item ? Runtime unexpected invocation exception ... > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 10:25:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 10:25:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13457) Failing Warp test throws exception while trying to take a screenshot In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13457: ------------------------------- Assignee: Juraj H?ska > Failing Warp test throws exception while trying to take a screenshot > -------------------------------------------------------------------- > > Key: RF-13457 > URL: https://issues.jboss.org/browse/RF-13457 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha4 > > > Here are the test results: > {code} > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 7.69 sec <<< FAILURE! - in org.richfaces.ui.toggle.panelMenu.ITPanelMenu > test_disabled_menu_item(org.richfaces.ui.toggle.panelMenu.ITPanelMenu) Time elapsed: 7.532 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.execution.WarpSynchronizationException: The Warp failed to observe requests or match them with response. > There were no requests matched by observer [null] > If Warp enriched a wrong request, use observe(...) method to select appropriate request which should be enriched instead. > Otherwise check the server-side log and enable Arquillian debugging mode on both, test and server VM by passing -Darquillian.debug=true. > at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155) > at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionInitializer.provideWarpContext(WarpExecutionInitializer.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpRequestSpecifier.execute(DefaultWarpRequestSpecifier.java:98) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpRequestSpecifier.inspect(DefaultWarpRequestSpecifier.java:76) > at org.richfaces.ui.toggle.panelMenu.ITPanelMenu.test_disabled_menu_item(ITPanelMenu.java:91) > test_disabled_menu_item(org.richfaces.ui.toggle.panelMenu.ITPanelMenu) Time elapsed: 7.534 sec <<< ERROR! > java.lang.RuntimeException: unexpected invocation exception during invocation of org.openqa.selenium.TakesScreenshot#getScreenshotAs(), on target 'ReusableRemoteWebDriver: chrome on LINUX (799229cc-608d-49d7-91d3-74d9f487fce3)': org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver.getScreenshotAs(org.openqa.selenium.OutputType) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:135) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver$$EnhancerByGraphene$$94b0812e.getScreenshotAs() > at org.richfaces.arquillian.browser.FailureScreenshot.takeScreenshotOnFailure(FailureScreenshot.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:141) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:114) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:86) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NoSuchMethodException: org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver.getScreenshotAs(org.openqa.selenium.OutputType) > at java.lang.Class.getDeclaredMethod(Class.java:1956) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:124) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver$$EnhancerByGraphene$$94b0812e.getScreenshotAs() > at org.richfaces.arquillian.browser.FailureScreenshot.takeScreenshotOnFailure(FailureScreenshot.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:141) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:114) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:86) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > 13847 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Shutting down proxy > 13853 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Closing all channels... > 13878 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Stopping timer > 13887 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Done shutting down proxy > Results : > Tests in error: > ITPanelMenu.test_disabled_menu_item:91 ? WarpSynchronization The Warp failed t... > ITPanelMenu.test_disabled_menu_item ? Runtime unexpected invocation exception ... > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 10:40:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 10:40:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13656: ------------------------------- Labels: needs-qe regression (was: regression) > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Michal Petrov > Labels: needs-qe, regression > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 11:24:40 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 12 Jun 2014 11:24:40 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975715#comment-12975715 ] Juraj H?ska commented on RF-13658: ---------------------------------- I have tried it again with publicly available EAP 6.3.0.Beta1, and I do not why but it does not work. However for RichFaces is IMHO important that it works with latest EAP 6.3.0.ER7. > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 12:09:39 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 12 Jun 2014 12:09:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13635) rich:menuGroup: Menu node image is missing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975739#comment-12975739 ] Michal Petrov commented on RF-13635: ------------------------------------ 4.3.5.Final jar on maven contains the correct image, however when I build it locally (even 4.3.4.Final) the bad one is generated. Although if I change the image type to PNG it will generate correctly, likewise if I fill the background with some color (rather than leaving it transparent). > rich:menuGroup: Menu node image is missing > ------------------------------------------ > > Key: RF-13635 > URL: https://issues.jboss.org/browse/RF-13635 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.6 > Reporter: Marta Juzepczuk > Fix For: 4.3.8 > > > After upgrading to 4.3.6.Final, the small black arrow near rich:menuGroup label disappeared. Background image of the menu item is set to ../org.richfaces.images/menuNodeImage.gif, the same as in previous versions, but the image is empty. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 15:15:41 2014 From: issues at jboss.org (Dmitry Volkov (JIRA)) Date: Thu, 12 Jun 2014 15:15:41 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13666) rich:editor: Paste does not work in Internet Explorer 11 In-Reply-To: References: Message-ID: Dmitry Volkov created RF-13666: ---------------------------------- Summary: rich:editor: Paste does not work in Internet Explorer 11 Key: RF-13666 URL: https://issues.jboss.org/browse/RF-13666 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.3.5 Environment: Windows 7, Internet Explorer 11.0.9600.17126 Reporter: Dmitry Volkov Can not paste text in rich:editor with ctrl+v and context menu in IE 11 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 19:00:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 19:00:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13665) RichFaces 4.5 should fail fast when used with un-pached Mojarra In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13665. -------------------------------- Assignee: Brian Leathem Resolution: Done Implemented a JsfVersionInspector class to inspect the jsf-impl version and prevent application initialisation for incompatible jsf impls > RichFaces 4.5 should fail fast when used with un-pached Mojarra > --------------------------------------------------------------- > > Key: RF-13665 > URL: https://issues.jboss.org/browse/RF-13665 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > [~bleathem] wrote [in this comment|https://issues.jboss.org/browse/RF-13658?focusedCommentId=12975468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12975468] for RF-13658: > ??There is a Mojarra bug that breaks the new EPVC ([JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also patched?? > ??We should have some code in place to fail fast if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in [JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]?? > And we are not failing fast. I would say that when application is about to use unpached Mojarra, the fail fast would be a runtime exception during deployment ? > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 20:08:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 20:08:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13667) Upgrade mojarra dependency In-Reply-To: References: Message-ID: Brian Leathem created RF-13667: ---------------------------------- Summary: Upgrade mojarra dependency Key: RF-13667 URL: https://issues.jboss.org/browse/RF-13667 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: third-party Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.5.0.Alpha3 Upgrade the RichFaces mojarra dependency to the version that ships with the latest stable WildFly release. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 20:10:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 20:10:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13667) Upgrade mojarra dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975856#comment-12975856 ] Brian Leathem commented on RF-13667: ------------------------------------ For WildFly 0.1.0.Final, that version is 2.2.6-jbossorg-4 https://github.com/wildfly/wildfly/blob/8.1.0.Final/pom.xml#L88 > Upgrade mojarra dependency > -------------------------- > > Key: RF-13667 > URL: https://issues.jboss.org/browse/RF-13667 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > Upgrade the RichFaces mojarra dependency to the version that ships with the latest stable WildFly release. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 12 20:14:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 12 Jun 2014 20:14:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13667) Upgrade mojarra dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13667. -------------------------------- Resolution: Done > Upgrade mojarra dependency > -------------------------- > > Key: RF-13667 > URL: https://issues.jboss.org/browse/RF-13667 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > Upgrade the RichFaces mojarra dependency to the version that ships with the latest stable WildFly release. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 02:50:38 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 02:50:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13457) Failing Warp test throws exception while trying to take a screenshot In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975893#comment-12975893 ] Juraj H?ska commented on RF-13457: ---------------------------------- I believe this pull request is no more required as fix for ARQ-1634 landed upstream. I checked it with 4.5.x integration tests, and it works. > Failing Warp test throws exception while trying to take a screenshot > -------------------------------------------------------------------- > > Key: RF-13457 > URL: https://issues.jboss.org/browse/RF-13457 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha4 > > > Here are the test results: > {code} > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 7.69 sec <<< FAILURE! - in org.richfaces.ui.toggle.panelMenu.ITPanelMenu > test_disabled_menu_item(org.richfaces.ui.toggle.panelMenu.ITPanelMenu) Time elapsed: 7.532 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.execution.WarpSynchronizationException: The Warp failed to observe requests or match them with response. > There were no requests matched by observer [null] > If Warp enriched a wrong request, use observe(...) method to select appropriate request which should be enriched instead. > Otherwise check the server-side log and enable Arquillian debugging mode on both, test and server VM by passing -Darquillian.debug=true. > at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155) > at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionInitializer.provideWarpContext(WarpExecutionInitializer.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpRequestSpecifier.execute(DefaultWarpRequestSpecifier.java:98) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpRequestSpecifier.inspect(DefaultWarpRequestSpecifier.java:76) > at org.richfaces.ui.toggle.panelMenu.ITPanelMenu.test_disabled_menu_item(ITPanelMenu.java:91) > test_disabled_menu_item(org.richfaces.ui.toggle.panelMenu.ITPanelMenu) Time elapsed: 7.534 sec <<< ERROR! > java.lang.RuntimeException: unexpected invocation exception during invocation of org.openqa.selenium.TakesScreenshot#getScreenshotAs(), on target 'ReusableRemoteWebDriver: chrome on LINUX (799229cc-608d-49d7-91d3-74d9f487fce3)': org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver.getScreenshotAs(org.openqa.selenium.OutputType) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:135) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver$$EnhancerByGraphene$$94b0812e.getScreenshotAs() > at org.richfaces.arquillian.browser.FailureScreenshot.takeScreenshotOnFailure(FailureScreenshot.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:141) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:114) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:86) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NoSuchMethodException: org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver.getScreenshotAs(org.openqa.selenium.OutputType) > at java.lang.Class.getDeclaredMethod(Class.java:1956) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:124) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver$$EnhancerByGraphene$$94b0812e.getScreenshotAs() > at org.richfaces.arquillian.browser.FailureScreenshot.takeScreenshotOnFailure(FailureScreenshot.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:141) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:114) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:86) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > 13847 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Shutting down proxy > 13853 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Closing all channels... > 13878 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Stopping timer > 13887 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Done shutting down proxy > Results : > Tests in error: > ITPanelMenu.test_disabled_menu_item:91 ? WarpSynchronization The Warp failed t... > ITPanelMenu.test_disabled_menu_item ? Runtime unexpected invocation exception ... > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:31:39 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jun 2014 06:31:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975948#comment-12975948 ] Luk?? Fry? commented on RF-13658: --------------------------------- [~jhuska] could you please create new issue to track the incompatibility with 6.3.0.Beta1? Does it work with 6.3.0.ER7? > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:35:38 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jun 2014 06:35:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975950#comment-12975950 ] Luk?? Fry? commented on RF-13663: --------------------------------- I believe better fix would be use of {{Warp....filter(...)}} method to intercept just JSF page request, but good catch anyway! > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Matej Novotny > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 06:45:43 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Fri, 13 Jun 2014 06:45:43 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975715#comment-12975715 ] Juraj H?ska edited comment on RF-13658 at 6/13/14 6:45 AM: ----------------------------------------------------------- I have tried it again with publicly available EAP 6.3.0.Beta1, and I do not why but it does not work. However for RichFaces is IMHO important that it works with latest EAP 6.3.0.ER7, and *it works*. was (Author: jhuska): I have tried it again with publicly available EAP 6.3.0.Beta1, and I do not why but it does not work. However for RichFaces is IMHO important that it works with latest EAP 6.3.0.ER7. > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 07:32:38 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Fri, 13 Jun 2014 07:32:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975966#comment-12975966 ] Luk?? Fry? commented on RF-13663: --------------------------------- [~manovotn] any chance you could try whether {{Warp..filter(...)}} API solves the issue? > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Matej Novotny > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 08:36:38 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 13 Jun 2014 08:36:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13666) rich:editor: Paste does not work in Internet Explorer 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975994#comment-12975994 ] Michal Petrov commented on RF-13666: ------------------------------------ CKEditor has had several compatibility issues with IE 11 (https://dev.ckeditor.com/ticket/10612), they were fixed in 4.3. > rich:editor: Paste does not work in Internet Explorer 11 > -------------------------------------------------------- > > Key: RF-13666 > URL: https://issues.jboss.org/browse/RF-13666 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Windows 7, Internet Explorer 11.0.9600.17126 > Reporter: Dmitry Volkov > > Can not paste text in rich:editor with ctrl+v and context menu in IE 11 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 10:52:40 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 10:52:40 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13457) Failing Warp test throws exception while trying to take a screenshot In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976071#comment-12976071 ] Brian Leathem commented on RF-13457: ------------------------------------ Thanks [~jhuska]. Go ahead and close the PR and resolve this issue as out-of-date. > Failing Warp test throws exception while trying to take a screenshot > -------------------------------------------------------------------- > > Key: RF-13457 > URL: https://issues.jboss.org/browse/RF-13457 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha4 > > > Here are the test results: > {code} > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 7.69 sec <<< FAILURE! - in org.richfaces.ui.toggle.panelMenu.ITPanelMenu > test_disabled_menu_item(org.richfaces.ui.toggle.panelMenu.ITPanelMenu) Time elapsed: 7.532 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.execution.WarpSynchronizationException: The Warp failed to observe requests or match them with response. > There were no requests matched by observer [null] > If Warp enriched a wrong request, use observe(...) method to select appropriate request which should be enriched instead. > Otherwise check the server-side log and enable Arquillian debugging mode on both, test and server VM by passing -Darquillian.debug=true. > at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155) > at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionInitializer.provideWarpContext(WarpExecutionInitializer.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpRequestSpecifier.execute(DefaultWarpRequestSpecifier.java:98) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpRequestSpecifier.inspect(DefaultWarpRequestSpecifier.java:76) > at org.richfaces.ui.toggle.panelMenu.ITPanelMenu.test_disabled_menu_item(ITPanelMenu.java:91) > test_disabled_menu_item(org.richfaces.ui.toggle.panelMenu.ITPanelMenu) Time elapsed: 7.534 sec <<< ERROR! > java.lang.RuntimeException: unexpected invocation exception during invocation of org.openqa.selenium.TakesScreenshot#getScreenshotAs(), on target 'ReusableRemoteWebDriver: chrome on LINUX (799229cc-608d-49d7-91d3-74d9f487fce3)': org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver.getScreenshotAs(org.openqa.selenium.OutputType) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:135) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver$$EnhancerByGraphene$$94b0812e.getScreenshotAs() > at org.richfaces.arquillian.browser.FailureScreenshot.takeScreenshotOnFailure(FailureScreenshot.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:141) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:114) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:86) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NoSuchMethodException: org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver.getScreenshotAs(org.openqa.selenium.OutputType) > at java.lang.Class.getDeclaredMethod(Class.java:1956) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:124) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver$$EnhancerByGraphene$$94b0812e.getScreenshotAs() > at org.richfaces.arquillian.browser.FailureScreenshot.takeScreenshotOnFailure(FailureScreenshot.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:141) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:114) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:86) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > 13847 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Shutting down proxy > 13853 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Closing all channels... > 13878 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Stopping timer > 13887 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Done shutting down proxy > Results : > Tests in error: > ITPanelMenu.test_disabled_menu_item:91 ? WarpSynchronization The Warp failed t... > ITPanelMenu.test_disabled_menu_item ? Runtime unexpected invocation exception ... > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 10:54:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 10:54:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13666) rich:editor: Paste does not work in Internet Explorer 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976073#comment-12976073 ] Brian Leathem commented on RF-13666: ------------------------------------ [~michpetrov] do you mean they were fixed in 4.5? > rich:editor: Paste does not work in Internet Explorer 11 > -------------------------------------------------------- > > Key: RF-13666 > URL: https://issues.jboss.org/browse/RF-13666 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Windows 7, Internet Explorer 11.0.9600.17126 > Reporter: Dmitry Volkov > > Can not paste text in rich:editor with ctrl+v and context menu in IE 11 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 11:08:38 2014 From: issues at jboss.org (Guillaume Renard (JIRA)) Date: Fri, 13 Jun 2014 11:08:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13668) Richfaces cannot work along wiht Prototype In-Reply-To: References: Message-ID: Guillaume Renard created RF-13668: ------------------------------------- Summary: Richfaces cannot work along wiht Prototype Key: RF-13668 URL: https://issues.jboss.org/browse/RF-13668 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.7 Reporter: Guillaume Renard I am trying to use Richfaces 3.4.7 within a web app which also serves Prototype.js. AJAX actions just don't work at all. a4j:log reveals the following: {code} warn [16:41:11.596]: richfaces.queue: ajax submit error: Object function $(element) { if (arguments.length > 1) { for (var i = 0, elements = [], length = arguments.length; i < length; i++) elements.push($(arguments[i])); return elements; } if (Object.isString(element)) element =...... } has no method 'extend' {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 11:10:38 2014 From: issues at jboss.org (Guillaume Renard (JIRA)) Date: Fri, 13 Jun 2014 11:10:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13668) Richfaces cannot work along wiht Prototype In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Renard updated RF-13668: ---------------------------------- Attachment: RF-13668.patch Attached patch to solve the issue. > Richfaces cannot work along wiht Prototype > ------------------------------------------ > > Key: RF-13668 > URL: https://issues.jboss.org/browse/RF-13668 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: Guillaume Renard > Attachments: RF-13668.patch > > > I am trying to use Richfaces 3.4.7 within a web app which also serves Prototype.js. > AJAX actions just don't work at all. a4j:log reveals the following: > {code} > warn [16:41:11.596]: richfaces.queue: ajax submit error: Object function $(element) { if (arguments.length > 1) { for (var i = 0, elements = [], length = arguments.length; i < length; i++) elements.push($(arguments[i])); return elements; } if (Object.isString(element)) element =...... } has no method 'extend' > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 12:13:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 12:13:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13668) Richfaces cannot work along wiht Prototype In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976137#comment-12976137 ] Brian Leathem commented on RF-13668: ------------------------------------ The patch isn't quite right. The auto-executing function surrounding the {{richfaces.queue}} definition captures the {{jQuery}} global in the closure using the {{$}} character as the the local reference. As in: {code} (function($, richfaces, jsf) { ... }(jQuery, RichFaces, jsf)); {code} So it's not preferred to use the {{jQuery}} global itself within the closure. However it is true that this has not been done systematically throughout the RichFaces codebase. This has been addressed in the upcoming 4.5 release with issue RF-12936. Backporting this fix to the 4.3 branch was ruled out in RF-13533. > Richfaces cannot work along wiht Prototype > ------------------------------------------ > > Key: RF-13668 > URL: https://issues.jboss.org/browse/RF-13668 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: Guillaume Renard > Attachments: RF-13668.patch > > > I am trying to use Richfaces 3.4.7 within a web app which also serves Prototype.js. > AJAX actions just don't work at all. a4j:log reveals the following: > {code} > warn [16:41:11.596]: richfaces.queue: ajax submit error: Object function $(element) { if (arguments.length > 1) { for (var i = 0, elements = [], length = arguments.length; i < length; i++) elements.push($(arguments[i])); return elements; } if (Object.isString(element)) element =...... } has no method 'extend' > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 12:15:41 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 12:15:41 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13668) Richfaces cannot work along wiht Prototype In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13668. -------------------------------- Resolution: Duplicate Issue > Richfaces cannot work along wiht Prototype > ------------------------------------------ > > Key: RF-13668 > URL: https://issues.jboss.org/browse/RF-13668 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Reporter: Guillaume Renard > Attachments: RF-13668.patch > > > I am trying to use Richfaces 3.4.7 within a web app which also serves Prototype.js. > AJAX actions just don't work at all. a4j:log reveals the following: > {code} > warn [16:41:11.596]: richfaces.queue: ajax submit error: Object function $(element) { if (arguments.length > 1) { for (var i = 0, elements = [], length = arguments.length; i < length; i++) elements.push($(arguments[i])); return elements; } if (Object.isString(element)) element =...... } has no method 'extend' > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 12:23:38 2014 From: issues at jboss.org (Lutz Ulrich (JIRA)) Date: Fri, 13 Jun 2014 12:23:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13071) Undeploying Showcase from Tomcat6/7 can cause memory leak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976139#comment-12976139 ] Lutz Ulrich commented on RF-13071: ---------------------------------- I guess it's a warning, too. Probably Tomcat logs such warnings whenever a wep application starts threads but won't stop them. For example {{org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.start()}} starts 'push-session-manager-thread'-s. These threads run a {{while(true)}} loop, and I guess they never terminate. You should terminate these threads when the web application is stopped. > Undeploying Showcase from Tomcat6/7 can cause memory leak > --------------------------------------------------------- > > Key: RF-13071 > URL: https://issues.jboss.org/browse/RF-13071 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Final, 5.0.0.Alpha1 > Reporter: Juraj H?ska > Priority: Minor > Labels: memory_leak, performance > Fix For: 5-Tracking > > > When undeploying showcase from Tomcat 6/7 then following log is present on the server console: > {code} > SEVERE: The web application [/richfaces-showcase-tomcat6] appears to have started a thread named [Thread-0 (group:HornetQ-client-factory-threads-1831192424-1080990297)] but has failed to stop it. This is very likely to create a memory leak. > {code} > There is lot of such logs, just the _Thread-counter_ is changing. > * 11 such logs just with showcase deploying and then right after undeploying > * bit more when after deploying playing a little bit with {{r:push}} > IMHO it is not just warning. I am experiencing {{Out of Memory}} issues when testing on Tomcat. I need to use quite big {{Perm Gen}} and {{Heap size}} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 12:50:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 12:50:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13665) RichFaces 4.5 should fail fast when used with un-pached Mojarra In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13665: ------------------------------- Labels: needs-qe (was: ) > RichFaces 4.5 should fail fast when used with un-pached Mojarra > --------------------------------------------------------------- > > Key: RF-13665 > URL: https://issues.jboss.org/browse/RF-13665 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > > [~bleathem] wrote [in this comment|https://issues.jboss.org/browse/RF-13658?focusedCommentId=12975468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12975468] for RF-13658: > ??There is a Mojarra bug that breaks the new EPVC ([JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also patched?? > ??We should have some code in place to fail fast if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in [JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]?? > And we are not failing fast. I would say that when application is about to use unpached Mojarra, the fail fast would be a runtime exception during deployment ? > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 12:50:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 12:50:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13665) RichFaces 4.5 should fail fast when used with un-pached Mojarra In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976147#comment-12976147 ] Brian Leathem commented on RF-13665: ------------------------------------ QE I tested this in EAP 6.2.0 (where it correctly fails) and Wildfly 8.1.0.Final (where it correctly succeeds). Can you please test this in other containers with configurations that are expected to both pass and fail? > RichFaces 4.5 should fail fast when used with un-pached Mojarra > --------------------------------------------------------------- > > Key: RF-13665 > URL: https://issues.jboss.org/browse/RF-13665 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > > [~bleathem] wrote [in this comment|https://issues.jboss.org/browse/RF-13658?focusedCommentId=12975468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12975468] for RF-13658: > ??There is a Mojarra bug that breaks the new EPVC ([JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also patched?? > ??We should have some code in place to fail fast if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in [JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]?? > And we are not failing fast. I would say that when application is about to use unpached Mojarra, the fail fast would be a runtime exception during deployment ? > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 14:44:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 14:44:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13669) Backport the CKEditor 4 upgrade to RichFaces 4.3 In-Reply-To: References: Message-ID: Brian Leathem created RF-13669: ---------------------------------- Summary: Backport the CKEditor 4 upgrade to RichFaces 4.3 Key: RF-13669 URL: https://issues.jboss.org/browse/RF-13669 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-input Reporter: Brian Leathem Fix For: 4.3.8 The only concern with this backport is the removal of the richfaces-skinning capability of the editor. Skinning the editor in RichFaces 4.5 requires using the CKEditor JS API. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 14:46:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 14:46:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13669) Backport the CKEditor 4 upgrade to RichFaces 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13669: ------------------------------- Description: the reason for this backport is to address the reported IE 11 problems with the CKeditor in RichFaces <= 4.3.7 The only concern with this backport is the removal of the richfaces-skinning capability of the editor. Skinning the editor in RichFaces 4.5 requires using the CKEditor JS API. was:The only concern with this backport is the removal of the richfaces-skinning capability of the editor. Skinning the editor in RichFaces 4.5 requires using the CKEditor JS API. > Backport the CKEditor 4 upgrade to RichFaces 4.3 > ------------------------------------------------ > > Key: RF-13669 > URL: https://issues.jboss.org/browse/RF-13669 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Fix For: 4.3.8 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > the reason for this backport is to address the reported IE 11 problems with the CKeditor in RichFaces <= 4.3.7 > The only concern with this backport is the removal of the richfaces-skinning capability of the editor. Skinning the editor in RichFaces 4.5 requires using the CKEditor JS API. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 14:46:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 14:46:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13669) Backport the CKEditor 4 upgrade to RichFaces 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13669: ---------------------------------- Assignee: Pavol Pitonak QE verification of the IE 11 incompatibility of the 4.3.7 ckeditor would be appreciated to help prioritize this issue. > Backport the CKEditor 4 upgrade to RichFaces 4.3 > ------------------------------------------------ > > Key: RF-13669 > URL: https://issues.jboss.org/browse/RF-13669 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Pavol Pitonak > Fix For: 4.3.8 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > the reason for this backport is to address the reported IE 11 problems with the CKeditor in RichFaces <= 4.3.7 > The only concern with this backport is the removal of the richfaces-skinning capability of the editor. Skinning the editor in RichFaces 4.5 requires using the CKEditor JS API. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 15:34:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 15:34:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13615: ------------------------------- Description: After changing the width of a column, subsequent scrolling of the table triggers 2 ajax requests instead of the expected single request. Due to this behavior I get some performance issues, as I have to execute some own javascript after each request. Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered. Best regards wlh was: 1. Go to the extendedDataTable showcase 2. Turn on ajax loading. 3. Open the debugger of your browser and watch the network communication 4. Scroll down in the table untli new data has to be fetched. => one POST request is sent. This is fine. 5. Change the width of a column in the table. => one POST request is sent. This is fine. 6. Scroll again in the table untli new data has to be fetched. -> 2 POST requests are sent. WHY? >From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table. Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request. Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered. Best regards wlh Steps to Reproduce: 1. Go to the extendedDataTable showcase 2. Turn on ajax loading. 3. Open the debugger of your browser and watch the network communication 4. Scroll down in the table untli new data has to be fetched. => one POST request is sent. This is fine. 5. Change the width of a column in the table. => one POST request is sent. This is fine. 6. Scroll again in the table untli new data has to be fetched. -> 2 POST requests are sent. WHY? >From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table. > ExtendedDataTable: double ajax request on scrolling > --------------------------------------------------- > > Key: RF-13615 > URL: https://issues.jboss.org/browse/RF-13615 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.6 > Environment: Problem can be tested in richfaces showcase. > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extendedDataTable&skin=blueSky > Reporter: Holger Walter > Assignee: Michal Petrov > Fix For: 4.3.8 > > Attachments: edt.png > > > After changing the width of a column, subsequent scrolling of the table triggers 2 ajax requests instead of the expected single request. > Due to this behavior I get some performance issues, as I have to execute some own javascript after each request. > Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered. > Best regards > wlh -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 17:03:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 17:03:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976230#comment-12976230 ] Brian Leathem commented on RF-13615: ------------------------------------ This fix needs to be ported to the 4.5 branch. If the port has already been done, please update the _fixVersion_. > ExtendedDataTable: double ajax request on scrolling > --------------------------------------------------- > > Key: RF-13615 > URL: https://issues.jboss.org/browse/RF-13615 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.6 > Environment: Problem can be tested in richfaces showcase. > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extendedDataTable&skin=blueSky > Reporter: Holger Walter > Assignee: Michal Petrov > Fix For: 4.3.8 > > Attachments: edt.png > > > After changing the width of a column, subsequent scrolling of the table triggers 2 ajax requests instead of the expected single request. > Due to this behavior I get some performance issues, as I have to execute some own javascript after each request. > Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered. > Best regards > wlh -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 17:05:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 17:05:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13647) File Download throws exception when used with a commandButton of type="button" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976231#comment-12976231 ] Brian Leathem commented on RF-13647: ------------------------------------ If still relevant despite the fileUpload changes in 4.5, then this fix should be ported to the 4.5 branch. If the port has already been done, please update the _fixVersion_. > File Download throws exception when used with a commandButton of type="button" > ------------------------------------------------------------------------------ > > Key: RF-13647 > URL: https://issues.jboss.org/browse/RF-13647 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6 > Environment: Richfaces 4.3.6 Final. > Mojarra - 2.1.28 > Weblogic 12.1.2 > Windows 7 > Reporter: santhosh siravuri > Assignee: Michal Petrov > Priority: Critical > Labels: regression > Fix For: 4.3.8 > > Attachments: RF-13647.zip > > > File download action throws below exception. > {code} > ]] Root cause of ServletException. > java.lang.NullPointerException > at org.richfaces.renderkit.AjaxCommandRendererBase.isSubmitted(AjaxCommandRendererBase.java:83) > at org.richfaces.renderkit.AjaxCommandRendererBase.doDecode(AjaxCommandRendererBase.java:59) > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:789) > at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1183) > Truncated. see log file for complete stacktrace > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 17:11:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 17:11:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13636) Add List Impls to the resource serialization whitelist In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13636: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Add List Impls to the resource serialization whitelist > ------------------------------------------------------ > > Key: RF-13636 > URL: https://issues.jboss.org/browse/RF-13636 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.6 > Reporter: Cody Lerum > Assignee: Cody Lerum > Fix For: 4.3.8, 4.5.0.Alpha3 > > > Not having these prevents passing data list data to charting components via the mediaoutput component -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 17:13:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 17:13:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13670) Update the "new" labels in the showcase In-Reply-To: References: Message-ID: Brian Leathem created RF-13670: ---------------------------------- Summary: Update the "new" labels in the showcase Key: RF-13670 URL: https://issues.jboss.org/browse/RF-13670 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.5.0.Alpha3 The only component that should be labelled as "new" in the 4.5.x showcase is the chart component. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 17:17:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 17:17:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13670) Update the "new" labels in the showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13670. -------------------------------- Resolution: Done > Update the "new" labels in the showcase > --------------------------------------- > > Key: RF-13670 > URL: https://issues.jboss.org/browse/RF-13670 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The only component that should be labelled as "new" in the 4.5.x showcase is the chart component. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 17:19:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 17:19:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) autocomplete cant select by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13640: ------------------------------- Affects Version/s: 4.5.0.Alpha3 > autocomplete cant select by mouse > --------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.8 > > > the suggestion list of autocomplete can not be selected by mouse, always the first one selected. > there is not this bug before 4.3.6. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 17:27:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 17:27:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) autocomplete cant select by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976235#comment-12976235 ] Brian Leathem commented on RF-13640: ------------------------------------ Also reproduced in 4.5.0-SNAPSHOT. > autocomplete cant select by mouse > --------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.8 > > > the suggestion list of autocomplete can not be selected by mouse, always the first one selected. > there is not this bug before 4.3.6. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 17:37:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 17:37:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13640: ------------------------------- Summary: Autocomplete with custom layout: cant select item by mouse (was: autocomplete cant select by mouse) > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.8 > > > the suggestion list of autocomplete can not be selected by mouse, always the first one selected. > there is not this bug before 4.3.6. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 17:37:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 17:37:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13640: ------------------------------- Description: When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. This bug was not observable before 4.3.6.Final. was: the suggestion list of autocomplete can not be selected by mouse, always the first one selected. there is not this bug before 4.3.6. > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.8 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Fri Jun 13 17:41:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 13 Jun 2014 17:41:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976242#comment-12976242 ] Brian Leathem commented on RF-13640: ------------------------------------ This was likely introduced with the fix to RF-13531. > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.8 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 03:18:24 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 16 Jun 2014 03:18:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13666) rich:editor: Paste does not work in Internet Explorer 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976402#comment-12976402 ] Michal Petrov commented on RF-13666: ------------------------------------ [~bleathem], ah, I should've specified. It was fixed in CKEditor 4.3 (and thus in RichFaces 4.5). > rich:editor: Paste does not work in Internet Explorer 11 > -------------------------------------------------------- > > Key: RF-13666 > URL: https://issues.jboss.org/browse/RF-13666 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Windows 7, Internet Explorer 11.0.9600.17126 > Reporter: Dmitry Volkov > > Can not paste text in rich:editor with ctrl+v and context menu in IE 11 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 03:38:25 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 16 Jun 2014 03:38:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13647) File Download throws exception when used with a commandButton of type="button" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13647: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > File Download throws exception when used with a commandButton of type="button" > ------------------------------------------------------------------------------ > > Key: RF-13647 > URL: https://issues.jboss.org/browse/RF-13647 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6 > Environment: Richfaces 4.3.6 Final. > Mojarra - 2.1.28 > Weblogic 12.1.2 > Windows 7 > Reporter: santhosh siravuri > Assignee: Michal Petrov > Priority: Critical > Labels: regression > Fix For: 4.3.8, 4.5.0.Alpha3 > > Attachments: RF-13647.zip > > > File download action throws below exception. > {code} > ]] Root cause of ServletException. > java.lang.NullPointerException > at org.richfaces.renderkit.AjaxCommandRendererBase.isSubmitted(AjaxCommandRendererBase.java:83) > at org.richfaces.renderkit.AjaxCommandRendererBase.doDecode(AjaxCommandRendererBase.java:59) > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:789) > at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1183) > Truncated. see log file for complete stacktrace > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 03:46:25 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 16 Jun 2014 03:46:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13615: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > ExtendedDataTable: double ajax request on scrolling > --------------------------------------------------- > > Key: RF-13615 > URL: https://issues.jboss.org/browse/RF-13615 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.6 > Environment: Problem can be tested in richfaces showcase. > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extendedDataTable&skin=blueSky > Reporter: Holger Walter > Assignee: Michal Petrov > Fix For: 4.3.8, 4.5.0.Alpha3 > > Attachments: edt.png > > > After changing the width of a column, subsequent scrolling of the table triggers 2 ajax requests instead of the expected single request. > Due to this behavior I get some performance issues, as I have to execute some own javascript after each request. > Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered. > Best regards > wlh -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 03:46:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 16 Jun 2014 03:46:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13457) Failing Warp test throws exception while trying to take a screenshot In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska resolved RF-13457. ------------------------------ Resolution: Out of Date Resolving as out of date. > Failing Warp test throws exception while trying to take a screenshot > -------------------------------------------------------------------- > > Key: RF-13457 > URL: https://issues.jboss.org/browse/RF-13457 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Juraj H?ska > Fix For: 5.0.0.Alpha4 > > > Here are the test results: > {code} > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 7.69 sec <<< FAILURE! - in org.richfaces.ui.toggle.panelMenu.ITPanelMenu > test_disabled_menu_item(org.richfaces.ui.toggle.panelMenu.ITPanelMenu) Time elapsed: 7.532 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.execution.WarpSynchronizationException: The Warp failed to observe requests or match them with response. > There were no requests matched by observer [null] > If Warp enriched a wrong request, use observe(...) method to select appropriate request which should be enriched instead. > Otherwise check the server-side log and enable Arquillian debugging mode on both, test and server VM by passing -Darquillian.debug=true. > at org.jboss.arquillian.warp.impl.client.execution.SynchronizationPoint.awaitResponses(SynchronizationPoint.java:155) > at org.jboss.arquillian.warp.impl.client.execution.DefaultExecutionSynchronizer.waitForResponse(DefaultExecutionSynchronizer.java:60) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.awaitResponse(WarpExecutionObserver.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.awaitServerExecution(DefaultWarpExecutor.java:95) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpExecutor.execute(DefaultWarpExecutor.java:65) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionObserver.executeWarp(WarpExecutionObserver.java:45) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.warp.impl.client.execution.WarpExecutionInitializer.provideWarpContext(WarpExecutionInitializer.java:64) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpRequestSpecifier.execute(DefaultWarpRequestSpecifier.java:98) > at org.jboss.arquillian.warp.impl.client.execution.DefaultWarpRequestSpecifier.inspect(DefaultWarpRequestSpecifier.java:76) > at org.richfaces.ui.toggle.panelMenu.ITPanelMenu.test_disabled_menu_item(ITPanelMenu.java:91) > test_disabled_menu_item(org.richfaces.ui.toggle.panelMenu.ITPanelMenu) Time elapsed: 7.534 sec <<< ERROR! > java.lang.RuntimeException: unexpected invocation exception during invocation of org.openqa.selenium.TakesScreenshot#getScreenshotAs(), on target 'ReusableRemoteWebDriver: chrome on LINUX (799229cc-608d-49d7-91d3-74d9f487fce3)': org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver.getScreenshotAs(org.openqa.selenium.OutputType) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:135) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver$$EnhancerByGraphene$$94b0812e.getScreenshotAs() > at org.richfaces.arquillian.browser.FailureScreenshot.takeScreenshotOnFailure(FailureScreenshot.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:141) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:114) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:86) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: java.lang.NoSuchMethodException: org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver.getScreenshotAs(org.openqa.selenium.OutputType) > at java.lang.Class.getDeclaredMethod(Class.java:1956) > at org.jboss.arquillian.graphene.proxy.GrapheneProxyHandler.invokeReal(GrapheneProxyHandler.java:124) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$1.invoke(GrapheneContextualHandler.java:159) > at org.jboss.arquillian.graphene.enricher.SearchContextInterceptor.intercept(SearchContextInterceptor.java:50) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:48) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor$1.apply(StaleElementInterceptor.java:44) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:177) > at org.openqa.selenium.support.ui.FluentWait$1.apply(FluentWait.java:175) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208) > at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:175) > at org.jboss.arquillian.graphene.wait.WebDriverWaitImpl.until(WebDriverWaitImpl.java:87) > at org.jboss.arquillian.graphene.enricher.StaleElementInterceptor.intercept(StaleElementInterceptor.java:44) > at org.jboss.arquillian.graphene.proxy.InvocationContextImpl.invoke(InvocationContextImpl.java:87) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler$2.call(GrapheneContextualHandler.java:209) > at org.jboss.arquillian.graphene.context.BrowserActions.performAction(BrowserActions.java:62) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.invoke(GrapheneContextualHandler.java:205) > at org.jboss.arquillian.graphene.proxy.GrapheneContextualHandler.intercept(GrapheneContextualHandler.java:229) > at org.jboss.arquillian.drone.webdriver.factory.remote.reusable.ReusableRemoteWebDriver$$EnhancerByGraphene$$94b0812e.getScreenshotAs() > at org.richfaces.arquillian.browser.FailureScreenshot.takeScreenshotOnFailure(FailureScreenshot.java:28) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.testenricher.cdi.CreationalContextDestroyer.destory(CreationalContextDestroyer.java:44) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createAfterContext(ContainerEventController.java:134) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.after(EventTestRunnerAdaptor.java:103) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:245) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.junit.runners.Suite.runChild(Suite.java:127) > at org.junit.runners.Suite.runChild(Suite.java:26) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.junit.runner.JUnitCore.run(JUnitCore.java:160) > at org.junit.runner.JUnitCore.run(JUnitCore.java:138) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:141) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:114) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:86) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:134) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > 13847 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Shutting down proxy > 13853 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Closing all channels... > 13878 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Stopping timer > 13887 [Thread-4] INFO org.jboss.arquillian.warp.impl.client.proxy.WarpHttpProxyServer - Done shutting down proxy > Results : > Tests in error: > ITPanelMenu.test_disabled_menu_item:91 ? WarpSynchronization The Warp failed t... > ITPanelMenu.test_disabled_menu_item ? Runtime unexpected invocation exception ... > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 04:17:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 16 Jun 2014 04:17:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13671) Upgrade Arquillian PhantomJS In-Reply-To: References: Message-ID: Ji?? ?tefek created RF-13671: -------------------------------- Summary: Upgrade Arquillian PhantomJS Key: RF-13671 URL: https://issues.jboss.org/browse/RF-13671 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: tests - functional Affects Versions: 4.5.0.Alpha2 Reporter: Ji?? ?tefek Assignee: Ji?? ?tefek -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 04:19:25 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 16 Jun 2014 04:19:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13671) Upgrade Arquillian PhantomJS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13671: ----------------------------- Description: Upgrade to version 1.1.3.Final > Upgrade Arquillian PhantomJS > ---------------------------- > > Key: RF-13671 > URL: https://issues.jboss.org/browse/RF-13671 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.5.0.Alpha2 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > > Upgrade to version 1.1.3.Final -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 04:19:25 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 16 Jun 2014 04:19:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13671) Upgrade Arquillian PhantomJS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13671: ----------------------------- Fix Version/s: 4.3.8 4.5.0.Alpha3 5.0.0.Alpha4 > Upgrade Arquillian PhantomJS > ---------------------------- > > Key: RF-13671 > URL: https://issues.jboss.org/browse/RF-13671 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.5.0.Alpha2 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > > Upgrade to version 1.1.3.Final -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 04:35:25 2014 From: issues at jboss.org (Tomas Sykora (JIRA)) Date: Mon, 16 Jun 2014 04:35:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13071) Undeploying Showcase from Tomcat6/7 can cause memory leak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976437#comment-12976437 ] Tomas Sykora commented on RF-13071: ----------------------------------- Hi Lutz, thank you very much for your comment! Yes, you are right. I discovered there probably left some LocalThreads opened and Tomcat detects it. It looks like it's the best to completely avoid them but need to consult with developers. > Undeploying Showcase from Tomcat6/7 can cause memory leak > --------------------------------------------------------- > > Key: RF-13071 > URL: https://issues.jboss.org/browse/RF-13071 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Final, 5.0.0.Alpha1 > Reporter: Juraj H?ska > Priority: Minor > Labels: memory_leak, performance > Fix For: 5-Tracking > > > When undeploying showcase from Tomcat 6/7 then following log is present on the server console: > {code} > SEVERE: The web application [/richfaces-showcase-tomcat6] appears to have started a thread named [Thread-0 (group:HornetQ-client-factory-threads-1831192424-1080990297)] but has failed to stop it. This is very likely to create a memory leak. > {code} > There is lot of such logs, just the _Thread-counter_ is changing. > * 11 such logs just with showcase deploying and then right after undeploying > * bit more when after deploying playing a little bit with {{r:push}} > IMHO it is not just warning. I am experiencing {{Out of Memory}} issues when testing on Tomcat. I need to use quite big {{Perm Gen}} and {{Heap size}} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 05:06:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 16 Jun 2014 05:06:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13671) Upgrade Arquillian PhantomJS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13671: ----------------------------- Fix Version/s: (was: 4.3.8) > Upgrade Arquillian PhantomJS > ---------------------------- > > Key: RF-13671 > URL: https://issues.jboss.org/browse/RF-13671 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.5.0.Alpha2 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha4 > > > Upgrade to version 1.1.3.Final -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 05:46:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 16 Jun 2014 05:46:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13671) Upgrade Arquillian PhantomJS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek resolved RF-13671. ------------------------------ Resolution: Done > Upgrade Arquillian PhantomJS > ---------------------------- > > Key: RF-13671 > URL: https://issues.jboss.org/browse/RF-13671 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.5.0.Alpha2 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha4 > > > Upgrade to version 1.1.3.Final -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 07:39:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 16 Jun 2014 07:39:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13672) Framework tests: add profile for WildFly 8.1 In-Reply-To: References: Message-ID: Ji?? ?tefek created RF-13672: -------------------------------- Summary: Framework tests: add profile for WildFly 8.1 Key: RF-13672 URL: https://issues.jboss.org/browse/RF-13672 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: tests - functional Reporter: Ji?? ?tefek Assignee: Ji?? ?tefek -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 10:47:25 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Mon, 16 Jun 2014 10:47:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976622#comment-12976622 ] Luk?? Fry? commented on RF-13658: --------------------------------- Since it works with ER7, we are fine as it is, right [~bleathem]? > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 16:10:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 16 Jun 2014 16:10:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13071) Undeploying Showcase from Tomcat6/7 can cause memory leak In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13071: ------------------------------- Fix Version/s: 4.5-Tracking (was: 5-Tracking) > Undeploying Showcase from Tomcat6/7 can cause memory leak > --------------------------------------------------------- > > Key: RF-13071 > URL: https://issues.jboss.org/browse/RF-13071 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Final, 5.0.0.Alpha1 > Reporter: Juraj H?ska > Priority: Minor > Labels: memory_leak, performance > Fix For: 4.5-Tracking > > > When undeploying showcase from Tomcat 6/7 then following log is present on the server console: > {code} > SEVERE: The web application [/richfaces-showcase-tomcat6] appears to have started a thread named [Thread-0 (group:HornetQ-client-factory-threads-1831192424-1080990297)] but has failed to stop it. This is very likely to create a memory leak. > {code} > There is lot of such logs, just the _Thread-counter_ is changing. > * 11 such logs just with showcase deploying and then right after undeploying > * bit more when after deploying playing a little bit with {{r:push}} > IMHO it is not just warning. I am experiencing {{Out of Memory}} issues when testing on Tomcat. I need to use quite big {{Perm Gen}} and {{Heap size}} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 16:12:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 16 Jun 2014 16:12:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13635) rich:menuGroup: Menu node image is missing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976743#comment-12976743 ] Brian Leathem commented on RF-13635: ------------------------------------ [~michpetrov] can you just change the image type to PNG permanently then? (And update the stylesheets accordingly) > rich:menuGroup: Menu node image is missing > ------------------------------------------ > > Key: RF-13635 > URL: https://issues.jboss.org/browse/RF-13635 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.6 > Reporter: Marta Juzepczuk > Fix For: 4.3.8 > > > After upgrading to 4.3.6.Final, the small black arrow near rich:menuGroup label disappeared. Background image of the menu item is set to ../org.richfaces.images/menuNodeImage.gif, the same as in previous versions, but the image is empty. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 16:19:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 16 Jun 2014 16:19:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13658) Component issues in 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976745#comment-12976745 ] Brian Leathem commented on RF-13658: ------------------------------------ If it works in the latest EAP 6.3.0-SNAPSHOT release than I would say we are fine. QE please keep a close eye on this though, to make sure we are working when EAP 6.3.0 goes GA. > Component issues in 4.5 > ----------------------- > > Key: RF-13658 > URL: https://issues.jboss.org/browse/RF-13658 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > I've checked showcase and photoalbum and discovered several issues: > These issues appear on EAP but not on WildFly. > * -trees: the node ids are not being resolved correctly, resulting in ids like this: {{overForm:PreDefinedTree:org.richfaces.model.SequenceRowKey\[DeclarativeModelKey\{modelId=j_idt273, modelKey=\}\]:j_idt275}}- > ** -this completely breaks photoalbum- > * data retrieval from server doesn't seem to work (there are no errors on either server or client) > ** datascroller - the pages switch but the data stay the same (works with a4j:repeat) > ** extendedDataTable with enabled ajax loading does not load any data > ** progressbar does not work > ** togglePanel does not switch > ** dynamic tabPanels do not switch > ** tooltips that make a server call do not work (the tooltip is empty) -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 16:29:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 16 Jun 2014 16:29:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13662) doesn't provide selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976749#comment-12976749 ] Brian Leathem commented on RF-13662: ------------------------------------ I'd like to see us resolve this issue by providing any required client-side javascript hooks, rather than complicate the component usage and API by targeting too many use cases. [~matinh] are the "selectItem" and "unselectItem" events not sufficient? > doesn't provide selection > --------------------------------------------- > > Key: RF-13662 > URL: https://issues.jboss.org/browse/RF-13662 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.7 > Reporter: Martin H?ller > Labels: waiting_on_user > > In RichFaces 3.x the component had a selection-Attribute. In RichFaces 4.x this is currently not supported and thus there is not way to obtain the selected entries. Please bring back this useful feature! -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 16:31:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 16 Jun 2014 16:31:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976750#comment-12976750 ] Brian Leathem commented on RF-13663: ------------------------------------ +1 - using {{Warp...filter}} would make the test more clear > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Matej Novotny > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 17:34:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 16 Jun 2014 17:34:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13640: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.8, 4.5.0.Alpha3 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 20:57:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 16 Jun 2014 20:57:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13673) Backport the plain skin fix from RF 5 In-Reply-To: References: Message-ID: Brian Leathem created RF-13673: ---------------------------------- Summary: Backport the plain skin fix from RF 5 Key: RF-13673 URL: https://issues.jboss.org/browse/RF-13673 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: skinning Reporter: Brian Leathem Fix For: 4.5.0.Alpha3 Backport RF-11103. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 21:11:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 16 Jun 2014 21:11:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13640: ------------------------------- Labels: needs-qe regression (was: regression) > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: needs-qe, regression > Fix For: 4.3.8, 4.5.0.Alpha3 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 21:15:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 16 Jun 2014 21:15:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976788#comment-12976788 ] Brian Leathem commented on RF-13640: ------------------------------------ @QE: I've committed a fix for this to the 4.5.x branch. Please verify the issue their before we backport the fix to 4.3.8. (Would it be easier to track the 4.3.8 backport with a separate jira issue?) I checked that my fix works in both Chrome and IE 11. Please verify other supported browsers as well. Also, please check that the use case in the triggering issue remains resolved (RF-13531). Lastly, please verify all showcase samples (the regression introduced with RF-13531 was evident in a showcase sample). cc: [~jhuska] > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: needs-qe, regression > Fix For: 4.3.8, 4.5.0.Alpha3 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 21:15:28 2014 From: issues at jboss.org (Val Blant (JIRA)) Date: Mon, 16 Jun 2014 21:15:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13674) a4j:push broken on WebLogic 12c In-Reply-To: References: Message-ID: Val Blant created RF-13674: ------------------------------ Summary: a4j:push broken on WebLogic 12c Key: RF-13674 URL: https://issues.jboss.org/browse/RF-13674 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.2.0.Final Environment: WebLogic 12c Reporter: Val Blant works properly on Tomcat 7, but fails on WebLogic 12c. {code:title=Page.xhtml|borderStyle=solid} stuff here {code} {code:title=Java Code} TopicKey topicKey = new TopicKey("systemLinks"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, "fly, you fools!"); {code} On Tomcat 7 this work perfectly, and always refreshes '_systemLinksPanel_' when data is published. On Weblogic 12c the data is not flushed correctly. If you use Wireshark, you'd see the following response coming back from the server: {panel:title=Tomcat 7} 3b <"topic":"systemLinks","data":"fly, you fools!","number":0> 0 {panel} {panel:title=Weblogic 12c} 003b <"topic":"systemLinks","data":"fly, you fools!","number":0> {panel} *Note the missing zero terminator line in the WebLogic response!* I narrowed down the problem to the following: {code:title=org.richfaces.application.push.impl.RequestImpl} public synchronized void onBroadcast(AtmosphereResourceEvent event) { MessageDataScriptString serializedMessages = (MessageDataScriptString) event.getMessage(); getSession().clearBroadcastedMessages(serializedMessages.getLastSequenceNumber()); hasActiveBroadcaster = false; if (isPolling()) { event.getResource().resume(); // <= THIS LINE } else { postMessages(); } } {code} There is nothing wrong with this in principle, but it does not work due to a bug in Atmosphere 0.8.4. Calling _AtmosphereResource.resume()_ at this point seems reasonable, since it is supposed to properly finish/commit the _HttpServletResponse_. However, this does not work on WebLogic 12c and leads to incorrectly flushed data demonstrated above. The underlying problem seems to be the fact that _AtmosphereResource.resume()_ method interrupts the thread which flushed the socket Writer before a call to _asyncContext.complete()_ is made: {code} public AtmosphereResource resume() { .... if (!b.isDestroyed()) { b.removeAtmosphereResource(event.getResource()); } .... asyncSupport.action(this); // <= This is where asyncContext.complete() is called } {code} I have verified that calling _asyncContext.complete()_ before we clean up Atmosphere resources fixes the problem. Here's the fix, which needs to go into _RequestImpl.onBroadcast_: {code:title=org.richfaces.application.push.impl.RequestImpl} public synchronized void onBroadcast(AtmosphereResourceEvent event) { .............. if (isPolling()) { // This is the workaround. Completing AsyncContext before cleaning up Atmosphere resources // seems to make this work everywhere. // AsyncContext asyncContext = (AsyncContext) event .getResource() .getRequest() .getAttribute("org.atmosphere.container.asyncContext"); if ( asyncContext != null ) { asyncContext.complete(); } event.getResource().resume(); } else { postMessages(); } } .............. {code} I am attaching a very simple WAR file that demonstrates the problem clearly. The demo app does not use Richfaces, b/c I wanted to remove all unnecessary complexity. Instead I created a couple of simple classes that mimic the behavior of _org.richfaces.webapp.PushHandlerFilter_ and _org.richfaces.application.push.impl.RequestImpl_. In the demo app, _MeteorRequest = RequestImpl_, which is where the fix needs to go. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 21:19:24 2014 From: issues at jboss.org (Val Blant (JIRA)) Date: Mon, 16 Jun 2014 21:19:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13674) a4j:push broken on WebLogic 12c In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Val Blant updated RF-13674: --------------------------- Attachment: atmosphere-weblogic12c-bug-0.8.4.war atmosphere-weblogic12c-bug-0.8.4-sources.jar Attaching a demo app that clearly demonstrates the problem. > a4j:push broken on WebLogic 12c > ------------------------------- > > Key: RF-13674 > URL: https://issues.jboss.org/browse/RF-13674 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Environment: WebLogic 12c > Reporter: Val Blant > Attachments: atmosphere-weblogic12c-bug-0.8.4-sources.jar, atmosphere-weblogic12c-bug-0.8.4.war > > > works properly on Tomcat 7, but fails on WebLogic 12c. > {code:title=Page.xhtml|borderStyle=solid} > > > > > > stuff here > > {code} > {code:title=Java Code} > TopicKey topicKey = new TopicKey("systemLinks"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, "fly, you fools!"); > {code} > On Tomcat 7 this work perfectly, and always refreshes '_systemLinksPanel_' when data is published. > On Weblogic 12c the data is not flushed correctly. If you use Wireshark, you'd see the following response coming back from the server: > {panel:title=Tomcat 7} > 3b > <"topic":"systemLinks","data":"fly, you fools!","number":0> > 0 > {panel} > {panel:title=Weblogic 12c} > 003b > <"topic":"systemLinks","data":"fly, you fools!","number":0> > {panel} > *Note the missing zero terminator line in the WebLogic response!* > I narrowed down the problem to the following: > {code:title=org.richfaces.application.push.impl.RequestImpl} > public synchronized void onBroadcast(AtmosphereResourceEvent event) { > MessageDataScriptString serializedMessages = (MessageDataScriptString) event.getMessage(); > getSession().clearBroadcastedMessages(serializedMessages.getLastSequenceNumber()); > hasActiveBroadcaster = false; > if (isPolling()) { > event.getResource().resume(); // <= THIS LINE > } else { > postMessages(); > } > } > {code} > There is nothing wrong with this in principle, but it does not work due to a bug in Atmosphere 0.8.4. Calling _AtmosphereResource.resume()_ at this point seems reasonable, since it is supposed to properly finish/commit the _HttpServletResponse_. However, this does not work on WebLogic 12c and leads to incorrectly flushed data demonstrated above. > The underlying problem seems to be the fact that _AtmosphereResource.resume()_ method interrupts the thread which flushed the socket Writer before a call to _asyncContext.complete()_ is made: > {code} > public AtmosphereResource resume() { > .... > if (!b.isDestroyed()) { > b.removeAtmosphereResource(event.getResource()); > } > .... > asyncSupport.action(this); // <= This is where asyncContext.complete() is called > } > {code} > I have verified that calling _asyncContext.complete()_ before we clean up Atmosphere resources fixes the problem. > Here's the fix, which needs to go into _RequestImpl.onBroadcast_: > {code:title=org.richfaces.application.push.impl.RequestImpl} > public synchronized void onBroadcast(AtmosphereResourceEvent event) { > .............. > if (isPolling()) { > // This is the workaround. Completing AsyncContext before cleaning up Atmosphere resources > // seems to make this work everywhere. > // > AsyncContext asyncContext = (AsyncContext) > event > .getResource() > .getRequest() > .getAttribute("org.atmosphere.container.asyncContext"); > if ( asyncContext != null ) { > asyncContext.complete(); > } > event.getResource().resume(); > } else { > postMessages(); > } > } > .............. > {code} > I am attaching a very simple WAR file that demonstrates the problem clearly. The demo app does not use Richfaces, b/c I wanted to remove all unnecessary complexity. Instead I created a couple of simple classes that mimic the behavior of _org.richfaces.webapp.PushHandlerFilter_ and _org.richfaces.application.push.impl.RequestImpl_. In the demo app, _MeteorRequest = RequestImpl_, which is where the fix needs to go. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 21:21:24 2014 From: issues at jboss.org (Val Blant (JIRA)) Date: Mon, 16 Jun 2014 21:21:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13674) a4j:push broken on WebLogic 12c In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Val Blant updated RF-13674: --------------------------- Description: works properly on Tomcat 7, but fails on WebLogic 12c. {code:title=Page.xhtml|borderStyle=solid} stuff here {code} {code:title=Java Code} TopicKey topicKey = new TopicKey("systemLinks"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, "fly, you fools!"); {code} On Tomcat 7 this work perfectly, and always refreshes '_systemLinksPanel_' when data is published. On Weblogic 12c the data is not flushed correctly. If you use Wireshark, you'd see the following response coming back from the server: {panel:title=Tomcat 7} 3b <"topic":"systemLinks","data":"fly, you fools!","number":0> 0 {panel} {panel:title=Weblogic 12c} 003b <"topic":"systemLinks","data":"fly, you fools!","number":0> {panel} *Note the missing zero terminator line in the WebLogic response!* I narrowed down the problem to the following: {code:title=org.richfaces.application.push.impl.RequestImpl} public synchronized void onBroadcast(AtmosphereResourceEvent event) { MessageDataScriptString serializedMessages = (MessageDataScriptString) event.getMessage(); getSession().clearBroadcastedMessages(serializedMessages.getLastSequenceNumber()); hasActiveBroadcaster = false; if (isPolling()) { event.getResource().resume(); // <= THIS LINE } else { postMessages(); } } {code} There is nothing wrong with this in principle, but it does not work due to a bug in Atmosphere 0.8.4. Calling _AtmosphereResource.resume()_ at this point seems reasonable, since it is supposed to properly finish/commit the _HttpServletResponse_. However, this does not work on WebLogic 12c and leads to incorrectly flushed data demonstrated above. The underlying problem seems to be the fact that _AtmosphereResource.resume()_ method interrupts the thread which flushed the socket Writer before a call to _asyncContext.complete()_ is made: {code} public AtmosphereResource resume() { .... if (!b.isDestroyed()) { b.removeAtmosphereResource(event.getResource()); } .... asyncSupport.action(this); // <= This is where asyncContext.complete() is called } {code} I have verified that calling _asyncContext.complete()_ before we clean up Atmosphere resources fixes the problem. Here's the fix, which needs to go into _RequestImpl.onBroadcast_: {code:title=org.richfaces.application.push.impl.RequestImpl} public synchronized void onBroadcast(AtmosphereResourceEvent event) { .............. if (isPolling()) { // This is the workaround. Completing AsyncContext before cleaning up Atmosphere resources // seems to make this work everywhere. // AsyncContext asyncContext = (AsyncContext) event .getResource() .getRequest() .getAttribute("org.atmosphere.container.asyncContext"); if ( asyncContext != null ) { asyncContext.complete(); } event.getResource().resume(); } else { postMessages(); } } .............. {code} I am attaching a very simple WAR file that demonstrates the problem clearly. The demo app does not use Richfaces, b/c I wanted to remove all unnecessary complexity. Instead I created a couple of simple classes that mimic the behavior of _org.richfaces.webapp.PushHandlerFilter_ and _org.richfaces.application.push.impl.RequestImpl_. In the demo app, _MeteorRequest = RequestImpl_, which is where the fix needs to go. Please note that according to the Atmosphere author, this problem is fixed in 2.1 branch. Here's the discussion: https://groups.google.com/forum/#!topic/atmosphere-framework/KCKlSmbMrRo was: works properly on Tomcat 7, but fails on WebLogic 12c. {code:title=Page.xhtml|borderStyle=solid} stuff here {code} {code:title=Java Code} TopicKey topicKey = new TopicKey("systemLinks"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, "fly, you fools!"); {code} On Tomcat 7 this work perfectly, and always refreshes '_systemLinksPanel_' when data is published. On Weblogic 12c the data is not flushed correctly. If you use Wireshark, you'd see the following response coming back from the server: {panel:title=Tomcat 7} 3b <"topic":"systemLinks","data":"fly, you fools!","number":0> 0 {panel} {panel:title=Weblogic 12c} 003b <"topic":"systemLinks","data":"fly, you fools!","number":0> {panel} *Note the missing zero terminator line in the WebLogic response!* I narrowed down the problem to the following: {code:title=org.richfaces.application.push.impl.RequestImpl} public synchronized void onBroadcast(AtmosphereResourceEvent event) { MessageDataScriptString serializedMessages = (MessageDataScriptString) event.getMessage(); getSession().clearBroadcastedMessages(serializedMessages.getLastSequenceNumber()); hasActiveBroadcaster = false; if (isPolling()) { event.getResource().resume(); // <= THIS LINE } else { postMessages(); } } {code} There is nothing wrong with this in principle, but it does not work due to a bug in Atmosphere 0.8.4. Calling _AtmosphereResource.resume()_ at this point seems reasonable, since it is supposed to properly finish/commit the _HttpServletResponse_. However, this does not work on WebLogic 12c and leads to incorrectly flushed data demonstrated above. The underlying problem seems to be the fact that _AtmosphereResource.resume()_ method interrupts the thread which flushed the socket Writer before a call to _asyncContext.complete()_ is made: {code} public AtmosphereResource resume() { .... if (!b.isDestroyed()) { b.removeAtmosphereResource(event.getResource()); } .... asyncSupport.action(this); // <= This is where asyncContext.complete() is called } {code} I have verified that calling _asyncContext.complete()_ before we clean up Atmosphere resources fixes the problem. Here's the fix, which needs to go into _RequestImpl.onBroadcast_: {code:title=org.richfaces.application.push.impl.RequestImpl} public synchronized void onBroadcast(AtmosphereResourceEvent event) { .............. if (isPolling()) { // This is the workaround. Completing AsyncContext before cleaning up Atmosphere resources // seems to make this work everywhere. // AsyncContext asyncContext = (AsyncContext) event .getResource() .getRequest() .getAttribute("org.atmosphere.container.asyncContext"); if ( asyncContext != null ) { asyncContext.complete(); } event.getResource().resume(); } else { postMessages(); } } .............. {code} I am attaching a very simple WAR file that demonstrates the problem clearly. The demo app does not use Richfaces, b/c I wanted to remove all unnecessary complexity. Instead I created a couple of simple classes that mimic the behavior of _org.richfaces.webapp.PushHandlerFilter_ and _org.richfaces.application.push.impl.RequestImpl_. In the demo app, _MeteorRequest = RequestImpl_, which is where the fix needs to go. > a4j:push broken on WebLogic 12c > ------------------------------- > > Key: RF-13674 > URL: https://issues.jboss.org/browse/RF-13674 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Environment: WebLogic 12c > Reporter: Val Blant > Attachments: atmosphere-weblogic12c-bug-0.8.4-sources.jar, atmosphere-weblogic12c-bug-0.8.4.war > > > works properly on Tomcat 7, but fails on WebLogic 12c. > {code:title=Page.xhtml|borderStyle=solid} > > > > > > stuff here > > {code} > {code:title=Java Code} > TopicKey topicKey = new TopicKey("systemLinks"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, "fly, you fools!"); > {code} > On Tomcat 7 this work perfectly, and always refreshes '_systemLinksPanel_' when data is published. > On Weblogic 12c the data is not flushed correctly. If you use Wireshark, you'd see the following response coming back from the server: > {panel:title=Tomcat 7} > 3b > <"topic":"systemLinks","data":"fly, you fools!","number":0> > 0 > {panel} > {panel:title=Weblogic 12c} > 003b > <"topic":"systemLinks","data":"fly, you fools!","number":0> > {panel} > *Note the missing zero terminator line in the WebLogic response!* > I narrowed down the problem to the following: > {code:title=org.richfaces.application.push.impl.RequestImpl} > public synchronized void onBroadcast(AtmosphereResourceEvent event) { > MessageDataScriptString serializedMessages = (MessageDataScriptString) event.getMessage(); > getSession().clearBroadcastedMessages(serializedMessages.getLastSequenceNumber()); > hasActiveBroadcaster = false; > if (isPolling()) { > event.getResource().resume(); // <= THIS LINE > } else { > postMessages(); > } > } > {code} > There is nothing wrong with this in principle, but it does not work due to a bug in Atmosphere 0.8.4. Calling _AtmosphereResource.resume()_ at this point seems reasonable, since it is supposed to properly finish/commit the _HttpServletResponse_. However, this does not work on WebLogic 12c and leads to incorrectly flushed data demonstrated above. > The underlying problem seems to be the fact that _AtmosphereResource.resume()_ method interrupts the thread which flushed the socket Writer before a call to _asyncContext.complete()_ is made: > {code} > public AtmosphereResource resume() { > .... > if (!b.isDestroyed()) { > b.removeAtmosphereResource(event.getResource()); > } > .... > asyncSupport.action(this); // <= This is where asyncContext.complete() is called > } > {code} > I have verified that calling _asyncContext.complete()_ before we clean up Atmosphere resources fixes the problem. > Here's the fix, which needs to go into _RequestImpl.onBroadcast_: > {code:title=org.richfaces.application.push.impl.RequestImpl} > public synchronized void onBroadcast(AtmosphereResourceEvent event) { > .............. > if (isPolling()) { > // This is the workaround. Completing AsyncContext before cleaning up Atmosphere resources > // seems to make this work everywhere. > // > AsyncContext asyncContext = (AsyncContext) > event > .getResource() > .getRequest() > .getAttribute("org.atmosphere.container.asyncContext"); > if ( asyncContext != null ) { > asyncContext.complete(); > } > event.getResource().resume(); > } else { > postMessages(); > } > } > .............. > {code} > I am attaching a very simple WAR file that demonstrates the problem clearly. The demo app does not use Richfaces, b/c I wanted to remove all unnecessary complexity. Instead I created a couple of simple classes that mimic the behavior of _org.richfaces.webapp.PushHandlerFilter_ and _org.richfaces.application.push.impl.RequestImpl_. In the demo app, _MeteorRequest = RequestImpl_, which is where the fix needs to go. > Please note that according to the Atmosphere author, this problem is fixed in 2.1 branch. Here's the discussion: https://groups.google.com/forum/#!topic/atmosphere-framework/KCKlSmbMrRo -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 16 21:31:24 2014 From: issues at jboss.org (Val Blant (JIRA)) Date: Mon, 16 Jun 2014 21:31:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13674) a4j:push broken on WebLogic 12c In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Val Blant updated RF-13674: --------------------------- Attachment: RichFacesPushFixFilter.java In the mean time, this filter can be used as a workaround. Note that it does not fix the problem entirely! It makes __ *kind of* work on WebLogic. Sometimes when long-polling connection times out, the client does not issue the next request, so push stops working until the page is refreshed. Could be another problem with the ancient Atmosphere version used by RichFaces. To register the filter: {code:xml|title=web.xml} RichFacesPushFixFilter ca.gc.agr.pushtest.RichFacesPushFixFilter true RichFacesPushFixFilter /__richfaces_push {code} > a4j:push broken on WebLogic 12c > ------------------------------- > > Key: RF-13674 > URL: https://issues.jboss.org/browse/RF-13674 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.0.Final > Environment: WebLogic 12c > Reporter: Val Blant > Attachments: atmosphere-weblogic12c-bug-0.8.4-sources.jar, atmosphere-weblogic12c-bug-0.8.4.war, RichFacesPushFixFilter.java > > > works properly on Tomcat 7, but fails on WebLogic 12c. > {code:title=Page.xhtml|borderStyle=solid} > > > > > > stuff here > > {code} > {code:title=Java Code} > TopicKey topicKey = new TopicKey("systemLinks"); > TopicsContext topicsContext = TopicsContext.lookup(); > topicsContext.publish(topicKey, "fly, you fools!"); > {code} > On Tomcat 7 this work perfectly, and always refreshes '_systemLinksPanel_' when data is published. > On Weblogic 12c the data is not flushed correctly. If you use Wireshark, you'd see the following response coming back from the server: > {panel:title=Tomcat 7} > 3b > <"topic":"systemLinks","data":"fly, you fools!","number":0> > 0 > {panel} > {panel:title=Weblogic 12c} > 003b > <"topic":"systemLinks","data":"fly, you fools!","number":0> > {panel} > *Note the missing zero terminator line in the WebLogic response!* > I narrowed down the problem to the following: > {code:title=org.richfaces.application.push.impl.RequestImpl} > public synchronized void onBroadcast(AtmosphereResourceEvent event) { > MessageDataScriptString serializedMessages = (MessageDataScriptString) event.getMessage(); > getSession().clearBroadcastedMessages(serializedMessages.getLastSequenceNumber()); > hasActiveBroadcaster = false; > if (isPolling()) { > event.getResource().resume(); // <= THIS LINE > } else { > postMessages(); > } > } > {code} > There is nothing wrong with this in principle, but it does not work due to a bug in Atmosphere 0.8.4. Calling _AtmosphereResource.resume()_ at this point seems reasonable, since it is supposed to properly finish/commit the _HttpServletResponse_. However, this does not work on WebLogic 12c and leads to incorrectly flushed data demonstrated above. > The underlying problem seems to be the fact that _AtmosphereResource.resume()_ method interrupts the thread which flushed the socket Writer before a call to _asyncContext.complete()_ is made: > {code} > public AtmosphereResource resume() { > .... > if (!b.isDestroyed()) { > b.removeAtmosphereResource(event.getResource()); > } > .... > asyncSupport.action(this); // <= This is where asyncContext.complete() is called > } > {code} > I have verified that calling _asyncContext.complete()_ before we clean up Atmosphere resources fixes the problem. > Here's the fix, which needs to go into _RequestImpl.onBroadcast_: > {code:title=org.richfaces.application.push.impl.RequestImpl} > public synchronized void onBroadcast(AtmosphereResourceEvent event) { > .............. > if (isPolling()) { > // This is the workaround. Completing AsyncContext before cleaning up Atmosphere resources > // seems to make this work everywhere. > // > AsyncContext asyncContext = (AsyncContext) > event > .getResource() > .getRequest() > .getAttribute("org.atmosphere.container.asyncContext"); > if ( asyncContext != null ) { > asyncContext.complete(); > } > event.getResource().resume(); > } else { > postMessages(); > } > } > .............. > {code} > I am attaching a very simple WAR file that demonstrates the problem clearly. The demo app does not use Richfaces, b/c I wanted to remove all unnecessary complexity. Instead I created a couple of simple classes that mimic the behavior of _org.richfaces.webapp.PushHandlerFilter_ and _org.richfaces.application.push.impl.RequestImpl_. In the demo app, _MeteorRequest = RequestImpl_, which is where the fix needs to go. > Please note that according to the Atmosphere author, this problem is fixed in 2.1 branch. Here's the discussion: https://groups.google.com/forum/#!topic/atmosphere-framework/KCKlSmbMrRo -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 02:15:28 2014 From: issues at jboss.org (=?UTF-8?Q?Martin_H=C3=B6ller_=28JIRA=29?=) Date: Tue, 17 Jun 2014 02:15:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13662) doesn't provide selection In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976822#comment-12976822 ] Martin H?ller commented on RF-13662: ------------------------------------ I'd say providing a selection-attribute simplifies component usage instead of complicating it. selectItem/unselectItem (and maybe a selectionChange-event) are welcome but they would still complicate my use-case compared with the selection-attribute: I'd have to use an additional a4j:jsFunction to propagate the client-side changes to the server. So while I understand your arguing on keeping component API small/simple, I still suggest providing available informations to the user. The user doesn't have to use the selection-attribute if he doesn't need it. So usage would be the same in most cases. > doesn't provide selection > --------------------------------------------- > > Key: RF-13662 > URL: https://issues.jboss.org/browse/RF-13662 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.7 > Reporter: Martin H?ller > Labels: waiting_on_user > > In RichFaces 3.x the component had a selection-Attribute. In RichFaces 4.x this is currently not supported and thus there is not way to obtain the selected entries. Please bring back this useful feature! -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 04:03:24 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 17 Jun 2014 04:03:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13635) rich:menuGroup: Menu node image is missing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976864#comment-12976864 ] Michal Petrov commented on RF-13635: ------------------------------------ [~bleathem] I suppose. I asked [~jhuska] to check the image in his local build and it generated correctly, I tried building it on a virtual machine and it still didn't work. > rich:menuGroup: Menu node image is missing > ------------------------------------------ > > Key: RF-13635 > URL: https://issues.jboss.org/browse/RF-13635 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.6 > Reporter: Marta Juzepczuk > Fix For: 4.3.8 > > > After upgrading to 4.3.6.Final, the small black arrow near rich:menuGroup label disappeared. Background image of the menu item is set to ../org.richfaces.images/menuNodeImage.gif, the same as in previous versions, but the image is empty. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 04:03:25 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 17 Jun 2014 04:03:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13635) rich:menuGroup: Menu node image is missing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov reassigned RF-13635: ---------------------------------- Assignee: Michal Petrov > rich:menuGroup: Menu node image is missing > ------------------------------------------ > > Key: RF-13635 > URL: https://issues.jboss.org/browse/RF-13635 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.6 > Reporter: Marta Juzepczuk > Assignee: Michal Petrov > Fix For: 4.3.8 > > > After upgrading to 4.3.6.Final, the small black arrow near rich:menuGroup label disappeared. Background image of the menu item is set to ../org.richfaces.images/menuNodeImage.gif, the same as in previous versions, but the image is empty. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 04:07:24 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 17 Jun 2014 04:07:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13635) rich:menuGroup: Menu node image is missing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13635. -------------------------------- Resolution: Done > rich:menuGroup: Menu node image is missing > ------------------------------------------ > > Key: RF-13635 > URL: https://issues.jboss.org/browse/RF-13635 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.6 > Reporter: Marta Juzepczuk > Assignee: Michal Petrov > Fix For: 4.3.8 > > > After upgrading to 4.3.6.Final, the small black arrow near rich:menuGroup label disappeared. Background image of the menu item is set to ../org.richfaces.images/menuNodeImage.gif, the same as in previous versions, but the image is empty. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 04:09:24 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 17 Jun 2014 04:09:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13635) rich:menuGroup: Menu node image is missing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-13635: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > rich:menuGroup: Menu node image is missing > ------------------------------------------ > > Key: RF-13635 > URL: https://issues.jboss.org/browse/RF-13635 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.6 > Reporter: Marta Juzepczuk > Assignee: Michal Petrov > Fix For: 4.3.8, 4.5.0.Alpha3 > > > After upgrading to 4.3.6.Final, the small black arrow near rich:menuGroup label disappeared. Background image of the menu item is set to ../org.richfaces.images/menuNodeImage.gif, the same as in previous versions, but the image is empty. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 04:11:24 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=) Date: Tue, 17 Jun 2014 04:11:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13675) Showcase: chart component improvements In-Reply-To: References: Message-ID: Luk?? Macko created RF-13675: -------------------------------- Summary: Showcase: chart component improvements Key: RF-13675 URL: https://issues.jboss.org/browse/RF-13675 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Luk?? Macko Priority: Minor -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 04:35:25 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 17 Jun 2014 04:35:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976873#comment-12976873 ] Ji?? ?tefek commented on RF-13656: ---------------------------------- Verified manually with the Metamer reproducer (RF 5.0.x, 4.5.x, 4.3.x). Also verified, that all EDT tests are passing in Metamer test suite with plain template (RF 5.0.x, 4.5.x, 4.3.x). > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Michal Petrov > Labels: regression > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 04:35:26 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 17 Jun 2014 04:35:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13656: ----------------------------- Labels: regression (was: needs-qe regression) > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Michal Petrov > Labels: regression > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 04:35:27 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 17 Jun 2014 04:35:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13656) Table collapse after tab change In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13656. ---------------------------- > Table collapse after tab change > ------------------------------- > > Key: RF-13656 > URL: https://issues.jboss.org/browse/RF-13656 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.7 > Reporter: Andr? Faber > Assignee: Michal Petrov > Labels: regression > Fix For: 4.3.8, 4.5.0.Alpha3, 5.0.0.Alpha4 > > Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg, test.xhtml, TestBean.java > > > I have a rich:tabPanel with 2 tabs containing each a rich:extendedDataTable this worked fine in version 4.3.6. But with version 4.3.7 the table "collapses" after the tab is changed (see pictures). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 05:52:25 2014 From: issues at jboss.org (Konstantin Morozov (JIRA)) Date: Tue, 17 Jun 2014 05:52:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13606) WebSphere/MyFaces in 4.3.6 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976911#comment-12976911 ] Konstantin Morozov commented on RF-13606: ----------------------------------------- For those who interested... WAS 8.x is bundled with 2.0.2 MyFaces implementation and it is not enough. The problem was solved by including myfaces-impl-2.1.3.jar in to WEB_INF\lib. > WebSphere/MyFaces in 4.3.6 > -------------------------- > > Key: RF-13606 > URL: https://issues.jboss.org/browse/RF-13606 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.6 > Environment: WebSphere AS 8.0.0.8 > Reporter: Konstantin Morozov > > Application started successfully, but throws exception when launched: > {code} > org.richfaces.resource.external.MyFacesExternalResourceTracker handleException error while delegating resource handling to myfaces impl > java.lang.NoSuchMethodException: org.apache.myfaces.shared_impl.renderkit.html.util.ResourceUtils.isRenderedStylesheet(javax.faces.context.FacesContext, java.lang.String, java.lang.String) > at java.lang.Class.throwNoSuchMethodException(Class.java:325) > at java.lang.Class.getMethod(Class.java:939) > at org.richfaces.resource.external.MyFacesExternalResourceTracker.(MyFacesExternalResourceTracker.java:52) > at org.richfaces.resource.external.ExternalResourceTrackerWrapper.getWrapped(ExternalResourceTrackerWrapper.java:94) > at org.richfaces.resource.external.ExternalResourceTrackerWrapper.markExternalResourceRendered(ExternalResourceTrackerWrapper.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at org.richfaces.application.ServiceTracker$1.invoke(ServiceTracker.java:153) > at com.sun.proxy.$Proxy284.markExternalResourceRendered(Unknown Source) > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:358) > at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270) > at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280) > at com.sun.faces.renderkit.html_basic.StylesheetRenderer.encodeEnd(StylesheetRenderer.java:97) > at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:915) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) > at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105) > at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92) > at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:915) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) > at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) > at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1071) > at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3774) > at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) > at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:981) > at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) > at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:277) > at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) > at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) > at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) > at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) > at com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.java:205) > at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1702) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 08:48:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 17 Jun 2014 08:48:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13676) InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable In-Reply-To: References: Message-ID: Juraj H?ska created RF-13676: -------------------------------- Summary: InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable Key: RF-13676 URL: https://issues.jboss.org/browse/RF-13676 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.5.0.Alpha3 Reporter: Juraj H?ska If {{InputNumberSpinner}} is nested in e.g. {{collapsiblesubTable}}, then JSR303 bean validation does not work when triggered with a4j:commandButton. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 08:50:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 17 Jun 2014 08:50:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13676) InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13676: ----------------------------- Labels: regression (was: ) > InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable > ---------------------------------------------------------------------------------------------------- > > Key: RF-13676 > URL: https://issues.jboss.org/browse/RF-13676 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > If {{InputNumberSpinner}} is nested in e.g. {{collapsiblesubTable}}, then JSR303 bean validation does not work when triggered with a4j:commandButton. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 09:07:27 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 17 Jun 2014 09:07:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13665) RichFaces 4.5 should fail fast when used with un-pached Mojarra In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977014#comment-12977014 ] Ji?? ?tefek commented on RF-13665: ---------------------------------- I've tried to deploy Metamer to: * EAP 6.3.0.Beta2: deployed (as expected) * Tomcat 7 with jsf 2.2.6 (default) or 2.1.28: deployed (as expected) * GlassFish 4.0 : failed (as expected) with message {{The JSF implementation 2.2.0 does not support the RichFaces ExtendedPartialViewContext. Please upgrade to at least Mojarra 2.1.28 or 2.2.6}} * AS 7.1 : failed (as expected), similar message as for GF 4.0 * Tomcat 7 with jsf 2.2.5 or 2.1.27: failed (as expected), similar message as for GF 4.0 * {color:red}GlassFish 3.1.2.2{color:red}: failed (as expected), but *failed with wrong error* : {code} SEVERE: Critical error during deployment: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! For input string: "6-SNAPSHOT" at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:375) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225) at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:4750) at com.sun.enterprise.web.WebModule.contextListenerStart(WebModule.java:550) at org.apache.catalina.core.StandardContext.start(StandardContext.java:5366) at com.sun.enterprise.web.WebModule.start(WebModule.java:498) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:917) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:901) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:733) at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:2019) at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1669) at com.sun.enterprise.web.WebApplication.start(WebApplication.java:109) at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130) at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269) at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:301) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259) at org.glassfish.admin.rest.ResourceUtil.runCommand(ResourceUtil.java:214) at org.glassfish.admin.rest.ResourceUtil.runCommand(ResourceUtil.java:207) at org.glassfish.admin.rest.resources.TemplateListOfResource.createResource(TemplateListOfResource.java:148) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288) at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339) at com.sun.jersey.server.impl.container.grizzly.GrizzlyContainer._service(GrizzlyContainer.java:182) at com.sun.jersey.server.impl.container.grizzly.GrizzlyContainer.service(GrizzlyContainer.java:147) at org.glassfish.admin.rest.adapter.RestAdapter.service(RestAdapter.java:148) at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179) at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117) at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.NumberFormatException: For input string: "6-SNAPSHOT" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:492) at java.lang.Integer.parseInt(Integer.java:527) at org.richfaces.application.JsfVersionInspector.parseVersion(JsfVersionInspector.java:172) at org.richfaces.application.JsfVersionInspector.verifyJsfImplVersion(JsfVersionInspector.java:85) at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:66) at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:167) at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2168) at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2144) at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:302) at javax.faces.application.ApplicationWrapper.publishEvent(ApplicationWrapper.java:683) at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:600) at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:369) ... 66 more {code} Should I try any other containers? > RichFaces 4.5 should fail fast when used with un-pached Mojarra > --------------------------------------------------------------- > > Key: RF-13665 > URL: https://issues.jboss.org/browse/RF-13665 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > > [~bleathem] wrote [in this comment|https://issues.jboss.org/browse/RF-13658?focusedCommentId=12975468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12975468] for RF-13658: > ??There is a Mojarra bug that breaks the new EPVC ([JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also patched?? > ??We should have some code in place to fail fast if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in [JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]?? > And we are not failing fast. I would say that when application is about to use unpached Mojarra, the fail fast would be a runtime exception during deployment ? > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 09:37:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 17 Jun 2014 09:37:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider does not update value in bean when nested e.g. in a4jRepeat In-Reply-To: References: Message-ID: Juraj H?ska created RF-13677: -------------------------------- Summary: InputNumberSlider does not update value in bean when nested e.g. in a4jRepeat Key: RF-13677 URL: https://issues.jboss.org/browse/RF-13677 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.5.0.Alpha3 Reporter: Juraj H?ska When {{inputNumberSlider}} is nested in either: * uiRepeat * a4jRepeat * richExtendedDataTable * richCollapsibleSubTable * richDataGrid * richDataTable then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 09:37:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 17 Jun 2014 09:37:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider does not update value in bean when nested e.g. in a4jRepeat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13677: ----------------------------- Labels: regression (was: ) > InputNumberSlider does not update value in bean when nested e.g. in a4jRepeat > ----------------------------------------------------------------------------- > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > When {{inputNumberSlider}} is nested in either: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 09:39:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 17 Jun 2014 09:39:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider does not update value in bean when nested e.g. in a4jRepeat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13677: ----------------------------- Description: When {{inputNumberSlider}} is nested in either of these iteration components: * uiRepeat * a4jRepeat * richExtendedDataTable * richCollapsibleSubTable * richDataGrid * richDataTable then the property of the bean bound to its {{value}} attribute is not updated by ajax request. was: When {{inputNumberSlider}} is nested in either: * uiRepeat * a4jRepeat * richExtendedDataTable * richCollapsibleSubTable * richDataGrid * richDataTable then the property of the bean bound to its {{value}} attribute is not updated by ajax request. > InputNumberSlider does not update value in bean when nested e.g. in a4jRepeat > ----------------------------------------------------------------------------- > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > When {{inputNumberSlider}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 09:55:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 17 Jun 2014 09:55:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider & Spinner does not update value in bean when nested e.g. in a4jRepeat In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13677: ----------------------------- Summary: InputNumberSlider & Spinner does not update value in bean when nested e.g. in a4jRepeat (was: InputNumberSlider does not update value in bean when nested e.g. in a4jRepeat) > InputNumberSlider & Spinner does not update value in bean when nested e.g. in a4jRepeat > --------------------------------------------------------------------------------------- > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > When {{inputNumberSlider}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 09:55:26 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 17 Jun 2014 09:55:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider & Spinner does not update value in bean when nested iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13677: ----------------------------- Description: When {{inputNumberSlider}} or {{inputNumberSpinner}} is nested in either of these iteration components: * uiRepeat * a4jRepeat * richExtendedDataTable * richCollapsibleSubTable * richDataGrid * richDataTable then the property of the bean bound to its {{value}} attribute is not updated by ajax request. was: When {{inputNumberSlider}} is nested in either of these iteration components: * uiRepeat * a4jRepeat * richExtendedDataTable * richCollapsibleSubTable * richDataGrid * richDataTable then the property of the bean bound to its {{value}} attribute is not updated by ajax request. > InputNumberSlider & Spinner does not update value in bean when nested iteration components > ------------------------------------------------------------------------------------------ > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > When {{inputNumberSlider}} or {{inputNumberSpinner}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 09:55:26 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 17 Jun 2014 09:55:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider & Spinner does not update value in bean when nested iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13677: ----------------------------- Summary: InputNumberSlider & Spinner does not update value in bean when nested iteration components (was: InputNumberSlider & Spinner does not update value in bean when nested e.g. in a4jRepeat) > InputNumberSlider & Spinner does not update value in bean when nested iteration components > ------------------------------------------------------------------------------------------ > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > When {{inputNumberSlider}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 09:57:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 17 Jun 2014 09:57:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13582) Revert the core package re-factoring In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977037#comment-12977037 ] Ji?? ?tefek commented on RF-13582: ---------------------------------- I have created a branch in qa repo for this. [This commit|https://github.com/richfaces/richfaces-qa/commit/5eab3f39145cf1bd65e58a1798c39b967b19d5d2] adds the RF 4.5 jars to Metamer and make it compilable, could you, please, check if I didn't something wrong? As you can see in the commit, there are just changes in rich components. I've also run all tests for a4j components from this branch ([verified with this job|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/richfaces-x.y-metamer-parametrized-test-runner-win/375/], ignore the status JS API tests (different call of JS API function in RF 4.3 and 4.5 {{RichFaces.$}} X {{RichFaces.component}})) + manually verified {{queue}} and {{attachedQueue}} components (there are no WebDriver tests for them). From these results I can confirm that all a4j components works correctly. > Revert the core package re-factoring > ------------------------------------ > > Key: RF-13582 > URL: https://issues.jboss.org/browse/RF-13582 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Michal Petrov > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > To improve compatibility with RichFaces 4.3, the package re-factorings introduced should be reverted. These include (but are not limited to): > * .servlet (PushServlet, ResourceServlet) > * .push.cdi (@PUsh) > * .push. (TopicContext) > * FileUploadException > A good test for this would be to compile and run the RichFaces 4.3 showcase and metamer samples against RichFaces 4.5 looking for failures. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:10:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:10:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13672) Framework tests: add profile for WildFly 8.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13672: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Framework tests: add profile for WildFly 8.1 > -------------------------------------------- > > Key: RF-13672 > URL: https://issues.jboss.org/browse/RF-13672 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 4.5.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:10:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:10:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13675) Showcase: chart component improvements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13675: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Showcase: chart component improvements > -------------------------------------- > > Key: RF-13675 > URL: https://issues.jboss.org/browse/RF-13675 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Luk?? Macko > Priority: Minor > Fix For: 4.5.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:10:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:10:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13676) InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13676: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable > ---------------------------------------------------------------------------------------------------- > > Key: RF-13676 > URL: https://issues.jboss.org/browse/RF-13676 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > > If {{InputNumberSpinner}} is nested in e.g. {{collapsiblesubTable}}, then JSR303 bean validation does not work when triggered with a4j:commandButton. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:10:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:10:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider & Spinner does not update value in bean when nested iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13677: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > InputNumberSlider & Spinner does not update value in bean when nested iteration components > ------------------------------------------------------------------------------------------ > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > > When {{inputNumberSlider}} or {{inputNumberSpinner}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:16:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:16:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13651) Integration tests failing in chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13651: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 3, 4.5.0.Alpha3 - Sprint 4 (was: 4.5.0.Alpha3 - Sprint 3) > Integration tests failing in chrome > ----------------------------------- > > Key: RF-13651 > URL: https://issues.jboss.org/browse/RF-13651 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > The framework tests pass in phantomjs but some fail in chrome. > Resolution of this issue involves running and stabilizing the tests in all supported browsers. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:16:36 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:16:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13640: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4 > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: needs-qe, regression > Fix For: 4.3.8, 4.5.0.Alpha3 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:16:36 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:16:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13660) RichFaces 4.5 integration tests - error after test execution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13660: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4 > RichFaces 4.5 integration tests - error after test execution > ------------------------------------------------------------ > > Key: RF-13660 > URL: https://issues.jboss.org/browse/RF-13660 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Environment: AS: Wildfly > Browser: PhantomJS > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > This issue originated from RF-13591. > There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/src/test/integration/org/richfaces/integration/resource/ITResourceMapping.java]. > The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines. > Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5/56/console]. > The exception in server console is: > {code} > 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException > at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:] > at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:] > at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:] > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] > at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:] > at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:16:36 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:16:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13672) Framework tests: add profile for WildFly 8.1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13672: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4 > Framework tests: add profile for WildFly 8.1 > -------------------------------------------- > > Key: RF-13672 > URL: https://issues.jboss.org/browse/RF-13672 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 4.5.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:16:36 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:16:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13673) Backport the plain skin fix from RF 5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13673: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4 > Backport the plain skin fix from RF 5 > ------------------------------------- > > Key: RF-13673 > URL: https://issues.jboss.org/browse/RF-13673 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: skinning > Reporter: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > Backport RF-11103. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:16:36 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:16:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13675) Showcase: chart component improvements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13675: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4 > Showcase: chart component improvements > -------------------------------------- > > Key: RF-13675 > URL: https://issues.jboss.org/browse/RF-13675 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Luk?? Macko > Priority: Minor > Fix For: 4.5.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:16:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:16:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13676) InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13676: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4 > InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable > ---------------------------------------------------------------------------------------------------- > > Key: RF-13676 > URL: https://issues.jboss.org/browse/RF-13676 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > > If {{InputNumberSpinner}} is nested in e.g. {{collapsiblesubTable}}, then JSR303 bean validation does not work when triggered with a4j:commandButton. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:16:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:16:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider & Spinner does not update value in bean when nested iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13677: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4 > InputNumberSlider & Spinner does not update value in bean when nested iteration components > ------------------------------------------------------------------------------------------ > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > > When {{inputNumberSlider}} or {{inputNumberSpinner}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:22:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:22:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13640. -------------------------------- Labels: needs-backport needs-qe regression (was: needs-qe regression) Resolution: Done > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: needs-qe, regression, needs-backport > Fix For: 4.3.8, 4.5.0.Alpha3 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:26:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:26:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13673) Backport the plain skin fix from RF 5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13673: ---------------------------------- Assignee: Brian Leathem > Backport the plain skin fix from RF 5 > ------------------------------------- > > Key: RF-13673 > URL: https://issues.jboss.org/browse/RF-13673 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: skinning > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > Backport RF-11103. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:28:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:28:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13675) Showcase: chart component improvements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13675: ---------------------------------- Assignee: Luk?? Macko > Showcase: chart component improvements > -------------------------------------- > > Key: RF-13675 > URL: https://issues.jboss.org/browse/RF-13675 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Luk?? Macko > Assignee: Luk?? Macko > Priority: Minor > Fix For: 4.5.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:30:26 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 17 Jun 2014 10:30:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider & Spinner does not update value in bean when nested iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov reassigned RF-13677: ---------------------------------- Assignee: Michal Petrov > InputNumberSlider & Spinner does not update value in bean when nested iteration components > ------------------------------------------------------------------------------------------ > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > > When {{inputNumberSlider}} or {{inputNumberSpinner}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:30:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:30:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13660) RichFaces 4.5 integration tests - error after test execution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13660: ---------------------------------- Assignee: Brian Leathem > RichFaces 4.5 integration tests - error after test execution > ------------------------------------------------------------ > > Key: RF-13660 > URL: https://issues.jboss.org/browse/RF-13660 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Environment: AS: Wildfly > Browser: PhantomJS > Reporter: Matej Novotny > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > This issue originated from RF-13591. > There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/src/test/integration/org/richfaces/integration/resource/ITResourceMapping.java]. > The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines. > Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5/56/console]. > The exception in server console is: > {code} > 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException > at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:] > at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:] > at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:] > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] > at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:] > at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:30:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 17 Jun 2014 10:30:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13676) InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13676: ---------------------------------- Assignee: Michal Petrov > InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable > ---------------------------------------------------------------------------------------------------- > > Key: RF-13676 > URL: https://issues.jboss.org/browse/RF-13676 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > > If {{InputNumberSpinner}} is nested in e.g. {{collapsiblesubTable}}, then JSR303 bean validation does not work when triggered with a4j:commandButton. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Tue Jun 17 10:56:26 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 17 Jun 2014 10:56:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider & Spinner does not update value in bean when nested iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977071#comment-12977071 ] Michal Petrov commented on RF-13677: ------------------------------------ The value in the bean is updated, it's just the render that is not working correctly. In case of the example above the render is called on {{form:containerRichDataTable:0:output}} but it should be {{?:2:output}}. I am also getting an error when switching templates. > InputNumberSlider & Spinner does not update value in bean when nested iteration components > ------------------------------------------------------------------------------------------ > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > > When {{inputNumberSlider}} or {{inputNumberSpinner}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 03:07:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 03:07:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider & Spinner render does not work when nested iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13677: ----------------------------- Summary: InputNumberSlider & Spinner render does not work when nested iteration components (was: InputNumberSlider & Spinner does not update value in bean when nested iteration components) > InputNumberSlider & Spinner render does not work when nested iteration components > --------------------------------------------------------------------------------- > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > > When {{inputNumberSlider}} or {{inputNumberSpinner}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 03:07:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 03:07:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider & Spinner render does not work when nested in iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13677: ----------------------------- Summary: InputNumberSlider & Spinner render does not work when nested in iteration components (was: InputNumberSlider & Spinner render does not work when nested iteration components) > InputNumberSlider & Spinner render does not work when nested in iteration components > ------------------------------------------------------------------------------------ > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > > When {{inputNumberSlider}} or {{inputNumberSpinner}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 03:33:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 03:33:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13678) Render @all does not work for nested a4j:region in collapsibleSubTable In-Reply-To: References: Message-ID: Juraj H?ska created RF-13678: -------------------------------- Summary: Render @all does not work for nested a4j:region in collapsibleSubTable Key: RF-13678 URL: https://issues.jboss.org/browse/RF-13678 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.5.0.Alpha3 Reporter: Juraj H?ska Suppose nested {{regions}} in a {{collapsibleSubTable}}. Those regions are not updated when a {{commandButton}} with {{render}} attribute set to {{@all}} is submitted. IMHO it is somehow connected with RF-13677, however, this issue occurs only with combination of {{regions}} and {{collapsibleSubTable}}, other iteration components works in this matter. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 03:37:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 03:37:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13678) Render @all does not work for nested a4j:region in collapsibleSubTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13678: ----------------------------- Labels: regression (was: ) > Render @all does not work for nested a4j:region in collapsibleSubTable > ---------------------------------------------------------------------- > > Key: RF-13678 > URL: https://issues.jboss.org/browse/RF-13678 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > Suppose nested {{regions}} in a {{collapsibleSubTable}}. > Those regions are not updated when a {{commandButton}} with {{render}} attribute set to {{@all}} is submitted. > IMHO it is somehow connected with RF-13677, however, this issue occurs only with combination of {{regions}} and {{collapsibleSubTable}}, other iteration components works in this matter. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 03:41:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 03:41:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13676) InputNumberSpinner - JSR validation is not triggered by ajax when nested in iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13676: ----------------------------- Summary: InputNumberSpinner - JSR validation is not triggered by ajax when nested in iteration components (was: InputNumberSpinner - JSR validation is not triggered by ajax when nested in e.g. collapsibleSubTable) > InputNumberSpinner - JSR validation is not triggered by ajax when nested in iteration components > ------------------------------------------------------------------------------------------------ > > Key: RF-13676 > URL: https://issues.jboss.org/browse/RF-13676 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > > If {{InputNumberSpinner}} is nested in e.g. {{collapsiblesubTable}}, then JSR303 bean validation does not work when triggered with a4j:commandButton. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:05:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 04:05:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek reopened RF-13640: ------------------------------ Reopening. Can still be reproduced in showcase. Tried with Chrome 35, Safari 5.1.7, Firefox 30, IE 11. On: EAP 6.3 RF version: richfaces-4.5.0-20140618.062938-20.jar > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: needs-backport, needs-qe, regression > Fix For: 4.3.8, 4.5.0.Alpha3 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:07:25 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 04:07:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977264#comment-12977264 ] Ji?? ?tefek commented on RF-13640: ---------------------------------- [~jhuska] was able to reproduce it too. > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: needs-backport, needs-qe, regression > Fix For: 4.3.8, 4.5.0.Alpha3 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:15:26 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 04:15:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977269#comment-12977269 ] Ji?? ?tefek commented on RF-13640: ---------------------------------- I've also noticed that the sample in Showcase is using @layout=table, but the issue [RF-12820: AutoComplete Layout Table is broken|https://issues.jboss.org/browse/RF-12820] is still not resolved. > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: needs-backport, needs-qe, regression > Fix For: 4.3.8, 4.5.0.Alpha3 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:17:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 04:17:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13676) InputNumberSpinner - Validation is not triggered by ajax when nested in iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13676: ----------------------------- Summary: InputNumberSpinner - Validation is not triggered by ajax when nested in iteration components (was: InputNumberSpinner - JSR validation is not triggered by ajax when nested in iteration components) > InputNumberSpinner - Validation is not triggered by ajax when nested in iteration components > -------------------------------------------------------------------------------------------- > > Key: RF-13676 > URL: https://issues.jboss.org/browse/RF-13676 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > > If {{InputNumberSpinner}} is nested in e.g. {{collapsiblesubTable}}, then JSR303 bean validation does not work when triggered with a4j:commandButton. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:17:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 04:17:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13676) InputNumberSpinner - Validation is not triggered by ajax when nested in iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13676: ----------------------------- Description: If {{InputNumberSpinner}} is nested in e.g. {{collapsiblesubTable}}, then validation (both Cliend Side Validation & JSR303 bean validation) does not work when triggered with a4j:commandButton. (was: If {{InputNumberSpinner}} is nested in e.g. {{collapsiblesubTable}}, then JSR303 bean validation does not work when triggered with a4j:commandButton.) > InputNumberSpinner - Validation is not triggered by ajax when nested in iteration components > -------------------------------------------------------------------------------------------- > > Key: RF-13676 > URL: https://issues.jboss.org/browse/RF-13676 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > > If {{InputNumberSpinner}} is nested in e.g. {{collapsiblesubTable}}, then validation (both Cliend Side Validation & JSR303 bean validation) does not work when triggered with a4j:commandButton. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:31:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 04:31:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13520) mediaOutput: NPE is thrown when used with CDI beans and JSF 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13520: ----------------------------- Steps to Reproduce: # build and deploy Metamer, load http://localhost:8080/metamer/faces/components/a4jMediaOutput/rf-13098.xhtml # see that no picture is rendered and that NPE is thrown to the WildFly console was: # build and deploy Metamer, load http://localhost:8080/metamer/faces/components/a4jMediaOutput/rf13098.xhtml # see that no picture is rendered and that NPE is thrown to the WildFly console > mediaOutput: NPE is thrown when used with CDI beans and JSF 2.2 > --------------------------------------------------------------- > > Key: RF-13520 > URL: https://issues.jboss.org/browse/RF-13520 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha3 > Environment: WildFly 8.0.0.Final-SNAPSHOT > WildFly 8.0.0.CR1 > Reporter: Juraj H?ska > Assignee: Brian Leathem > Priority: Critical > Labels: 45x, jsf22 > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > > When {{mediaOutput}} is bound via {{value}} attribute to a *CDI* bean, following NPE is thrown: > {code} > 15:32:20,443 ERROR [io.undertow.request] (default task-16) UT005023: Exception handling request to /metamer/faces/rfRes/org.richfaces.ui.output.mediaOutput.MediaOutputResource: java.lang.NullPointerException > at org.richfaces.ui.output.mediaOutput.MediaOutputResource.encode(MediaOutputResource.java:66) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:69) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:69) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.SessionRestoringHandler.handleRequest(SessionRestoringHandler.java:101) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:685) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] > {code} > Note that everything works with JSF 2.1.x (AS 7.1.1.Final) and when Managed Beans are used. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:49:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 04:49:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13679) PickList is missing styleClass attribute In-Reply-To: References: Message-ID: Juraj H?ska created RF-13679: -------------------------------- Summary: PickList is missing styleClass attribute Key: RF-13679 URL: https://issues.jboss.org/browse/RF-13679 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 4.5.0.Alpha3 Reporter: Juraj H?ska {{PickList}} is missing {{styleClass}} attribute. It can not be found in generated {{faces-config.xml}}, in: {{richfaces-4.5.0-SNAPSHOT.jar/META-INF/faces-config.xml}}. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:49:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 04:49:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13679) PickList is missing styleClass attribute In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13679: ----------------------------- Labels: regression (was: ) > PickList is missing styleClass attribute > ---------------------------------------- > > Key: RF-13679 > URL: https://issues.jboss.org/browse/RF-13679 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > {{PickList}} is missing {{styleClass}} attribute. > It can not be found in generated {{faces-config.xml}}, in: {{richfaces-4.5.0-SNAPSHOT.jar/META-INF/faces-config.xml}}. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:57:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 04:57:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13520) mediaOutput: NPE is thrown when used with CDI beans and JSF 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13520. ---------------------------- Closing. Verified in RF 4.5. on WildFly 8.1 and Firefox 30 with reproducer in Metamer. Also verified, that all a4jMediaOutput tests in Metamer are passing with this configuration. > mediaOutput: NPE is thrown when used with CDI beans and JSF 2.2 > --------------------------------------------------------------- > > Key: RF-13520 > URL: https://issues.jboss.org/browse/RF-13520 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha3 > Environment: WildFly 8.0.0.Final-SNAPSHOT > WildFly 8.0.0.CR1 > Reporter: Juraj H?ska > Assignee: Brian Leathem > Priority: Critical > Labels: 45x, jsf22 > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > > When {{mediaOutput}} is bound via {{value}} attribute to a *CDI* bean, following NPE is thrown: > {code} > 15:32:20,443 ERROR [io.undertow.request] (default task-16) UT005023: Exception handling request to /metamer/faces/rfRes/org.richfaces.ui.output.mediaOutput.MediaOutputResource: java.lang.NullPointerException > at org.richfaces.ui.output.mediaOutput.MediaOutputResource.encode(MediaOutputResource.java:66) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:643) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) [classes:] > at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:70) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:69) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:69) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.SessionRestoringHandler.handleRequest(SessionRestoringHandler.java:101) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:685) [undertow-core-1.0.0.Beta33.jar:1.0.0.Beta33] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] > {code} > Note that everything works with JSF 2.1.x (AS 7.1.1.Final) and when Managed Beans are used. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 04:59:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 04:59:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13679) PickList is missing styleClass attribute In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977277#comment-12977277 ] Juraj H?ska commented on RF-13679: ---------------------------------- My guess is that it was introduced with [this|https://github.com/richfaces/richfaces/commit/a0427e1f8795310e2caef86ecb700879693c3461] commit > PickList is missing styleClass attribute > ---------------------------------------- > > Key: RF-13679 > URL: https://issues.jboss.org/browse/RF-13679 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > {{PickList}} is missing {{styleClass}} attribute. > It can not be found in generated {{faces-config.xml}}, in: {{richfaces-4.5.0-SNAPSHOT.jar/META-INF/faces-config.xml}}. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 05:19:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 05:19:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13518) Action Listener - invoking from composite component does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13518. ---------------------------- Closing. Verified in RF 4.5. Verified in Metamer with tests for a4jActionListener on EAP 6.3 (jsf 2.1) and WildFly 8.1 (jsf 2.2). > Action Listener - invoking from composite component does not work > ----------------------------------------------------------------- > > Key: RF-13518 > URL: https://issues.jboss.org/browse/RF-13518 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha3 > Environment: WildFly 8.0.0.Final-SNAPSHOT > Reporter: Juraj H?ska > Assignee: Luk?? Fry? > Priority: Critical > Labels: 45x, jsf22 > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > > Invoking Action Listener from composite component does not work. Please see the steps to reproduce the issue. > Note that it works with JSF 2.1.x. It is similar to issue RF-10585, but that one is for MyFaces. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 05:33:25 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 05:33:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13513) CollectionDataModel API is not available on pre-JSF 2.1 that poses backward compatibility problem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13513: ----------------------------- Fix Version/s: 4.5.0.Alpha3 > CollectionDataModel API is not available on pre-JSF 2.1 that poses backward compatibility problem > ------------------------------------------------------------------------------------------------- > > Key: RF-13513 > URL: https://issues.jboss.org/browse/RF-13513 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha3 > Environment: 5.0.0-SNAPSHOT > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > > As we have introduced support for collections, leveraging JSF 2.2 CollectionDataModel, this might prevent some pre-JSF 2.2 containers to work correctly with component using UISeuqence or AutocompleteRendererBase. > This is an exception from TomEE 1.5.1 with MyFaces 2.1.10: > {code} > SEVERE: Class : org.richfaces.ui.input.autocomplete.AutocompleteRenderer not found. > java.lang.NoClassDefFoundError: javax/faces/model/CollectionDataModel > at java.lang.Class.getDeclaredConstructors0(Native Method) > at java.lang.Class.privateGetDeclaredConstructors(Class.java:2493) > at java.lang.Class.getConstructor0(Class.java:2803) > at java.lang.Class.newInstance(Class.java:345) > at org.apache.myfaces.shared.util.ClassUtils.newInstance(ClassUtils.java:379) > at org.apache.myfaces.shared.util.ClassUtils.newInstance(ClassUtils.java:342) > at org.apache.myfaces.config.FacesConfigurator.configureRenderKits(FacesConfigurator.java:910) > at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:420) > at org.apache.myfaces.webapp.AbstractFacesInitializer.buildConfiguration(AbstractFacesInitializer.java:370) > at org.apache.myfaces.webapp.Jsp21FacesInitializer.initContainerIntegration(Jsp21FacesInitializer.java:73) > at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:143) > at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791) > at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) > at org.apache.tomee.catalina.TomcatWebAppBuilder.deployWar(TomcatWebAppBuilder.java:538) > at org.apache.tomee.catalina.TomcatWebAppBuilder.deployWebApps(TomcatWebAppBuilder.java:509) > at org.apache.tomee.catalina.deployment.TomcatWebappDeployer.deploy(TomcatWebappDeployer.java:44) > at org.apache.openejb.assembler.DeployerEjb.deploy(DeployerEjb.java:131) > at org.apache.openejb.assembler.DeployerEjb.deploy(DeployerEjb.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.security.internal.InternalSecurityInterceptor.invoke(InternalSecurityInterceptor.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.cdi.CdiInterceptor.invoke(CdiInterceptor.java:128) > at org.apache.openejb.cdi.CdiInterceptor.access$000(CdiInterceptor.java:43) > at org.apache.openejb.cdi.CdiInterceptor$1.call(CdiInterceptor.java:64) > at org.apache.openejb.cdi.CdiInterceptor.aroundInvoke(CdiInterceptor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.monitoring.StatsInterceptor.record(StatsInterceptor.java:176) > at org.apache.openejb.monitoring.StatsInterceptor.invoke(StatsInterceptor.java:95) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:138) > at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:237) > at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:189) > at org.apache.openejb.server.ejbd.EjbRequestHandler.doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:290) > at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:140) > at org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:267) > at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:191) > at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:81) > at org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:56) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.ClassNotFoundException: javax.faces.model.CollectionDataModel > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1714) > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559) > at org.apache.tomee.catalina.LazyStopWebappClassLoader.loadClass(LazyStopWebappClassLoader.java:98) > ... 80 more > Jan 24, 2014 4:27:36 PM org.apache.myfaces.config.FacesConfigurator configureRenderKits > SEVERE: failed to configure class org.richfaces.ui.input.autocomplete.AutocompleteRenderer > javax.faces.FacesException: java.lang.NoClassDefFoundError: javax/faces/model/CollectionDataModel > at org.apache.myfaces.shared.util.ClassUtils.newInstance(ClassUtils.java:384) > at org.apache.myfaces.shared.util.ClassUtils.newInstance(ClassUtils.java:342) > at org.apache.myfaces.config.FacesConfigurator.configureRenderKits(FacesConfigurator.java:910) > at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:420) > at org.apache.myfaces.webapp.AbstractFacesInitializer.buildConfiguration(AbstractFacesInitializer.java:370) > at org.apache.myfaces.webapp.Jsp21FacesInitializer.initContainerIntegration(Jsp21FacesInitializer.java:73) > at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:143) > at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791) > at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) > at org.apache.tomee.catalina.TomcatWebAppBuilder.deployWar(TomcatWebAppBuilder.java:538) > at org.apache.tomee.catalina.TomcatWebAppBuilder.deployWebApps(TomcatWebAppBuilder.java:509) > at org.apache.tomee.catalina.deployment.TomcatWebappDeployer.deploy(TomcatWebappDeployer.java:44) > at org.apache.openejb.assembler.DeployerEjb.deploy(DeployerEjb.java:131) > at org.apache.openejb.assembler.DeployerEjb.deploy(DeployerEjb.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.security.internal.InternalSecurityInterceptor.invoke(InternalSecurityInterceptor.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.cdi.CdiInterceptor.invoke(CdiInterceptor.java:128) > at org.apache.openejb.cdi.CdiInterceptor.access$000(CdiInterceptor.java:43) > at org.apache.openejb.cdi.CdiInterceptor$1.call(CdiInterceptor.java:64) > at org.apache.openejb.cdi.CdiInterceptor.aroundInvoke(CdiInterceptor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.monitoring.StatsInterceptor.record(StatsInterceptor.java:176) > at org.apache.openejb.monitoring.StatsInterceptor.invoke(StatsInterceptor.java:95) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:138) > at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:237) > at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:189) > at org.apache.openejb.server.ejbd.EjbRequestHandler.doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:290) > at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:140) > at org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:267) > at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:191) > at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:81) > at org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:56) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.NoClassDefFoundError: javax/faces/model/CollectionDataModel > at java.lang.Class.getDeclaredConstructors0(Native Method) > at java.lang.Class.privateGetDeclaredConstructors(Class.java:2493) > at java.lang.Class.getConstructor0(Class.java:2803) > at java.lang.Class.newInstance(Class.java:345) > at org.apache.myfaces.shared.util.ClassUtils.newInstance(ClassUtils.java:379) > ... 75 more > Caused by: java.lang.ClassNotFoundException: javax.faces.model.CollectionDataModel > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1714) > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559) > at org.apache.tomee.catalina.LazyStopWebappClassLoader.loadClass(LazyStopWebappClassLoader.java:98) > ... 80 more > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 05:33:26 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 05:33:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13513) CollectionDataModel API is not available on pre-JSF 2.1 that poses backward compatibility problem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13513. ---------------------------- Verified in RF 4.5, Closing. > CollectionDataModel API is not available on pre-JSF 2.1 that poses backward compatibility problem > ------------------------------------------------------------------------------------------------- > > Key: RF-13513 > URL: https://issues.jboss.org/browse/RF-13513 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 5.0.0.Alpha3 > Environment: 5.0.0-SNAPSHOT > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > > As we have introduced support for collections, leveraging JSF 2.2 CollectionDataModel, this might prevent some pre-JSF 2.2 containers to work correctly with component using UISeuqence or AutocompleteRendererBase. > This is an exception from TomEE 1.5.1 with MyFaces 2.1.10: > {code} > SEVERE: Class : org.richfaces.ui.input.autocomplete.AutocompleteRenderer not found. > java.lang.NoClassDefFoundError: javax/faces/model/CollectionDataModel > at java.lang.Class.getDeclaredConstructors0(Native Method) > at java.lang.Class.privateGetDeclaredConstructors(Class.java:2493) > at java.lang.Class.getConstructor0(Class.java:2803) > at java.lang.Class.newInstance(Class.java:345) > at org.apache.myfaces.shared.util.ClassUtils.newInstance(ClassUtils.java:379) > at org.apache.myfaces.shared.util.ClassUtils.newInstance(ClassUtils.java:342) > at org.apache.myfaces.config.FacesConfigurator.configureRenderKits(FacesConfigurator.java:910) > at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:420) > at org.apache.myfaces.webapp.AbstractFacesInitializer.buildConfiguration(AbstractFacesInitializer.java:370) > at org.apache.myfaces.webapp.Jsp21FacesInitializer.initContainerIntegration(Jsp21FacesInitializer.java:73) > at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:143) > at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791) > at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) > at org.apache.tomee.catalina.TomcatWebAppBuilder.deployWar(TomcatWebAppBuilder.java:538) > at org.apache.tomee.catalina.TomcatWebAppBuilder.deployWebApps(TomcatWebAppBuilder.java:509) > at org.apache.tomee.catalina.deployment.TomcatWebappDeployer.deploy(TomcatWebappDeployer.java:44) > at org.apache.openejb.assembler.DeployerEjb.deploy(DeployerEjb.java:131) > at org.apache.openejb.assembler.DeployerEjb.deploy(DeployerEjb.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.security.internal.InternalSecurityInterceptor.invoke(InternalSecurityInterceptor.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.cdi.CdiInterceptor.invoke(CdiInterceptor.java:128) > at org.apache.openejb.cdi.CdiInterceptor.access$000(CdiInterceptor.java:43) > at org.apache.openejb.cdi.CdiInterceptor$1.call(CdiInterceptor.java:64) > at org.apache.openejb.cdi.CdiInterceptor.aroundInvoke(CdiInterceptor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.monitoring.StatsInterceptor.record(StatsInterceptor.java:176) > at org.apache.openejb.monitoring.StatsInterceptor.invoke(StatsInterceptor.java:95) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:138) > at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:237) > at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:189) > at org.apache.openejb.server.ejbd.EjbRequestHandler.doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:290) > at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:140) > at org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:267) > at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:191) > at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:81) > at org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:56) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.ClassNotFoundException: javax.faces.model.CollectionDataModel > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1714) > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559) > at org.apache.tomee.catalina.LazyStopWebappClassLoader.loadClass(LazyStopWebappClassLoader.java:98) > ... 80 more > Jan 24, 2014 4:27:36 PM org.apache.myfaces.config.FacesConfigurator configureRenderKits > SEVERE: failed to configure class org.richfaces.ui.input.autocomplete.AutocompleteRenderer > javax.faces.FacesException: java.lang.NoClassDefFoundError: javax/faces/model/CollectionDataModel > at org.apache.myfaces.shared.util.ClassUtils.newInstance(ClassUtils.java:384) > at org.apache.myfaces.shared.util.ClassUtils.newInstance(ClassUtils.java:342) > at org.apache.myfaces.config.FacesConfigurator.configureRenderKits(FacesConfigurator.java:910) > at org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.java:420) > at org.apache.myfaces.webapp.AbstractFacesInitializer.buildConfiguration(AbstractFacesInitializer.java:370) > at org.apache.myfaces.webapp.Jsp21FacesInitializer.initContainerIntegration(Jsp21FacesInitializer.java:73) > at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:143) > at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791) > at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) > at org.apache.tomee.catalina.TomcatWebAppBuilder.deployWar(TomcatWebAppBuilder.java:538) > at org.apache.tomee.catalina.TomcatWebAppBuilder.deployWebApps(TomcatWebAppBuilder.java:509) > at org.apache.tomee.catalina.deployment.TomcatWebappDeployer.deploy(TomcatWebappDeployer.java:44) > at org.apache.openejb.assembler.DeployerEjb.deploy(DeployerEjb.java:131) > at org.apache.openejb.assembler.DeployerEjb.deploy(DeployerEjb.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.security.internal.InternalSecurityInterceptor.invoke(InternalSecurityInterceptor.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.cdi.CdiInterceptor.invoke(CdiInterceptor.java:128) > at org.apache.openejb.cdi.CdiInterceptor.access$000(CdiInterceptor.java:43) > at org.apache.openejb.cdi.CdiInterceptor$1.call(CdiInterceptor.java:64) > at org.apache.openejb.cdi.CdiInterceptor.aroundInvoke(CdiInterceptor.java:70) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.monitoring.StatsInterceptor.record(StatsInterceptor.java:176) > at org.apache.openejb.monitoring.StatsInterceptor.invoke(StatsInterceptor.java:95) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext$Invocation.invoke(ReflectionInvocationContext.java:181) > at org.apache.openejb.core.interceptor.ReflectionInvocationContext.proceed(ReflectionInvocationContext.java:163) > at org.apache.openejb.core.interceptor.InterceptorStack.invoke(InterceptorStack.java:138) > at org.apache.openejb.core.stateless.StatelessContainer._invoke(StatelessContainer.java:237) > at org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:189) > at org.apache.openejb.server.ejbd.EjbRequestHandler.doEjbObject_BUSINESS_METHOD(EjbRequestHandler.java:290) > at org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:140) > at org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:267) > at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:191) > at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:81) > at org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:56) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.NoClassDefFoundError: javax/faces/model/CollectionDataModel > at java.lang.Class.getDeclaredConstructors0(Native Method) > at java.lang.Class.privateGetDeclaredConstructors(Class.java:2493) > at java.lang.Class.getConstructor0(Class.java:2803) > at java.lang.Class.newInstance(Class.java:345) > at org.apache.myfaces.shared.util.ClassUtils.newInstance(ClassUtils.java:379) > ... 75 more > Caused by: java.lang.ClassNotFoundException: javax.faces.model.CollectionDataModel > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1714) > at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1559) > at org.apache.tomee.catalina.LazyStopWebappClassLoader.loadClass(LazyStopWebappClassLoader.java:98) > ... 80 more > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 05:37:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 05:37:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13498) Photoalbum - shutting down server with deployed app will throw JdbcSQLException: In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13498: ----------------------------- Fix Version/s: 4.5.0.Alpha3 > Photoalbum - shutting down server with deployed app will throw JdbcSQLException: > -------------------------------------------------------------------------------- > > Key: RF-13498 > URL: https://issues.jboss.org/browse/RF-13498 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 5.0.0.Alpha2 > Environment: JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Trivial > Labels: 45x, photoalbum > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > > Shutting down AS with deployed photoalbum.war will result in throwing following exception: > {code} > 15:40:12,568 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-161] > at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) > at org.h2.message.DbException.get(DbException.java:169) > at org.h2.message.DbException.get(DbException.java:146) > at org.h2.message.DbException.get(DbException.java:135) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1394) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1369) > at org.h2.jdbc.JdbcConnection.setAutoCommit(JdbcConnection.java:407) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.checkTransaction(BaseWrapperManagedConnection.java:817) > at org.jboss.jca.adapters.jdbc.WrappedConnection.checkTransaction(WrappedConnection.java:1589) > at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:298) > at org.hibernate.tool.hbm2ddl.DatabaseExporter.(DatabaseExporter.java:54) > at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:368) > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:319) > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:315) > at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:1279) > at org.hibernate.ejb.EntityManagerFactoryImpl.close(EntityManagerFactoryImpl.java:140) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.stop(PersistenceUnitServiceImpl.java:98) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] > {code} > As suggested by the exception message, it can be easily fixed by adding {{;DB_CLOSE_ON_EXIT=FALSE}} to the connection url. > This issue is similar to the RF-12102, which was resolved with same fix. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 05:39:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 05:39:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13498) Photoalbum - shutting down server with deployed app will throw JdbcSQLException: In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13498. ---------------------------- Verified with Photoalbum 4.5, closing. > Photoalbum - shutting down server with deployed app will throw JdbcSQLException: > -------------------------------------------------------------------------------- > > Key: RF-13498 > URL: https://issues.jboss.org/browse/RF-13498 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 5.0.0.Alpha2 > Environment: JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Trivial > Labels: 45x, photoalbum > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > > Shutting down AS with deployed photoalbum.war will result in throwing following exception: > {code} > 15:40:12,568 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] HHH000231: Schema export unsuccessful: org.h2.jdbc.JdbcSQLException: Database is already closed (to disable automatic closing at VM shutdown, add ";DB_CLOSE_ON_EXIT=FALSE" to the db URL) [90121-161] > at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) > at org.h2.message.DbException.get(DbException.java:169) > at org.h2.message.DbException.get(DbException.java:146) > at org.h2.message.DbException.get(DbException.java:135) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1394) > at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1369) > at org.h2.jdbc.JdbcConnection.setAutoCommit(JdbcConnection.java:407) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.checkTransaction(BaseWrapperManagedConnection.java:817) > at org.jboss.jca.adapters.jdbc.WrappedConnection.checkTransaction(WrappedConnection.java:1589) > at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:298) > at org.hibernate.tool.hbm2ddl.DatabaseExporter.(DatabaseExporter.java:54) > at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:368) > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:319) > at org.hibernate.tool.hbm2ddl.SchemaExport.drop(SchemaExport.java:315) > at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:1279) > at org.hibernate.ejb.EntityManagerFactoryImpl.close(EntityManagerFactoryImpl.java:140) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.stop(PersistenceUnitServiceImpl.java:98) [jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] > {code} > As suggested by the exception message, it can be easily fixed by adding {{;DB_CLOSE_ON_EXIT=FALSE}} to the connection url. > This issue is similar to the RF-12102, which was resolved with same fix. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 05:43:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 05:43:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside calendar is not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13361: ----------------------------- Fix Version/s: 4.5.0.Alpha3 > Placeholder inside calendar is not rendered > ------------------------------------------- > > Key: RF-13361 > URL: https://issues.jboss.org/browse/RF-13361 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Reporter: Pavol Pitonak > Assignee: Michal Petrov > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha2 > > Attachments: placeholder1.png > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky > # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky > result: > * in Showcase 4 calendar component has a placeholder text > * in Showcase 5 placeholder in calendar is missing, see screenshot -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 05:45:26 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 05:45:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13361) Placeholder inside calendar is not rendered In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13361. ---------------------------- Verified in 4.5 Showcase and Metamer, closing. > Placeholder inside calendar is not rendered > ------------------------------------------- > > Key: RF-13361 > URL: https://issues.jboss.org/browse/RF-13361 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Environment: RichFaces 5.0.0-SNAPSHOT > Reporter: Pavol Pitonak > Assignee: Michal Petrov > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha2 > > Attachments: placeholder1.png > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # open Showcase 5 http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky > # open Showcase 4 http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=placeholder&skin=blueSky > result: > * in Showcase 4 calendar component has a placeholder text > * in Showcase 5 placeholder in calendar is missing, see screenshot -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 06:39:26 2014 From: issues at jboss.org (Sebastian Cramer (JIRA)) Date: Wed, 18 Jun 2014 06:39:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11103) org.richfaces.skin = plain causes java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977307#comment-12977307 ] Sebastian Cramer commented on RF-11103: --------------------------------------- Hello. As far as I can tell this bug is still unfixed for 4.3.7.Final. The problem surfaces e.g. when using with skinning set to plain. I checked the sources and it seems the Skin#imageUrl() solution wasn't backported from 5.0.0.Alpha2 to RF4 head. I belive this issue needs to be reopened. What can be done to backport the solution? I tried to look at the attached changes but couldn't really make any sense of it. Seems to be a little confused. :-) Is it as simple as adding #imageUrl() to Skin/AbstractSkin and changing all background-image: references accordingly? Cheers S > org.richfaces.skin = plain causes java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 > ---------------------------------------------------------------------------------------------------------------- > > Key: RF-11103 > URL: https://issues.jboss.org/browse/RF-11103 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: skinning > Reporter: u j > Assignee: Brian Leathem > Priority: Minor > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I tried > {code} > > org.richfaces.skin > plain > > {code} > > and the skinning seems to be disabled, but I get > {code} > 14:44:21,584 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/myapp].[Faces Servlet]] Servlet.service() para servlet Faces Servlet lanz? excepci?n: java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 > at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:999) [:1.6.0_24] > at java.awt.image.BufferedImage.(BufferedImage.java:321) [:1.6.0_24] > at org.richfaces.resource.ImageType.createARGBImage(ImageType.java:103) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.access$200(ImageType.java:34) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType$2.createImage(ImageType.java:44) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.createImage(ImageType.java:118) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.paintAndWrite(Java2DUserResourceWrapperImpl.java:155) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.getInputStream(Java2DUserResourceWrapperImpl.java:65) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.CachedResourceImpl.initialize(CachedResourceImpl.java:178) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:171) [:4.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:407) [:2.1.1-FCS] > 14:45:38,493 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/myapp].[Faces Servlet]] Servlet.service() para servlet Faces Servlet lanz? excepci?n: java.lang.IllegalArgumentException: Width (1) and height (0) cannot be <= 0 > at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:999) [:1.6.0_24] > at java.awt.image.BufferedImage.(BufferedImage.java:321) [:1.6.0_24] > at org.richfaces.resource.ImageType.createARGBImage(ImageType.java:103) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.access$200(ImageType.java:34) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType$2.createImage(ImageType.java:44) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.createImage(ImageType.java:118) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.paintAndWrite(Java2DUserResourceWrapperImpl.java:155) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.getInputStream(Java2DUserResourceWrapperImpl.java:65) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.CachedResourceImpl.initialize(CachedResourceImpl.java:178) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:171) [:4.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:407) [:2.1.1-FCS] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] > {code} > I found a note > http://echelog.matzon.dk/logs/browse/richfaces/1306706400 > Thanks -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 07:25:24 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 18 Jun 2014 07:25:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13677) InputNumberSlider & Spinner render does not work when nested in iteration components In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977325#comment-12977325 ] Michal Petrov commented on RF-13677: ------------------------------------ There seems to be an issue with ID resolution. * The id of the slider should be {{form:containerRichDataTable:2:slider}}, however it is just {{form:containerRichDataTable:slider}}. Don't know if it affects the issue. * During ApplyRequestValuesPhase the output is found on the first row (it is processed despite rendered="false", but that is intended) and so the resolved id is wrong. > InputNumberSlider & Spinner render does not work when nested in iteration components > ------------------------------------------------------------------------------------ > > Key: RF-13677 > URL: https://issues.jboss.org/browse/RF-13677 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > > When {{inputNumberSlider}} or {{inputNumberSpinner}} is nested in either of these iteration components: > * uiRepeat > * a4jRepeat > * richExtendedDataTable > * richCollapsibleSubTable > * richDataGrid > * richDataTable > then the property of the bean bound to its {{value}} attribute is not updated by ajax request. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 07:45:24 2014 From: issues at jboss.org (J W (JIRA)) Date: Wed, 18 Jun 2014 07:45:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12936) Use jQuery in non-conflicting way In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977332#comment-12977332 ] J W commented on RF-12936: -------------------------- I just updated to the latest RF version(4.3.7). Now i have a conflict with Prototype and richfaces.js @ Line: 137 https://github.com/richfaces4/core/blob/master/impl/src/main/resources/META-INF/resources/richfaces.js#L137 Shouldn't all the "$" be gone after the issues got fixed? > Use jQuery in non-conflicting way > --------------------------------- > > Key: RF-12936 > URL: https://issues.jboss.org/browse/RF-12936 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The {{richfaces.js}} references both, {{jQuery}} from closure and global {{$}} - this issue is addressed in RF-12833. > However jQuery should not be used directly, rather from closures - prefered way is to use {{$}} but its naming now conflicts with {{RichFaces.$}} for component references. > I suggest to use following trick: > {code:title=richfaces.js} > window.RichFaces = window.RichFaces || {}; > RichFaces.jQuery = RichFaces.jQuery || window.jQuery; > //encapsulation > (function($, rf) { > // free to use $ here > }(RichFaces.jQuery, RichFaces)); > {code} > It will allow: > * provide own jQuery for RichFaces (using _jQuery.noConflict()_) > * use libraries which make use of {{$}} (prototype, other jQuery versions) in no-conflicting way -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 07:47:24 2014 From: issues at jboss.org (J W (JIRA)) Date: Wed, 18 Jun 2014 07:47:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12936) Use jQuery in non-conflicting way In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977332#comment-12977332 ] J W edited comment on RF-12936 at 6/18/14 7:47 AM: --------------------------------------------------- I just updated to the latest RF version(4.3.7). Now i have a conflict with Prototype and richfaces.js @ Line: 137 https://github.com/richfaces4/core/blob/master/impl/src/main/resources/META-INF/resources/richfaces.js#L137 Shouldn't all the "$" be gone after the issues got fixed? EDIT: Nevermind, i assumed it got fixed in 4.3, while this issues states it will be fixed in 4.5 was (Author: jigg4): I just updated to the latest RF version(4.3.7). Now i have a conflict with Prototype and richfaces.js @ Line: 137 https://github.com/richfaces4/core/blob/master/impl/src/main/resources/META-INF/resources/richfaces.js#L137 Shouldn't all the "$" be gone after the issues got fixed? > Use jQuery in non-conflicting way > --------------------------------- > > Key: RF-12936 > URL: https://issues.jboss.org/browse/RF-12936 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The {{richfaces.js}} references both, {{jQuery}} from closure and global {{$}} - this issue is addressed in RF-12833. > However jQuery should not be used directly, rather from closures - prefered way is to use {{$}} but its naming now conflicts with {{RichFaces.$}} for component references. > I suggest to use following trick: > {code:title=richfaces.js} > window.RichFaces = window.RichFaces || {}; > RichFaces.jQuery = RichFaces.jQuery || window.jQuery; > //encapsulation > (function($, rf) { > // free to use $ here > }(RichFaces.jQuery, RichFaces)); > {code} > It will allow: > * provide own jQuery for RichFaces (using _jQuery.noConflict()_) > * use libraries which make use of {{$}} (prototype, other jQuery versions) in no-conflicting way -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 09:23:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 09:23:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13680) Editor JS API method blur does not work after upgrade of CKEditor In-Reply-To: References: Message-ID: Juraj H?ska created RF-13680: -------------------------------- Summary: Editor JS API method blur does not work after upgrade of CKEditor Key: RF-13680 URL: https://issues.jboss.org/browse/RF-13680 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.5.0.Alpha3 Reporter: Juraj H?ska When executing JS function: {code} RichFaces.component('editorComponentClientId').blur(); {code} Following error is thrown: {code} this.ckeditor.focusManager.forceBlur is not a function {code} It is probably caused by CKEditor upgrade in [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 09:23:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 09:23:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13680) Editor JS API method blur does not work after upgrade of CKEditor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13680: ----------------------------- Labels: regression (was: ) > Editor JS API method blur does not work after upgrade of CKEditor > ----------------------------------------------------------------- > > Key: RF-13680 > URL: https://issues.jboss.org/browse/RF-13680 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > When executing JS function: > {code} > RichFaces.component('editorComponentClientId').blur(); > {code} > Following error is thrown: > {code} > this.ckeditor.focusManager.forceBlur is not a function > {code} > It is probably caused by CKEditor upgrade in [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 09:33:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 09:33:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13680) Editor JS API method blur does not work after upgrade of CKEditor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977374#comment-12977374 ] Juraj H?ska commented on RF-13680: ---------------------------------- In CKEditor 3.x , there was a {{forceBlur}} method. Documentation [here|http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.focusManager.html]. In CKEditor 4.x there is only {{blur(noDelay)}} function, which should be used instead. Documentation [here|http://docs.ckeditor.com/#!/api/CKEDITOR.focusManager] > Editor JS API method blur does not work after upgrade of CKEditor > ----------------------------------------------------------------- > > Key: RF-13680 > URL: https://issues.jboss.org/browse/RF-13680 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > > When executing JS function: > {code} > RichFaces.component('editorComponentClientId').blur(); > {code} > Following error is thrown: > {code} > this.ckeditor.focusManager.forceBlur is not a function > {code} > It is probably caused by CKEditor upgrade in [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 09:33:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 09:33:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) Add support for a 'header' meta-component to the rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977375#comment-12977375 ] Ji?? ?tefek commented on RF-13278: ---------------------------------- It seems that this issue was not resolved in 5.0.0.Alpha3. The provided test do not pass with: 5.0.0.Alpha3, 5.0.0-SNAPSHOT, 4.5.0-SNAPSHOT. Tried on AS 7.1 (for 5.0.0.Alpha3), EAP 6.3 (for actual 5 and 4.5 snapshots and 5.0.0.Alpha3) Steps: # build and deploy metamer # load http://localhost:8080/metamer/faces/components/richTabPanel/rf-13278.xhtml # click the "click me" link in tab1 content # the tab2 header *is* updated with ajax to "1 clicks" (correct) # switch to second tab # the header of the second tab is changed back to its *initial state* "0 clicks" * If you refresh the page, the tab header will be updated. * if you switch back to tab1, the header will be updated to "1 clicks", but if you then switch again to tab2 the header will be back at "0 clicks" [~bleathem], is this a correct/ecpected behaviour of the tab panel? Or is the sample somehow wrong? (the test, bean, sample can be easily accessed from [this comment|https://issues.jboss.org/browse/RF-13278?focusedCommentId=12825431&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12825431]) > Add support for a 'header' meta-component to the rich:tabPanel > -------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 09:43:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 09:43:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13237) Showcase: enable debugging tools (ui:debug, r:log) when in development mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13237: ----------------------------- Fix Version/s: 4.5.0.Alpha3 > Showcase: enable debugging tools (ui:debug, r:log) when in development mode > --------------------------------------------------------------------------- > > Key: RF-13237 > URL: https://issues.jboss.org/browse/RF-13237 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 09:51:25 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 18 Jun 2014 09:51:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13237) Showcase: enable debugging tools (ui:debug, r:log) when in development mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek reopened RF-13237: ------------------------------ Reopening. Please apply this patch also to 4.5.x branch and to 4.3 Showcase? > Showcase: enable debugging tools (ui:debug, r:log) when in development mode > --------------------------------------------------------------------------- > > Key: RF-13237 > URL: https://issues.jboss.org/browse/RF-13237 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 10:03:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 10:03:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) Add support for a 'header' meta-component to the rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977399#comment-12977399 ] Juraj H?ska commented on RF-13278: ---------------------------------- My guess is that the behavior changed after the EPVC refactoring ? [~jstefek] have you have chance to test it without EPVC refactoring ? > Add support for a 'header' meta-component to the rich:tabPanel > -------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 10:09:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 18 Jun 2014 10:09:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13680) Editor JS API method blur does not work after upgrade of CKEditor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13680: ----------------------------- Priority: Minor (was: Major) > Editor JS API method blur does not work after upgrade of CKEditor > ----------------------------------------------------------------- > > Key: RF-13680 > URL: https://issues.jboss.org/browse/RF-13680 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Priority: Minor > Labels: regression > > When executing JS function: > {code} > RichFaces.component('editorComponentClientId').blur(); > {code} > Following error is thrown: > {code} > this.ckeditor.focusManager.forceBlur is not a function > {code} > It is probably caused by CKEditor upgrade in [this|https://github.com/richfaces/richfaces/commit/4c8ac2c970692ac96fde0ef3f505a1b7fbda3d29] commit. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 11:17:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 11:17:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11103) org.richfaces.skin = plain causes java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977449#comment-12977449 ] Brian Leathem commented on RF-11103: ------------------------------------ The backport to the RichFaces 4.x branch is tracked in issue RF-13673. > org.richfaces.skin = plain causes java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 > ---------------------------------------------------------------------------------------------------------------- > > Key: RF-11103 > URL: https://issues.jboss.org/browse/RF-11103 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: skinning > Reporter: u j > Assignee: Brian Leathem > Priority: Minor > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I tried > {code} > > org.richfaces.skin > plain > > {code} > > and the skinning seems to be disabled, but I get > {code} > 14:44:21,584 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/myapp].[Faces Servlet]] Servlet.service() para servlet Faces Servlet lanz? excepci?n: java.lang.IllegalArgumentException: Width (2000) and height (0) cannot be <= 0 > at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:999) [:1.6.0_24] > at java.awt.image.BufferedImage.(BufferedImage.java:321) [:1.6.0_24] > at org.richfaces.resource.ImageType.createARGBImage(ImageType.java:103) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.access$200(ImageType.java:34) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType$2.createImage(ImageType.java:44) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.createImage(ImageType.java:118) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.paintAndWrite(Java2DUserResourceWrapperImpl.java:155) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.getInputStream(Java2DUserResourceWrapperImpl.java:65) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.CachedResourceImpl.initialize(CachedResourceImpl.java:178) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:171) [:4.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:407) [:2.1.1-FCS] > 14:45:38,493 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/myapp].[Faces Servlet]] Servlet.service() para servlet Faces Servlet lanz? excepci?n: java.lang.IllegalArgumentException: Width (1) and height (0) cannot be <= 0 > at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:999) [:1.6.0_24] > at java.awt.image.BufferedImage.(BufferedImage.java:321) [:1.6.0_24] > at org.richfaces.resource.ImageType.createARGBImage(ImageType.java:103) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.access$200(ImageType.java:34) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType$2.createImage(ImageType.java:44) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ImageType.createImage(ImageType.java:118) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.paintAndWrite(Java2DUserResourceWrapperImpl.java:155) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.Java2DUserResourceWrapperImpl.getInputStream(Java2DUserResourceWrapperImpl.java:65) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.CachedResourceImpl.initialize(CachedResourceImpl.java:178) [:4.0.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:171) [:4.0.0-SNAPSHOT] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:407) [:2.1.1-FCS] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] > {code} > I found a note > http://echelog.matzon.dk/logs/browse/richfaces/1306706400 > Thanks -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 11:19:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 11:19:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13237) Showcase: enable debugging tools (ui:debug, r:log) when in development mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13237: ------------------------------- Fix Version/s: (was: 4.5.0.Alpha3) > Showcase: enable debugging tools (ui:debug, r:log) when in development mode > --------------------------------------------------------------------------- > > Key: RF-13237 > URL: https://issues.jboss.org/browse/RF-13237 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: 45x > Fix For: 5.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 11:19:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 11:19:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13237) Showcase: enable debugging tools (ui:debug, r:log) when in development mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13237. -------------------------------- Resolution: Done > Showcase: enable debugging tools (ui:debug, r:log) when in development mode > --------------------------------------------------------------------------- > > Key: RF-13237 > URL: https://issues.jboss.org/browse/RF-13237 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: 45x > Fix For: 5.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 11:21:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 11:21:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13237) Showcase: enable debugging tools (ui:debug, r:log) when in development mode In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977453#comment-12977453 ] Brian Leathem commented on RF-13237: ------------------------------------ [~jstefek] since this issue was resolved in an already released version, would you please file a new issue requesting a backport, rather than re-opening the issue? We end up messing with finalized release notes when we re-open issues for already released versions. > Showcase: enable debugging tools (ui:debug, r:log) when in development mode > --------------------------------------------------------------------------- > > Key: RF-13237 > URL: https://issues.jboss.org/browse/RF-13237 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Labels: 45x > Fix For: 5.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 11:23:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 11:23:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13278) Add support for a 'header' meta-component to the rich:tabPanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977457#comment-12977457 ] Brian Leathem commented on RF-13278: ------------------------------------ The new EPVC will not work on AS 7.1. And it will only work on EAP 6.3.ER7. The latest 4.5 branch will throw an error in the server log if you use it with too old a Mojarra. > Add support for a 'header' meta-component to the rich:tabPanel > -------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Labels: 45x > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > > > > > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 11:27:27 2014 From: issues at jboss.org (Sebastian Cramer (JIRA)) Date: Wed, 18 Jun 2014 11:27:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13673) Backport the plain skin fix from RF 5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977461#comment-12977461 ] Sebastian Cramer commented on RF-13673: --------------------------------------- Hello. I would be willing to do the backporting. I only need a short pointer on what to do: Is it enough to implement the imageUrl() method on Skin/AbstractSkin and go through all eccs files and replace the urls? Or is there any more work needed? Cheers S > Backport the plain skin fix from RF 5 > ------------------------------------- > > Key: RF-13673 > URL: https://issues.jboss.org/browse/RF-13673 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: skinning > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > Backport RF-11103. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 11:27:27 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 11:27:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13678) Render @all does not work for nested a4j:region in collapsibleSubTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13678: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Render @all does not work for nested a4j:region in collapsibleSubTable > ---------------------------------------------------------------------- > > Key: RF-13678 > URL: https://issues.jboss.org/browse/RF-13678 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > > Suppose nested {{regions}} in a {{collapsibleSubTable}}. > Those regions are not updated when a {{commandButton}} with {{render}} attribute set to {{@all}} is submitted. > IMHO it is somehow connected with RF-13677, however, this issue occurs only with combination of {{regions}} and {{collapsibleSubTable}}, other iteration components works in this matter. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 11:27:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 11:27:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13679) PickList is missing styleClass attribute In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13679: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > PickList is missing styleClass attribute > ---------------------------------------- > > Key: RF-13679 > URL: https://issues.jboss.org/browse/RF-13679 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > > {{PickList}} is missing {{styleClass}} attribute. > It can not be found in generated {{faces-config.xml}}, in: {{richfaces-4.5.0-SNAPSHOT.jar/META-INF/faces-config.xml}}. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 11:45:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 11:45:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13673) Backport the plain skin fix from RF 5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977470#comment-12977470 ] Brian Leathem commented on RF-13673: ------------------------------------ Backporting the issue involves cherry-picking the following commits: {code} commit 46b03d226ae420bcbc8abd7f79ed5790f2bb6dc4 Author: Brian Leathem Date: Thu Sep 12 16:40:55 2013 -0700 RF-11103: Converted all background-image CSS properties in .ecss files to use the skin.imageUrl method commit 21a41993bd30d64688c2cf11b667af1edc42c3fe Author: Brian Leathem Date: Thu Sep 12 16:34:39 2013 -0700 RF-11103: Implemented a skin method to return the image URL, and none for the plain skin commit 3d58e36885890d3e0a1b51fe6d2e6af13bbd5028 Author: Brian Leathem Date: Tue Sep 10 19:28:37 2013 -0700 RF-11103: Implemented an integration test for richfaces skinning {code} However, the cherry-pick is not quite straightforward, as some of the paths have changed, and so some of the changes will have to be applied manually. > Backport the plain skin fix from RF 5 > ------------------------------------- > > Key: RF-13673 > URL: https://issues.jboss.org/browse/RF-13673 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: skinning > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > Backport RF-11103. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 12:45:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 12:45:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13661) De-couple the RichFaces.BaseComponent implementation from its JSF backend In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975475#comment-12975475 ] Brian Leathem edited comment on RF-13661 at 6/18/14 12:44 PM: -------------------------------------------------------------- I created a branch [RF-13661-standalone-js|https://github.com/richfaces/richfaces/tree/RF-13661-standalone-js] where I added a examples/standalone-js example that can be use to create standalone html pages for various RF components. The jsf pages are stored in the {{jsf}} webapp folder, and the corresponding standalone html page is stored in the {{html}} folder. Note: the standalone html page is created by deploying the webapp, and viewing a component page in a browser. The html source of the component page is saved as an html file. Path changes are made to the html file to use the js resources of the components directly from the source tree. ---- Merging of this branch is pending discussion at the upcoming f2f meeting. was (Author: bleathem): I created a branch [RF-13661-independent-js|https://github.com/richfaces/richfaces/tree/RF-13661-independent-js] where I added a examples/standalone-js example that can be use to create standalone html pages for various RF components. The jsf pages are stored in the {{jsf}} webapp folder, and the corresponding standalone html page is stored in the {{html}} folder. Note: the standalone html page is created by deploying the webapp, and viewing a component page in a browser. The html source of the component page is saved as an html file. Path changes are made to the html file to use the js resources of the components directly from the source tree. ---- Merging of this branch is pending discussion at the upcoming f2f meeting. > De-couple the RichFaces.BaseComponent implementation from its JSF backend > ------------------------------------------------------------------------- > > Key: RF-13661 > URL: https://issues.jboss.org/browse/RF-13661 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5-Tracking > > > Investigate whether we can de-couple a {{RichFaces.BaseComponent}} based component from the JSF back-end. The ExtendedDataTable implementation would be a good candidate for this PoC. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 13:59:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 13:59:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13640. -------------------------------- Resolution: Done Thanks guys, I had tested with {{}} child elements, not tables/rows. Turns out the mouseenter event is fired on the {{}} element, rather than the {{}} element. I've updated the mouseenter listener to lookup the parent item element and tested the showcase sample on Chrome. Please continue with QA for this issue. > Autocomplete with custom layout: cant select item by mouse > ---------------------------------------------------------- > > Key: RF-13640 > URL: https://issues.jboss.org/browse/RF-13640 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6, 4.5.0.Alpha3 > Environment: Firefox 29.0.1 > Chrome 35.0.1916.114 > Reporter: liumin hu > Assignee: Brian Leathem > Labels: needs-backport, needs-qe, regression > Fix For: 4.3.8, 4.5.0.Alpha3 > > > When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected. > This bug was not observable before 4.3.6.Final. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 14:29:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 18 Jun 2014 14:29:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13660) RichFaces 4.5 integration tests - error after test execution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977522#comment-12977522 ] Brian Leathem commented on RF-13660: ------------------------------------ It seems the {{InitializationListener#onStop}} method is called twice. > RichFaces 4.5 integration tests - error after test execution > ------------------------------------------------------------ > > Key: RF-13660 > URL: https://issues.jboss.org/browse/RF-13660 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Environment: AS: Wildfly > Browser: PhantomJS > Reporter: Matej Novotny > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > This issue originated from RF-13591. > There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/src/test/integration/org/richfaces/integration/resource/ITResourceMapping.java]. > The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines. > Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5/56/console]. > The exception in server console is: > {code} > 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException > at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:] > at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:] > at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:] > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] > at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:] > at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 18 17:45:28 2014 From: issues at jboss.org (Val Blant (JIRA)) Date: Wed, 18 Jun 2014 17:45:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13674) a4j:push broken on WebLogic 12c in Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Val Blant updated RF-13674: --------------------------- Summary: a4j:push broken on WebLogic 12c in Chrome (was: a4j:push broken on WebLogic 12c) Description: works properly on Tomcat 7, but fails on WebLogic 12c in Chrome (Firefox works fine). {code:title=Page.xhtml|borderStyle=solid} stuff here {code} {code:title=Java Code} TopicKey topicKey = new TopicKey("systemLinks"); TopicsContext topicsContext = TopicsContext.lookup(); topicsContext.publish(topicKey, "fly, you fools!"); {code} On Tomcat 7 this work perfectly, and always refreshes '_systemLinksPanel_' when data is published. On Weblogic 12c the data is not flushed correctly. If you use Wireshark, you'd see the following response coming back from the server: {panel:title=Tomcat 7} 3b <"topic":"systemLinks","data":"fly, you fools!","number":0> 0 {panel} {panel:title=Weblogic 12c} 003b <"topic":"systemLinks","data":"fly, you fools!","number":0> {panel} *Note the missing zero terminator line in the WebLogic response!* I narrowed down the problem to the following: {code:title=org.richfaces.application.push.impl.RequestImpl} public synchronized void onBroadcast(AtmosphereResourceEvent event) { MessageDataScriptString serializedMessages = (MessageDataScriptString) event.getMessage(); getSession().clearBroadcastedMessages(serializedMessages.getLastSequenceNumber()); hasActiveBroadcaster = false; if (isPolling()) { event.getResource().resume(); // <= THIS LINE } else { postMessages(); } } {code} There is nothing wrong with this in principle, but it does not work due to a bug in Atmosphere 0.8.4. Calling _AtmosphereResource.resume()_ at this point seems reasonable, since it is supposed to properly finish/commit the _HttpServletResponse_. However, this does not work on WebLogic 12c and leads to incorrectly flushed data demonstrated above. The underlying problem seems to be the fact that _AtmosphereResource.resume()_ method interrupts the thread which flushed the socket Writer before a call to _asyncContext.complete()_ is made: {code} public AtmosphereResource resume() { .... if (!b.isDestroyed()) { b.removeAtmosphereResource(event.getResource()); } .... asyncSupport.action(this); // <= This is where asyncContext.complete() is called } {code} I have verified that calling _asyncContext.complete()_ before we clean up Atmosphere resources fixes the problem. Here's the fix, which needs to go into _RequestImpl.onBroadcast_: {code:title=org.richfaces.application.push.impl.RequestImpl} public synchronized void onBroadcast(AtmosphereResourceEvent event) { .............. if (isPolling()) { // This is the workaround. Completing AsyncContext before cleaning up Atmosphere resources // seems to make this work everywhere. // AsyncContext asyncContext = (AsyncContext) event .getResource() .getRequest() .getAttribute("org.atmosphere.container.asyncContext"); if ( asyncContext != null ) { asyncContext.complete(); } event.getResource().resume(); } else { postMessages(); } } .............. {code} I am attaching a very simple WAR file that demonstrates the problem clearly. The demo app does not use Richfaces, b/c I wanted to remove all unnecessary complexity. Instead I created a couple of simple classes that mimic the behavior of _org.richfaces.webapp.PushHandlerFilter_ and _org.richfaces.application.push.impl.RequestImpl_. In the demo app, _MeteorRequest = RequestImpl_, which is where the fix needs to go. Please note that according to the Atmosphere author, this problem is fixed in 2.1 branch. Here's the discussion: https://groups.google.com/forum/#!topic/atmosphere-framework/KCKlSmbMrRo Now, the reason why only Chrome is effected has to do with processing of chunked responses by the XMLHttpRequest. Unlike other browsers, Chrome is not capable of handling improperly terminated chunked responses. So: {noformat} HTTP/1.1 200 OK Cache-Control: no-store, no-cache, must-revalidate Date: Wed, 18 Jun 2014 05:37:55 GMT Pragma: no-cache Transfer-Encoding: chunked <<--- THIS IS IMPORTANT Content-Type: text/plain Expires: -1 Access-Control-Allow-Credentials: true Access-Control-Allow-Origin: * X-Powered-By: Servlet/3.0 JSP/2.2 0841 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > opensymphony > oscache > ${version.oscache} > > > org.jboss.cache > jbosscache-core > ${version.jbosscache} > > > net.sf.ehcache > ehcache > ${version.ehcache} > > > > {code} > Since only the cache-dependencies are managed, we could rename the BOM to {{richfaces-cache-bom}}. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 06:00:35 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 25 Jun 2014 06:00:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13608) Apply appropriate package and artifact names to the component poms In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13608. ------------------------------ Verified, closing. > Apply appropriate package and artifact names to the component poms > ------------------------------------------------------------------ > > Key: RF-13608 > URL: https://issues.jboss.org/browse/RF-13608 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The current package {{org.richfaces.compat}} is inappropriate for the RichFaces 4.5 release. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 06:06:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 06:06:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13694) Update README files for RichFaces 4.5.x In-Reply-To: References: Message-ID: Juraj H?ska created RF-13694: -------------------------------- Summary: Update README files for RichFaces 4.5.x Key: RF-13694 URL: https://issues.jboss.org/browse/RF-13694 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.5.0.Alpha3 Reporter: Juraj H?ska Priority: Minor {{README.md}} and {{dist/src/main/resources/txt/readme.txt}} need to be updated with RichFaces 4.5.x. For {{README.md}} e.g.: * change of the title to RichFaces 4.5 * remove "New approach to styling based on LESS" * alter "Smooth Migration from RF4 to RF5" and other -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 06:06:25 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 25 Jun 2014 06:06:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13663) Warp on Chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13663. ------------------------------ Verified, closing. > Warp on Chrome > -------------- > > Key: RF-13663 > URL: https://issues.jboss.org/browse/RF-13663 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Environment: Chrome > Wildfly 8.0 > Reporter: Matej Novotny > Assignee: Matej Novotny > > This issue originates from RF-13651. > RF 4.5 integration tests (I tried it with a4j tests) fail when there is a @Warp test using @BeforePhase JSF hooks. > The problem is that the Phase does not get executed. However this only happens with Chrome, FF and PhantomJS work corectly. > This is the exception: > {code} > testExecuteForm(org.richfaces.component.region.ITExecuteRichAjax) Time elapsed: 11.187 sec <<< ERROR! > org.jboss.arquillian.warp.impl.client.verification.InspectionMethodWasNotInvokedException: Lifecycle test declared on public void org.richfaces.component.region.VerifyExecutedIds.validaExecutedIds(javax.faces.context.FacesContext) with qualifiers [@org.jboss.arquillian.warp.jsf.BeforePhase(value=RENDER_RESPONSE)] was not executed > at org.jboss.arquillian.warp.impl.client.verification.ResponsePayloadVerifier.verifyAllLifecycleTestsExecuted(ResponsePayloadVerifier.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultResponseDeenrichmentService.deenrichResponse(DefaultResponseDeenrichmentService.java:87) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.deenrichResponse(EnrichmentObserver.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.EnrichmentObserver.tryDeenrichResponse(EnrichmentObserver.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.warp.impl.client.execution.DefaultHttpFiltersSource$1.responsePost(DefaultHttpFiltersSource.java:102) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.warp.impl.client.context.operation.Contextualizer$2.invoke(Contextualizer.java:68) > at com.sun.proxy.$Proxy27.responsePost(Unknown Source) > at org.littleshoot.proxy.impl.ClientToProxyConnection.respond(ClientToProxyConnection.java:316) > at org.littleshoot.proxy.impl.ProxyToServerConnection.respondWith(ProxyToServerConnection.java:440) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:182) > at org.littleshoot.proxy.impl.ProxyToServerConnection.readHTTPInitial(ProxyToServerConnection.java:66) > at org.littleshoot.proxy.impl.ProxyConnection.readHTTP(ProxyConnection.java:143) > at org.littleshoot.proxy.impl.ProxyConnection.read(ProxyConnection.java:130) > at org.littleshoot.proxy.impl.ProxyToServerConnection.read(ProxyToServerConnection.java:173) > at org.littleshoot.proxy.impl.ProxyConnection.channelRead0(ProxyConnection.java:563) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:253) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$ResponseReadMonitor.channelRead(ProxyConnection.java:714) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:153) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) > at org.littleshoot.proxy.impl.ProxyConnection$BytesReadMonitor.channelRead(ProxyConnection.java:668) > at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:338) > at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:324) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:126) > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:485) > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:452) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:346) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) > at java.lang.Thread.run(Thread.java:724) > {code} > What I tried: > * I downloaded Arq. warp repo and tried integration tests there (there is a test for JSF lifecycle hooks) > ** This test works, so I suppose warp works correctly > * I tried to change dependencies to other version to see whether it would work > ** No luck, fails all the time -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 06:06:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 06:06:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13653) Update component namespaces in 4.5 examples In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979190#comment-12979190 ] Juraj H?ska commented on RF-13653: ---------------------------------- Created RF-13694 for the README files as there are more changes required. > Update component namespaces in 4.5 examples > ------------------------------------------- > > Key: RF-13653 > URL: https://issues.jboss.org/browse/RF-13653 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > With the exception of showcase, all examples use the r namespace, it needs to be changed back to a4j/rich. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 06:08:24 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 25 Jun 2014 06:08:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13591) RichFaces 4.5 integration tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13591. ------------------------------ Integration tests (Smoke tests) are passing in PhantomJS. Other browsers are being addressed in different issues. Closing this issue. > RichFaces 4.5 integration tests are failing > ------------------------------------------- > > Key: RF-13591 > URL: https://issues.jboss.org/browse/RF-13591 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Luk?? Fry? > Priority: Blocker > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > RichFaces 4.5 cannot be build because of compilation errors in integration tests: > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on project richfaces: Compilation failure: Compilation failure: > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[9,30] error: cannot find symbol > [ERROR] package org.richfaces.ui.toggle > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[10,39] error: package org.richfaces.ui.toggle.tabPanel does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[18,12] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[19,27] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[21,28] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[25,11] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[29,35] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/tabPanel/model/TabPanelItemChangeEventBean.java:[33,16] error: cannot find symbol > [ERROR] class TabPanelItemChangeEventBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusDefaults.java:[48,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcing.java:[38,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcingOverridesFocusSettings.java:[31,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcingOverridesFocusSettings.java:[32,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusCandidates.java:[34,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusCandidates.java:[35,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[31,26] error: cannot find symbol > [ERROR] package org.richfaces.model > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[44,12] error: cannot find symbol > [ERROR] class IterationBuiltInBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[45,12] error: cannot find symbol > [ERROR] class IterationBuiltInBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[57,11] error: cannot find symbol > [ERROR] class IterationBuiltInBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[61,11] error: cannot find symbol > [ERROR] class IterationBuiltInBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationBuiltInBean.java:[65,29] error: cannot find symbol > [ERROR] class IterationBuiltInBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusSubmissionMethods.java:[50,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[31,26] error: cannot find symbol > [ERROR] package org.richfaces.model > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[49,12] error: cannot find symbol > [ERROR] class IterationTableStateBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[50,12] error: cannot find symbol > [ERROR] class IterationTableStateBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[85,11] error: cannot find symbol > [ERROR] class IterationTableStateBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[89,11] error: cannot find symbol > [ERROR] class IterationTableStateBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/IterationTableStateBean.java:[93,29] error: cannot find symbol > [ERROR] class IterationTableStateBean > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusValidationAware.java:[56,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusValidationAware.java:[57,34] error: package org.richfaces.ui.misc.focus does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[63,51] error: package org.richfaces.ui.iteration.extendedDataTable does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[64,51] error: package org.richfaces.ui.iteration.extendedDataTable does not exist > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusDefaults.java:[100,16] error: cannot find symbol > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcing.java:[62,19] error: cannot find symbol > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcingOverridesFocusSettings.java:[49,8] error: cannot find symbol > [ERROR] class VerifyFocusEnforcingOverridesFocusSettings > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusEnforcingOverridesFocusSettings.java:[50,8] error: cannot find symbol > [ERROR] > [ERROR] E extends HtmlElement declared in method getElementById(String) > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusCandidates.java:[77,8] error: cannot find symbol > [ERROR] class VerifyFocusCandidates > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/VerifyFocusCandidates.java:[78,8] error: cannot find symbol > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusValidationAware.java:[153,16] error: cannot find symbol > [ERROR] class AbstractFocus > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/focus/ITFocusValidationAware.java:[154,16] error: cannot find symbol > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[136,16] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[136,55] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[140,16] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[140,58] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[141,16] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[141,56] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[187,20] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[187,62] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[188,20] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[188,60] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[228,20] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[228,62] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[229,20] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[229,60] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[268,16] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[268,58] error: cannot find symbol > [ERROR] class AbstractExtendedDataTable > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[269,16] error: cannot find symbol > [ERROR] class ExtendedDataTableState > [ERROR] /mnt/hudson_workspace/workspace/richfaces-4.5/framework/src/test/integration/org/richfaces/ui/extendedDataTable/ITTableState.java:[269,56] error: cannot find symbol > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 06:10:27 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 25 Jun 2014 06:10:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13334) Upgrade jQuery UI to 1.10.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13334. ---------------------------- Verified, closing. > Upgrade jQuery UI to 1.10.3 > --------------------------- > > Key: RF-13334 > URL: https://issues.jboss.org/browse/RF-13334 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha2 > Reporter: Luk?? Fry? > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > RichWidgets issue: > https://github.com/richwidgets/richwidgets/issues/99 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 06:30:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 25 Jun 2014 06:30:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13160) Refactor the InputNumber* components into abstract classes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13160. ---------------------------- Verified in 4.5, closing. > Refactor the InputNumber* components into abstract classes > ---------------------------------------------------------- > > Key: RF-13160 > URL: https://issues.jboss.org/browse/RF-13160 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3, 5.0.0.Alpha2 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > The InputNumberSpinner and InputNumberSlider components are generated via xml in a faces-config.xml file. While this is clever, it means we have two components that are created differently from all the others, making them harder to manage. Additionally the xml is not conducive to refactoring, and the method relies on an xml format for shared attribute definitions, making it difficult to move forward with RF-12952. > I propose re-implementing those components as Abstract components, like the majority of other RichFaces CDK components. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 07:09:24 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 25 Jun 2014 07:09:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13620) Port the RichFaces 5 re-write of xml attribute to interfaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13620. ------------------------------ Verified, closing issue. > Port the RichFaces 5 re-write of xml attribute to interfaces > ------------------------------------------------------------ > > Key: RF-13620 > URL: https://issues.jboss.org/browse/RF-13620 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > In RichFaces 5 we re-wrote the xml attribute definitions as Interfaces to support type safety. This issue addresses backporting that fix to RichFaces 4.5. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 07:27:26 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 25 Jun 2014 07:27:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13641) Upgrade CSSParser to 0.9.14 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13641. ------------------------------ Verified, CSSParser is updated. > Upgrade CSSParser to 0.9.14 > --------------------------- > > Key: RF-13641 > URL: https://issues.jboss.org/browse/RF-13641 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Assignee: Brian Leathem > Labels: 30m > Fix For: 4.5.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 07:57:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 07:57:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13650) ITResourceOptimization tests fail - no resource aggregation applied In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13650. ---------------------------- Verified. Closing. > ITResourceOptimization tests fail - no resource aggregation applied > ------------------------------------------------------------------- > > Key: RF-13650 > URL: https://issues.jboss.org/browse/RF-13650 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.5.0.Alpha3 > Reporter: Luk?? Fry? > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > {code} > TResourceOptimization.test_script_packaging:104 expected:<1> but was:<0> > ITResourceOptimization.test_stylesheet_packaging:113 expected:<1> but was:<0> > {code} > Originally revealed by RF-13591 > These are smoke tests ,we should address them in 4.5.0.Alpha3. > ---- > Here is the source of the page generated by {{test_script_packaging}}: > {code} > > > > > > > > > {code} > As you can see, there is {{richfaces.js}} in the head section, but actual aggregated resource (like ({{core.js}}) is expected. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 07:57:24 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 25 Jun 2014 07:57:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13597) Drag and drop support for file upload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979219#comment-12979219 ] Michal Petrov commented on RF-13597: ------------------------------------ Dropping files onto the add button is not the intended use. The add button contains the , some browsers allow dropping the files directly onto the input element, some do not. I don't think that functionality can be changed. Extending the dropzone might interfere with this, I'll look into it. > Drag and drop support for file upload > ------------------------------------- > > Key: RF-13597 > URL: https://issues.jboss.org/browse/RF-13597 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.1.0.Final > Reporter: abhishek vijra > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Drag/Drop support should be added to file upload component . > Like the primefaces fileUploadDnd : http://www.primefaces.org/showcase/ui/fileUploadDnd.jsf -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 08:57:24 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 25 Jun 2014 08:57:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13514) Support file upload progress tracking in Servlets >= 3.0 environment In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13514. ------------------------------ Verified, closing issue. > Support file upload progress tracking in Servlets >= 3.0 environment > -------------------------------------------------------------------- > > Key: RF-13514 > URL: https://issues.jboss.org/browse/RF-13514 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input, core > Affects Versions: 5.0.0.Alpha3 > Reporter: Luk?? Fry? > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > We currently support two approaches for file upload: > * Servlets 2.5: own request form data parser [{{MultipartRequestParser}}|https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/request/MultipartRequestParser.java] > * Servlets 3.0: leveraging {{HttpServletRequest#getParts()}} > However as we have discussed RF-13444, we had to finally do a trade-off of limiting support of file progress tracking. I.e. in Servlets 3.0 we have no simple way how to track file upload progress since getParts() returns data for completed request. > There are several possible outcomes: > 1) drop server-side file upload progress tracking and leverage XHR2/HTML5 that has built-in ability to track progress > * imho we are already prepared to switch to XHR2 and client-side progress (possibly leveraging some third-party widget) since [all major browsers support it at least one version back|http://caniuse.com/#feat=xhr2] > * existing implementation: http://www.script-tutorials.com/pure-html5-file-upload/ > 2) use a {{ServletFilter}} to wrap a request as our {{FileUploadFacesContextFactory}} currently do and so have an earlier access to the request object > * this principle has a drawback - we have to ensure our filter has high-enough priority so the servlet container won't touch the request body yet -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 09:35:25 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 25 Jun 2014 09:35:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11741) ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek reopened RF-11741: ------------------------------ Assignee: Brian Leathem [~bleathem], I have added a reproducer to Metamer. I used the same ecss as in decription: {code} .shadow { -webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; -moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; } {code} At the end (accessible from browser) the css looked like this: {code} *.shadow { -webkit-box-shadow: 4px 4px 5px "#ECF4FE"; -moz-box-shadow: 4px 4px 5px "#ECF4FE"; box-shadow: 4px 4px 5px "#ECF4FE"; } {code} In the result, this ecss file will not work because of the inserted {{""}} to the css file. Is there any way how to prevent inserting of these quotation marks? Verified in 4.5 Metamer on FF 30, Chrome 35 and on EAP 6.3.0.ER8. ----- Just to verify, I have also tried to hardcode the same values without the quotation marks in the ecss, like this: {code} .shadow{ -webkit-box-shadow: 40px 40px 50px #ECF4FE; -moz-box-shadow: 40px 40px 50px #ECF4FE; box-shadow: 40px 40px 50px #ECF4FE; } {code} The panel had the shadow and the final css was: {code} *.shadow { -webkit-box-shadow: 40px 40px 50px rgb(236, 244, 254); -moz-box-shadow: 40px 40px 50px rgb(236, 244, 254); box-shadow: 40px 40px 50px rgb(236, 244, 254); } {code} The Metamer sample is accessible from http://localhost:8080/metamer/faces/components/skinning/rf-11741.xhtml. If this cannot be fixed, please resolve and close this issue. > ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely > ------------------------------------------------------------------------------------------------------ > > Key: RF-11741 > URL: https://issues.jboss.org/browse/RF-11741 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: skinning > Affects Versions: 4.1.0.CR1 > Reporter: Karsten Wutzke > Assignee: Brian Leathem > Labels: ecss, parsing, skinning > Fix For: 4.5.0.Alpha3 > > > When defining rules like > {code} > .shadow > { > -webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; > -moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; > box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; > } > {code} > in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule entirely and no shadows will be rendered. BTW it would be better to just omit the invalid properties instead of the entire selector (box-shadow: ... alone works). > Most browsers don't support the box-shadow yet, so defining proprietary properties *must* be possible. Note, this applies to a lot more properties than the above. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 09:47:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 09:47:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13649) TogglePanel: fails to render meta-component '@header' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13649. ---------------------------- Verified. Closing. > TogglePanel: fails to render meta-component '@header' > ----------------------------------------------------- > > Key: RF-13649 > URL: https://issues.jboss.org/browse/RF-13649 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.5.0.Alpha3 > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The issue is here: [{{header != activeItem}}|https://github.com/richfaces/richfaces/blob/0733e3d0d76ca7dfbe66e2a85f225284a1650e07/components/rich/src/main/java/org/richfaces/renderkit/html/TogglePanelRenderer.java#L179] > Server stack trace: > {code} > 09:31:06,859 SEVERE [org.richfaces.log.Context] (default task-12) header: java.lang.IllegalArgumentException: header > at org.richfaces.renderkit.html.TogglePanelRenderer.encodeMetaComponent(TogglePanelRenderer.java:192) [richfaces.jar:4.5.0-SNAPSHOT] > at org.richfaces.component.AbstractTogglePanel.encodeMetaComponent(AbstractTogglePanel.java:891) [richfaces.jar:4.5.0-SNAPSHOT] > at org.richfaces.context.MetaComponentEncodingVisitCallback.visit(MetaComponentEncodingVisitCallback.java:69) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:103) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.context.ExtendedRenderVisitContext.invokeVisitCallback(ExtendedRenderVisitContext.java:65) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.context.ExtendedVisitContext.invokeMetaComponentVisitCallback(ExtendedVisitContext.java:76) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.component.AbstractTabPanel.visitMetaComponents(AbstractTabPanel.java:150) [richfaces.jar:4.5.0-SNAPSHOT] > at org.richfaces.component.AbstractTogglePanel.visitTree(AbstractTogglePanel.java:915) [richfaces.jar:4.5.0-SNAPSHOT] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at javax.faces.component.UIComponent.visitTree(UIComponent.java:1700) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.context.PartialViewContextImpl.processComponents(PartialViewContextImpl.java:406) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.context.PartialViewContextImpl.processPartial(PartialViewContextImpl.java:325) [jsf-impl-2.2.5-jbossorg-3.jar:] > at org.richfaces.context.ExtendedPartialViewContext.processPartial(ExtendedPartialViewContext.java:254) [richfaces-core-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:1004) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1856) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:435) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:133) [jsf-impl-2.2.5-jbossorg-3.jar:] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:337) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219) [jsf-impl-2.2.5-jbossorg-3.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:647) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > {code} > The issue is reproducible by [ITStaticTab|https://github.com/richfaces/richfaces/blob/0733e3d0d76ca7dfbe66e2a85f225284a1650e07/components/rich/src/test/integration/org/richfaces/component/tabPanel/ITStaticTab.java#L174] test -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 09:51:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 09:51:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13646) Fix resource optimization In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13646. ---------------------------- Verified. Closing. > Fix resource optimization > ------------------------- > > Key: RF-13646 > URL: https://issues.jboss.org/browse/RF-13646 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > # There are some resource files that are not being generated (e.g. gradientA.png). It's either a generation or optimization issue. > # -The optimization settings need to be updated, core files are currently not being packed (legacy of RF 4.5/RF 5 source collision avoidance)- -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 09:57:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 09:57:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13638) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13638: ----------------------------- Labels: needs (was: ) > Upgrade CKEditor to 4.3 > ----------------------- > > Key: RF-13638 > URL: https://issues.jboss.org/browse/RF-13638 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: barbara b > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 09:57:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 09:57:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13638) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13638: ----------------------------- Labels: (was: needs) > Upgrade CKEditor to 4.3 > ----------------------- > > Key: RF-13638 > URL: https://issues.jboss.org/browse/RF-13638 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: barbara b > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 09:59:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jun 2014 09:59:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13583) Backport the chart components to RichFaces 4.5 components module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979274#comment-12979274 ] Brian Leathem commented on RF-13583: ------------------------------------ [~manovotn] the PR has already been merged. Can you link to the branch you are looking at? > Backport the chart components to RichFaces 4.5 components module > ---------------------------------------------------------------- > > Key: RF-13583 > URL: https://issues.jboss.org/browse/RF-13583 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Backport the chart components to RichFaces 4.5 components module -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 09:59:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 09:59:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13638) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979275#comment-12979275 ] Juraj H?ska commented on RF-13638: ---------------------------------- Verified for 4.5.0.Alpha3 [~bleathem] do we want _needs-backport_ on this issue to backport it to 4.3.x ? > Upgrade CKEditor to 4.3 > ----------------------- > > Key: RF-13638 > URL: https://issues.jboss.org/browse/RF-13638 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: barbara b > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 10:05:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 10:05:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13634) Consolidate deployment classes for integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13634. ---------------------------- Verified. Closing. > Consolidate deployment classes for integration tests > ---------------------------------------------------- > > Key: RF-13634 > URL: https://issues.jboss.org/browse/RF-13634 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 10:07:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 10:07:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13632) RF 4.5 - refactor Javascript namespaces In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13632. ---------------------------- Verified. Closing. > RF 4.5 - refactor Javascript namespaces > --------------------------------------- > > Key: RF-13632 > URL: https://issues.jboss.org/browse/RF-13632 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha2 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Component scripts were using {{rf.rf4.ui}} namespace to avoid collision. This can be changed back to {{rf.ui}}. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 10:09:27 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 10:09:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13631) Remove the components/dist module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13631. ---------------------------- Verified. Closing. > Remove the components/dist module > --------------------------------- > > Key: RF-13631 > URL: https://issues.jboss.org/browse/RF-13631 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The components-dist module appears to be redundant now that we have ported the RF 5 frameowrk to RF 4.5.: > https://github.com/richfaces/richfaces/tree/4.5.x/components/dist > I propose we removed this dist module altogether. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 10:15:29 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 25 Jun 2014 10:15:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13583) Backport the chart components to RichFaces 4.5 components module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979289#comment-12979289 ] Matej Novotny commented on RF-13583: ------------------------------------ Yea, [this|https://github.com/richfaces/richfaces/tree/RF-13583-charts] is the branch. Now I can see it was merged but there was a commit 2 days ago which modifies the chart.js file. This commit allows to use public JS API. And this change is not included in 4.5.x yet. I am not sure whether this was intentionally commited into this branch and some more work is to be done, or whether we can add this commit do 4.5.x. > Backport the chart components to RichFaces 4.5 components module > ---------------------------------------------------------------- > > Key: RF-13583 > URL: https://issues.jboss.org/browse/RF-13583 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Backport the chart components to RichFaces 4.5 components module -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 10:17:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jun 2014 10:17:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13583) Backport the chart components to RichFaces 4.5 components module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979292#comment-12979292 ] Brian Leathem commented on RF-13583: ------------------------------------ [~lukindo] can you comment on the status of this commit? > Backport the chart components to RichFaces 4.5 components module > ---------------------------------------------------------------- > > Key: RF-13583 > URL: https://issues.jboss.org/browse/RF-13583 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Backport the chart components to RichFaces 4.5 components module -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 10:28:24 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 25 Jun 2014 10:28:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13637) Refresh the dist zip for RF 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny closed RF-13637. ------------------------------ Verified, closing issue. > Refresh the dist zip for RF 4.5 > ------------------------------- > > Key: RF-13637 > URL: https://issues.jboss.org/browse/RF-13637 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 days > Time Spent: 1 day > Remaining Estimate: 1 day > > The distribution zip for RichFaces 4.5 needs to be refreshed to account for the module and repository changes. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 10:52:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 10:52:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13630) RichFaces 4.5.x can not be built due to cyclic maven dependency In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13630. ---------------------------- Verified. Closing. > RichFaces 4.5.x can not be built due to cyclic maven dependency > --------------------------------------------------------------- > > Key: RF-13630 > URL: https://issues.jboss.org/browse/RF-13630 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Building of https://github.com/richfaces/richfaces/tree/4.5.x is not possible. > There is a cyclic maven dependency: > {code} > [ERROR] The projects in the reactor contain a cyclic reference: Edge between 'Vertex{label='org.richfaces:richfaces-resource-optimizer-maven-plugin:4.5.0-SNAPSHOT'}' and 'Vertex{label='org.richfaces:richfaces:4.5.0-SNAPSHOT'}' introduces to cycle in the graph org.richfaces:richfaces:4.5.0-SNAPSHOT --> org.richfaces:richfaces-resource-optimizer-maven-plugin:4.5.0-SNAPSHOT --> org.richfaces:richfaces:4.5.0-SNAPSHOT -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 11:16:27 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 25 Jun 2014 11:16:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11741) ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11741: ------------------------------- Fix Version/s: 4.5-Tracking (was: 4.5.0.Alpha3) > ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely > ------------------------------------------------------------------------------------------------------ > > Key: RF-11741 > URL: https://issues.jboss.org/browse/RF-11741 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: skinning > Affects Versions: 4.1.0.CR1 > Reporter: Karsten Wutzke > Assignee: Brian Leathem > Labels: ecss, parsing, skinning > Fix For: 4.5-Tracking > > > When defining rules like > {code} > .shadow > { > -webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; > -moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; > box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; > } > {code} > in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule entirely and no shadows will be rendered. BTW it would be better to just omit the invalid properties instead of the entire selector (box-shadow: ... alone works). > Most browsers don't support the box-shadow yet, so defining proprietary properties *must* be possible. Note, this applies to a lot more properties than the above. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 11:59:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 11:59:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13627) Refactor the RF 4.5 components to make use of the type-safe handlerClass attribute In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13627. ---------------------------- Verified. Closing. > Refactor the RF 4.5 components to make use of the type-safe handlerClass attribute > ---------------------------------------------------------------------------------- > > Key: RF-13627 > URL: https://issues.jboss.org/browse/RF-13627 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > RF-12957 introduced the handlerClass attribute in the RichFaces CDK. RichFaces 5 components were ported to use this new attribute. The RichFaces 4.5 components should also use these attributes. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 12:01:27 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 12:01:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13623) Merge components/pom with components/parent/pom in 4.5.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13623. ---------------------------- Verified. Closing. > Merge components/pom with components/parent/pom in 4.5.x > -------------------------------------------------------- > > Key: RF-13623 > URL: https://issues.jboss.org/browse/RF-13623 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > components/pom.xml doesn't contain any useful information so it should be merged with components/parent/pom.xml. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 12:03:27 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 12:03:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13583) Backport the chart components to RichFaces 4.5 components module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska reopened RF-13583: ------------------------------ The public API [~manovotn] is talking about was added by Lukas Macko into this branch: https://github.com/richfaces/richfaces/commits/RF-13583-charts It need to be merged with 4.5.x. Reopening. > Backport the chart components to RichFaces 4.5 components module > ---------------------------------------------------------------- > > Key: RF-13583 > URL: https://issues.jboss.org/browse/RF-13583 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Backport the chart components to RichFaces 4.5 components module -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 12:11:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 12:11:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13507) Backport RF-13317 (EPVCI should specify correct ViewState) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13507. ---------------------------- Verified. Closing. > Backport RF-13317 (EPVCI should specify correct ViewState) > ---------------------------------------------------------- > > Key: RF-13507 > URL: https://issues.jboss.org/browse/RF-13507 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.4 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Let's let RF-13317 stabilize in 5.x first. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 12:11:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 25 Jun 2014 12:11:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13505. ---------------------------- Verified. Closing. > Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactory (blocked by Mojarra issue) > ----------------------------------------------------------------------------------------------------------------- > > Key: RF-13505 > URL: https://issues.jboss.org/browse/RF-13505 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > Attachments: fu-request.png > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 > We will still need to use some: > * resolve values in runtime > * add IDs for execution of AjaxOutput's > * collect list of meta-components to render > * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 18:27:24 2014 From: issues at jboss.org (Frank Langelage (JIRA)) Date: Wed, 25 Jun 2014 18:27:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13685) ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979458#comment-12979458 ] Frank Langelage commented on RF-13685: -------------------------------------- Using current 4.5.0-SNAPSHOT build problem is solved. Application works as before. But using 5.0.0-SNAPSHOT problem is still present. A fix of this problem in this branch is also required. > ExtendedPartialViewContext.release causes IllegalStateException > --------------------------------------------------------------- > > Key: RF-13685 > URL: https://issues.jboss.org/browse/RF-13685 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Frank Langelage > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > When using latest WildFly 9.0-SNAPSHOT including JSF 2.2.7 I get an exception immediately after login from my web-app which is using richfaces-5.0.0-SNAPSHOT. > According to Farah Juma this is an error in RichFaces which comes up now because of a fix in JSF: > "This is a bug in RichFaces that was introduced by this recent Mojarra fix: > https://java.net/jira/browse/JAVASERVERFACES-3203 > The RichFaces ExtendedPartialViewContext class just needs to be updated accordingly." > Stacktrace fragment: > {code} > Caused by: java.lang.IllegalStateException > at com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:705) [jsf-impl-2.2.7-jbossorg-1.jar:] > at com.sun.faces.context.FacesContextImpl.getAttributes(FacesContextImpl.java:237) [jsf-impl-2.2.7-jbossorg-1.jar:] > at org.richfaces.context.ExtendedPartialViewContext.setInstance(ExtendedPartialViewContext.java:55) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContext.release(ExtendedPartialViewContext.java:64) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContextImpl.release(ExtendedPartialViewContextImpl.java:473) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at com.sun.faces.context.FacesContextImpl.release(FacesContextImpl.java:591) [jsf-impl-2.2.7-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:665) [jboss-jsf-api_2.2_spec-2.2.7.jar:2.2.7] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Wed Jun 25 18:37:24 2014 From: issues at jboss.org (Frank Langelage (JIRA)) Date: Wed, 25 Jun 2014 18:37:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13641) Upgrade CSSParser to 0.9.14 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979459#comment-12979459 ] Frank Langelage commented on RF-13641: -------------------------------------- Update of CSSParser should be done in 5.x too. There we still have version 0.9.11. > Upgrade CSSParser to 0.9.14 > --------------------------- > > Key: RF-13641 > URL: https://issues.jboss.org/browse/RF-13641 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Assignee: Brian Leathem > Labels: 30m > Fix For: 4.5.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 02:28:24 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 26 Jun 2014 02:28:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13641) Upgrade CSSParser to 0.9.14 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979546#comment-12979546 ] Matej Novotny commented on RF-13641: ------------------------------------ Good point, I'll create new issue to track it separately. > Upgrade CSSParser to 0.9.14 > --------------------------- > > Key: RF-13641 > URL: https://issues.jboss.org/browse/RF-13641 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Assignee: Brian Leathem > Labels: 30m > Fix For: 4.5.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 02:30:39 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 26 Jun 2014 02:30:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13695) Upgrade CSSParser for RF 5.x In-Reply-To: References: Message-ID: Matej Novotny created RF-13695: ---------------------------------- Summary: Upgrade CSSParser for RF 5.x Key: RF-13695 URL: https://issues.jboss.org/browse/RF-13695 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: third-party Affects Versions: 5.0.0.Alpha4 Reporter: Matej Novotny Priority: Minor As suggested in RF-13641, we should update CSSParser in RF 5 as well. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 03:54:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 03:54:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13696) Port fix for ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: Juraj H?ska created RF-13696: -------------------------------- Summary: Port fix for ExtendedPartialViewContext.release causes IllegalStateException Key: RF-13696 URL: https://issues.jboss.org/browse/RF-13696 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 Reporter: Juraj H?ska Assignee: Brian Leathem Fix For: 4.5.0.Alpha3 When using latest WildFly 9.0-SNAPSHOT including JSF 2.2.7 I get an exception immediately after login from my web-app which is using richfaces-5.0.0-SNAPSHOT. According to Farah Juma this is an error in RichFaces which comes up now because of a fix in JSF: "This is a bug in RichFaces that was introduced by this recent Mojarra fix: https://java.net/jira/browse/JAVASERVERFACES-3203 The RichFaces ExtendedPartialViewContext class just needs to be updated accordingly." Stacktrace fragment: {code} Caused by: java.lang.IllegalStateException at com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:705) [jsf-impl-2.2.7-jbossorg-1.jar:] at com.sun.faces.context.FacesContextImpl.getAttributes(FacesContextImpl.java:237) [jsf-impl-2.2.7-jbossorg-1.jar:] at org.richfaces.context.ExtendedPartialViewContext.setInstance(ExtendedPartialViewContext.java:55) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContext.release(ExtendedPartialViewContext.java:64) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContextImpl.release(ExtendedPartialViewContextImpl.java:473) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] at com.sun.faces.context.FacesContextImpl.release(FacesContextImpl.java:591) [jsf-impl-2.2.7-jbossorg-1.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:665) [jboss-jsf-api_2.2_spec-2.2.7.jar:2.2.7] {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 03:56:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 03:56:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13696) Port fix for ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13696: ----------------------------- Assignee: (was: Brian Leathem) > Port fix for ExtendedPartialViewContext.release causes IllegalStateException > ---------------------------------------------------------------------------- > > Key: RF-13696 > URL: https://issues.jboss.org/browse/RF-13696 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > > When using latest WildFly 9.0-SNAPSHOT including JSF 2.2.7 I get an exception immediately after login from my web-app which is using richfaces-5.0.0-SNAPSHOT. > According to Farah Juma this is an error in RichFaces which comes up now because of a fix in JSF: > "This is a bug in RichFaces that was introduced by this recent Mojarra fix: > https://java.net/jira/browse/JAVASERVERFACES-3203 > The RichFaces ExtendedPartialViewContext class just needs to be updated accordingly." > Stacktrace fragment: > {code} > Caused by: java.lang.IllegalStateException > at com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:705) [jsf-impl-2.2.7-jbossorg-1.jar:] > at com.sun.faces.context.FacesContextImpl.getAttributes(FacesContextImpl.java:237) [jsf-impl-2.2.7-jbossorg-1.jar:] > at org.richfaces.context.ExtendedPartialViewContext.setInstance(ExtendedPartialViewContext.java:55) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContext.release(ExtendedPartialViewContext.java:64) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContextImpl.release(ExtendedPartialViewContextImpl.java:473) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at com.sun.faces.context.FacesContextImpl.release(FacesContextImpl.java:591) [jsf-impl-2.2.7-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:665) [jboss-jsf-api_2.2_spec-2.2.7.jar:2.2.7] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 03:56:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 03:56:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13696) Port fix for ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13696: ----------------------------- Fix Version/s: (was: 4.5.0.Alpha3) > Port fix for ExtendedPartialViewContext.release causes IllegalStateException > ---------------------------------------------------------------------------- > > Key: RF-13696 > URL: https://issues.jboss.org/browse/RF-13696 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Juraj H?ska > > When using latest WildFly 9.0-SNAPSHOT including JSF 2.2.7 I get an exception immediately after login from my web-app which is using richfaces-5.0.0-SNAPSHOT. > According to Farah Juma this is an error in RichFaces which comes up now because of a fix in JSF: > "This is a bug in RichFaces that was introduced by this recent Mojarra fix: > https://java.net/jira/browse/JAVASERVERFACES-3203 > The RichFaces ExtendedPartialViewContext class just needs to be updated accordingly." > Stacktrace fragment: > {code} > Caused by: java.lang.IllegalStateException > at com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:705) [jsf-impl-2.2.7-jbossorg-1.jar:] > at com.sun.faces.context.FacesContextImpl.getAttributes(FacesContextImpl.java:237) [jsf-impl-2.2.7-jbossorg-1.jar:] > at org.richfaces.context.ExtendedPartialViewContext.setInstance(ExtendedPartialViewContext.java:55) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContext.release(ExtendedPartialViewContext.java:64) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContextImpl.release(ExtendedPartialViewContextImpl.java:473) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at com.sun.faces.context.FacesContextImpl.release(FacesContextImpl.java:591) [jsf-impl-2.2.7-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:665) [jboss-jsf-api_2.2_spec-2.2.7.jar:2.2.7] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 03:56:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 03:56:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13696) Port fix for ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13696: ----------------------------- Description: (was: When using latest WildFly 9.0-SNAPSHOT including JSF 2.2.7 I get an exception immediately after login from my web-app which is using richfaces-5.0.0-SNAPSHOT. According to Farah Juma this is an error in RichFaces which comes up now because of a fix in JSF: "This is a bug in RichFaces that was introduced by this recent Mojarra fix: https://java.net/jira/browse/JAVASERVERFACES-3203 The RichFaces ExtendedPartialViewContext class just needs to be updated accordingly." Stacktrace fragment: {code} Caused by: java.lang.IllegalStateException at com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:705) [jsf-impl-2.2.7-jbossorg-1.jar:] at com.sun.faces.context.FacesContextImpl.getAttributes(FacesContextImpl.java:237) [jsf-impl-2.2.7-jbossorg-1.jar:] at org.richfaces.context.ExtendedPartialViewContext.setInstance(ExtendedPartialViewContext.java:55) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContext.release(ExtendedPartialViewContext.java:64) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] at org.richfaces.context.ExtendedPartialViewContextImpl.release(ExtendedPartialViewContextImpl.java:473) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] at com.sun.faces.context.FacesContextImpl.release(FacesContextImpl.java:591) [jsf-impl-2.2.7-jbossorg-1.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:665) [jboss-jsf-api_2.2_spec-2.2.7.jar:2.2.7] {code}) > Port fix for ExtendedPartialViewContext.release causes IllegalStateException > ---------------------------------------------------------------------------- > > Key: RF-13696 > URL: https://issues.jboss.org/browse/RF-13696 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Juraj H?ska > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 03:56:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 03:56:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13696) Port fix for ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13696: ----------------------------- Affects Version/s: (was: 4.5.0.Alpha3) > Port fix for ExtendedPartialViewContext.release causes IllegalStateException > ---------------------------------------------------------------------------- > > Key: RF-13696 > URL: https://issues.jboss.org/browse/RF-13696 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Juraj H?ska > > When using latest WildFly 9.0-SNAPSHOT including JSF 2.2.7 I get an exception immediately after login from my web-app which is using richfaces-5.0.0-SNAPSHOT. > According to Farah Juma this is an error in RichFaces which comes up now because of a fix in JSF: > "This is a bug in RichFaces that was introduced by this recent Mojarra fix: > https://java.net/jira/browse/JAVASERVERFACES-3203 > The RichFaces ExtendedPartialViewContext class just needs to be updated accordingly." > Stacktrace fragment: > {code} > Caused by: java.lang.IllegalStateException > at com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:705) [jsf-impl-2.2.7-jbossorg-1.jar:] > at com.sun.faces.context.FacesContextImpl.getAttributes(FacesContextImpl.java:237) [jsf-impl-2.2.7-jbossorg-1.jar:] > at org.richfaces.context.ExtendedPartialViewContext.setInstance(ExtendedPartialViewContext.java:55) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContext.release(ExtendedPartialViewContext.java:64) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContextImpl.release(ExtendedPartialViewContextImpl.java:473) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at com.sun.faces.context.FacesContextImpl.release(FacesContextImpl.java:591) [jsf-impl-2.2.7-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:665) [jboss-jsf-api_2.2_spec-2.2.7.jar:2.2.7] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 03:56:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 03:56:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13696) Port fix for ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13696: ----------------------------- Description: This issues was resolved in 4.5.0.Alpha3. Please consider porting of the fix to 5.x branch as well. > Port fix for ExtendedPartialViewContext.release causes IllegalStateException > ---------------------------------------------------------------------------- > > Key: RF-13696 > URL: https://issues.jboss.org/browse/RF-13696 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Juraj H?ska > > This issues was resolved in 4.5.0.Alpha3. Please consider porting of the fix to 5.x branch as well. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 03:56:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 03:56:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13696) Port fix for ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13696: ----------------------------- Issue Type: Task (was: Bug) > Port fix for ExtendedPartialViewContext.release causes IllegalStateException > ---------------------------------------------------------------------------- > > Key: RF-13696 > URL: https://issues.jboss.org/browse/RF-13696 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Juraj H?ska > > This issues was resolved in 4.5.0.Alpha3. Please consider porting of the fix to 5.x branch as well. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 03:58:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 03:58:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13696) Port fix for RF-13685 - ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13696: ----------------------------- Summary: Port fix for RF-13685 - ExtendedPartialViewContext.release causes IllegalStateException (was: Port fix for ExtendedPartialViewContext.release causes IllegalStateException) > Port fix for RF-13685 - ExtendedPartialViewContext.release causes IllegalStateException > --------------------------------------------------------------------------------------- > > Key: RF-13696 > URL: https://issues.jboss.org/browse/RF-13696 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Juraj H?ska > > This issues was resolved in 4.5.0.Alpha3. Please consider porting of the fix to 5.x branch as well. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 03:58:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 03:58:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13685) ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979571#comment-12979571 ] Juraj H?ska commented on RF-13685: ---------------------------------- Thanks [~lafr] for verification! I have created RF-13696 for porting this fix to 5.x branch. Verified. Closing. > ExtendedPartialViewContext.release causes IllegalStateException > --------------------------------------------------------------- > > Key: RF-13685 > URL: https://issues.jboss.org/browse/RF-13685 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Frank Langelage > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > When using latest WildFly 9.0-SNAPSHOT including JSF 2.2.7 I get an exception immediately after login from my web-app which is using richfaces-5.0.0-SNAPSHOT. > According to Farah Juma this is an error in RichFaces which comes up now because of a fix in JSF: > "This is a bug in RichFaces that was introduced by this recent Mojarra fix: > https://java.net/jira/browse/JAVASERVERFACES-3203 > The RichFaces ExtendedPartialViewContext class just needs to be updated accordingly." > Stacktrace fragment: > {code} > Caused by: java.lang.IllegalStateException > at com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:705) [jsf-impl-2.2.7-jbossorg-1.jar:] > at com.sun.faces.context.FacesContextImpl.getAttributes(FacesContextImpl.java:237) [jsf-impl-2.2.7-jbossorg-1.jar:] > at org.richfaces.context.ExtendedPartialViewContext.setInstance(ExtendedPartialViewContext.java:55) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContext.release(ExtendedPartialViewContext.java:64) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContextImpl.release(ExtendedPartialViewContextImpl.java:473) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at com.sun.faces.context.FacesContextImpl.release(FacesContextImpl.java:591) [jsf-impl-2.2.7-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:665) [jboss-jsf-api_2.2_spec-2.2.7.jar:2.2.7] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 03:58:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 03:58:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13685) ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13685. ---------------------------- > ExtendedPartialViewContext.release causes IllegalStateException > --------------------------------------------------------------- > > Key: RF-13685 > URL: https://issues.jboss.org/browse/RF-13685 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Frank Langelage > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > When using latest WildFly 9.0-SNAPSHOT including JSF 2.2.7 I get an exception immediately after login from my web-app which is using richfaces-5.0.0-SNAPSHOT. > According to Farah Juma this is an error in RichFaces which comes up now because of a fix in JSF: > "This is a bug in RichFaces that was introduced by this recent Mojarra fix: > https://java.net/jira/browse/JAVASERVERFACES-3203 > The RichFaces ExtendedPartialViewContext class just needs to be updated accordingly." > Stacktrace fragment: > {code} > Caused by: java.lang.IllegalStateException > at com.sun.faces.context.FacesContextImpl.assertNotReleased(FacesContextImpl.java:705) [jsf-impl-2.2.7-jbossorg-1.jar:] > at com.sun.faces.context.FacesContextImpl.getAttributes(FacesContextImpl.java:237) [jsf-impl-2.2.7-jbossorg-1.jar:] > at org.richfaces.context.ExtendedPartialViewContext.setInstance(ExtendedPartialViewContext.java:55) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContext.release(ExtendedPartialViewContext.java:64) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at org.richfaces.context.ExtendedPartialViewContextImpl.release(ExtendedPartialViewContextImpl.java:473) [richfaces-5.0.0-SNAPSHOT.jar:5.0.0-SNAPSHOT] > at com.sun.faces.context.FacesContextImpl.release(FacesContextImpl.java:591) [jsf-impl-2.2.7-jbossorg-1.jar:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:665) [jboss-jsf-api_2.2_spec-2.2.7.jar:2.2.7] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 04:48:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 26 Jun 2014 04:48:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13697) fileupload: maxFilesQuantity + multiple select: can upload more files than the limit In-Reply-To: References: Message-ID: Ji?? ?tefek created RF-13697: -------------------------------- Summary: fileupload: maxFilesQuantity + multiple select: can upload more files than the limit Key: RF-13697 URL: https://issues.jboss.org/browse/RF-13697 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 5.0.0.Alpha3, 4.5.0.Alpha2 Environment: EAP 6.3.0.ER8 Metamer Reporter: Ji?? ?tefek Can add more files than @maxFilesQuantity to upload when using multiselect after some files have been added before. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 04:48:25 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 26 Jun 2014 04:48:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13697) fileupload: maxFilesQuantity + multiple select: can upload more files than the limit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13697: ----------------------------- Environment: Tried on EAP 6.3.0.ER8, FF 30 (was: EAP 6.3.0.ER8 Metamer) > fileupload: maxFilesQuantity + multiple select: can upload more files than the limit > ------------------------------------------------------------------------------------ > > Key: RF-13697 > URL: https://issues.jboss.org/browse/RF-13697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: Tried on EAP 6.3.0.ER8, FF 30 > Reporter: Ji?? ?tefek > > Can add more files than @maxFilesQuantity to upload when using multiselect after some files have been added before. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 05:46:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 05:46:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13583) Backport the chart components to RichFaces 4.5 components module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979325#comment-12979325 ] Juraj H?ska edited comment on RF-13583 at 6/26/14 5:45 AM: ----------------------------------------------------------- The public API [~manovotn] is talking about was added by Lukas Macko into this branch: https://github.com/richfaces/richfaces/commits/RF-13583-charts It needs to be merged with 4.5.x. Reopening. was (Author: jhuska): The public API [~manovotn] is talking about was added by Lukas Macko into this branch: https://github.com/richfaces/richfaces/commits/RF-13583-charts It need to be merged with 4.5.x. Reopening. > Backport the chart components to RichFaces 4.5 components module > ---------------------------------------------------------------- > > Key: RF-13583 > URL: https://issues.jboss.org/browse/RF-13583 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Backport the chart components to RichFaces 4.5 components module -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 07:38:24 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 26 Jun 2014 07:38:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13698) RF 4.5 Chart title does not render In-Reply-To: References: Message-ID: Matej Novotny created RF-13698: ---------------------------------- Summary: RF 4.5 Chart title does not render Key: RF-13698 URL: https://issues.jboss.org/browse/RF-13698 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.5.0.Alpha3 Environment: Wildfly 8.0 FF/Chrome Reporter: Matej Novotny The title of the chart is not rendered above the chart. This affects all kinds of charts, eg. line, pie and bar. I created Metamer samples of charts for 4.5.x where this can be tested (not automatically until public JS API for charts will be available). This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 07:50:24 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 26 Jun 2014 07:50:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13699) RF 4.5 Chart attribute 'zoom' does not work In-Reply-To: References: Message-ID: Matej Novotny created RF-13699: ---------------------------------- Summary: RF 4.5 Chart attribute 'zoom' does not work Key: RF-13699 URL: https://issues.jboss.org/browse/RF-13699 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.5.0.Alpha3 Environment: Wildfly 8.0 Latest Chrome/FF Reporter: Matej Novotny The attribute 'zoom' does not work, setting it to true has no effect and user cannot zoom the chart. This attribute is only available for line chart. I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 07:52:24 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 26 Jun 2014 07:52:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13699) RF 4.5 Chart attribute 'zoom' does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny updated RF-13699: ------------------------------- Steps to Reproduce: * Start Wildfly 8.0 * Deploy Metamer for RF 4.5 * Go to [this|http://localhost:8080/metamer/faces/components/richChart/simpleLine.xhtml] page with line chart * Defaultly I set {{zoom=true}} so nothing you need to do * Try zooming some area in chart (click-move-release) ** Expected: as you drag mouse a rectangle is drawn and once released, marked area is zoomed ** Actual: nothing happens was: * Start Wildfly 8.0 * Deploy Metamer for RF 4.5 * Go to [this|http://localhost:8080/metamer/faces/components/richChart/simpleLine.xhtml] page with line chart * Defaultly I set {{zoom=true}} so nothing you need to do * Try zooming some area in chart (click-move-release) ** Expected: as you drag mouse a rectangle is drawn and once released, marked are is zoomed ** Actual: nothing happens > RF 4.5 Chart attribute 'zoom' does not work > ------------------------------------------- > > Key: RF-13699 > URL: https://issues.jboss.org/browse/RF-13699 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > Latest Chrome/FF > Reporter: Matej Novotny > > The attribute 'zoom' does not work, setting it to true has no effect and user cannot zoom the chart. This attribute is only available for line chart. > I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 07:54:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 07:54:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13700) Charts Mobile Showcase demo on tablets - bars are overlapping In-Reply-To: References: Message-ID: Juraj H?ska created RF-13700: -------------------------------- Summary: Charts Mobile Showcase demo on tablets - bars are overlapping Key: RF-13700 URL: https://issues.jboss.org/browse/RF-13700 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.5.0.Alpha3 Reporter: Juraj H?ska Bars in the showcase chart demo are overlapping. It is probably issue of responsiveness. It is reproducible on Mobile showcase demo, accessing on tablets. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:14:25 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 26 Jun 2014 08:14:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13701) RF 4.5 Bar chart plotClick malfunctioning In-Reply-To: References: Message-ID: Matej Novotny created RF-13701: ---------------------------------- Summary: RF 4.5 Bar chart plotClick malfunctioning Key: RF-13701 URL: https://issues.jboss.org/browse/RF-13701 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.5.0.Alpha3 Environment: Wildfly 8.0 Latest Chrome/FF Reporter: Matej Novotny When interacting with bar chart where {{onplotclick}} and {{plotClickListener}} are set, it does not react when last bar is clicked (no request is sent for server side event). See steps to reproduce. I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:16:29 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:16:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13700) Charts Mobile Showcase demo on tablets - bars are overlapping In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13700: ----------------------------- Attachment: barChartOverlapping.PNG > Charts Mobile Showcase demo on tablets - bars are overlapping > ------------------------------------------------------------- > > Key: RF-13700 > URL: https://issues.jboss.org/browse/RF-13700 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Attachments: barChartOverlapping.PNG > > > Bars in the showcase chart demo are overlapping. It is probably issue of responsiveness. It is reproducible on Mobile showcase demo, accessing on tablets. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:16:29 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 26 Jun 2014 08:16:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13701) RF 4.5 Bar chart plotClick malfunctioning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny updated RF-13701: ------------------------------- Description: When interacting with bar chart where {{onplotclick}} and {{plotClickListener}} are set, it does not react when last bar in the series is clicked (eg .no request is sent for server side event and no JS executed for onplotclick). See steps to reproduce, in case they are not clear ask me for more details. I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. was: When interacting with bar chart where {{onplotclick}} and {{plotClickListener}} are set, it does not react when last bar is clicked (no request is sent for server side event). See steps to reproduce. I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. > RF 4.5 Bar chart plotClick malfunctioning > ----------------------------------------- > > Key: RF-13701 > URL: https://issues.jboss.org/browse/RF-13701 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > Latest Chrome/FF > Reporter: Matej Novotny > > When interacting with bar chart where {{onplotclick}} and {{plotClickListener}} are set, it does not react when last bar in the series is clicked (eg .no request is sent for server side event and no JS executed for onplotclick). See steps to reproduce, in case they are not clear ask me for more details. > I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:22:25 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 26 Jun 2014 08:22:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13583) Backport the chart components to RichFaces 4.5 components module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979655#comment-12979655 ] Matej Novotny commented on RF-13583: ------------------------------------ I created three new issues with charts and linked them to this one. They were all working in RF 5 (I verified that) so I suppose it was caused by backporting. > Backport the chart components to RichFaces 4.5 components module > ---------------------------------------------------------------- > > Key: RF-13583 > URL: https://issues.jboss.org/browse/RF-13583 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Backport the chart components to RichFaces 4.5 components module -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:26:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:26:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13702) Charts Mobile Showcase - initial rendering is broken and with JS errors In-Reply-To: References: Message-ID: Juraj H?ska created RF-13702: -------------------------------- Summary: Charts Mobile Showcase - initial rendering is broken and with JS errors Key: RF-13702 URL: https://issues.jboss.org/browse/RF-13702 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output, mobile Affects Versions: 4.5.0.Alpha3 Reporter: Juraj H?ska When the charts demo from Showcase is initially loaded on mobile device (tested on tablet), then there are JS errors, and the output is broken. After full refresh of the page it is rendered correctly. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:28:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:28:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13702) Charts Mobile Showcase - initial rendering is broken and with JS errors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13702: ----------------------------- Attachment: chartRenderingError.PNG > Charts Mobile Showcase - initial rendering is broken and with JS errors > ----------------------------------------------------------------------- > > Key: RF-13702 > URL: https://issues.jboss.org/browse/RF-13702 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, mobile > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Attachments: chartRenderingError.PNG > > > When the charts demo from Showcase is initially loaded on mobile device (tested on tablet), then there are JS errors, and the output is broken. > After full refresh of the page it is rendered correctly. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:45:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:45:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13702) Charts Mobile Showcase - initial rendering is broken and with JS errors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13702: ----------------------------- Affects Version/s: 5.0.0.Alpha3 > Charts Mobile Showcase - initial rendering is broken and with JS errors > ----------------------------------------------------------------------- > > Key: RF-13702 > URL: https://issues.jboss.org/browse/RF-13702 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, mobile > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Attachments: chartRenderingError.PNG > > > When the charts demo from Showcase is initially loaded on mobile device (tested on tablet), then there are JS errors, and the output is broken. > After full refresh of the page it is rendered correctly. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:45:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:45:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13702) Charts Mobile Showcase - initial rendering is broken and with JS errors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979665#comment-12979665 ] Juraj H?ska commented on RF-13702: ---------------------------------- It is reproducible in RichFaces {{5.0.0.Alpha3}} as well. > Charts Mobile Showcase - initial rendering is broken and with JS errors > ----------------------------------------------------------------------- > > Key: RF-13702 > URL: https://issues.jboss.org/browse/RF-13702 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, mobile > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Attachments: chartRenderingError.PNG > > > When the charts demo from Showcase is initially loaded on mobile device (tested on tablet), then there are JS errors, and the output is broken. > After full refresh of the page it is rendered correctly. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:47:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:47:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13700) Charts Mobile Showcase demo on tablets - bars are overlapping In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13700: ----------------------------- Affects Version/s: 5.0.0.Alpha3 > Charts Mobile Showcase demo on tablets - bars are overlapping > ------------------------------------------------------------- > > Key: RF-13700 > URL: https://issues.jboss.org/browse/RF-13700 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Attachments: barChartOverlapping.PNG > > > Bars in the showcase chart demo are overlapping. It is probably issue of responsiveness. It is reproducible on Mobile showcase demo, accessing on tablets. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:47:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:47:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13700) Charts Mobile Showcase demo on tablets - bars are overlapping In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979666#comment-12979666 ] Juraj H?ska commented on RF-13700: ---------------------------------- It is reproducible on RichFaces {{5.0.0.Alpha3}} as well. > Charts Mobile Showcase demo on tablets - bars are overlapping > ------------------------------------------------------------- > > Key: RF-13700 > URL: https://issues.jboss.org/browse/RF-13700 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Attachments: barChartOverlapping.PNG > > > Bars in the showcase chart demo are overlapping. It is probably issue of responsiveness. It is reproducible on Mobile showcase demo, accessing on tablets. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:49:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:49:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13583) Backport the chart components to RichFaces 4.5 components module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979667#comment-12979667 ] Juraj H?ska commented on RF-13583: ---------------------------------- I have found some issues with charts on mobile devices: RF-13700 & RF-13702. Unlike [~manovotn] issues, my are reproducible on {{5.0.0.Alpha3}}. > Backport the chart components to RichFaces 4.5 components module > ---------------------------------------------------------------- > > Key: RF-13583 > URL: https://issues.jboss.org/browse/RF-13583 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Backport the chart components to RichFaces 4.5 components module -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:53:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:53:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13702) Charts Mobile Showcase - initial rendering is broken and with JS errors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979665#comment-12979665 ] Juraj H?ska edited comment on RF-13702 at 6/26/14 8:52 AM: ----------------------------------------------------------- It is reproducible in RichFaces {{5.0.0-SNAPSHOT}} as well. was (Author: jhuska): It is reproducible in RichFaces {{5.0.0.Alpha3}} as well. > Charts Mobile Showcase - initial rendering is broken and with JS errors > ----------------------------------------------------------------------- > > Key: RF-13702 > URL: https://issues.jboss.org/browse/RF-13702 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, mobile > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Attachments: chartRenderingError.PNG > > > When the charts demo from Showcase is initially loaded on mobile device (tested on tablet), then there are JS errors, and the output is broken. > After full refresh of the page it is rendered correctly. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:53:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:53:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13700) Charts Mobile Showcase demo on tablets - bars are overlapping In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979666#comment-12979666 ] Juraj H?ska edited comment on RF-13700 at 6/26/14 8:52 AM: ----------------------------------------------------------- It is reproducible on RichFaces {{5.0.0-SNAPSHOT}} as well. was (Author: jhuska): It is reproducible on RichFaces {{5.0.0.Alpha3}} as well. > Charts Mobile Showcase demo on tablets - bars are overlapping > ------------------------------------------------------------- > > Key: RF-13700 > URL: https://issues.jboss.org/browse/RF-13700 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Attachments: barChartOverlapping.PNG > > > Bars in the showcase chart demo are overlapping. It is probably issue of responsiveness. It is reproducible on Mobile showcase demo, accessing on tablets. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:53:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:53:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13583) Backport the chart components to RichFaces 4.5 components module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979667#comment-12979667 ] Juraj H?ska edited comment on RF-13583 at 6/26/14 8:53 AM: ----------------------------------------------------------- I have found some issues with charts on mobile devices: RF-13700 & RF-13702. Unlike [~manovotn] issues, my are reproducible on {{5.0.0.-SNAPSHOT}} as well. was (Author: jhuska): I have found some issues with charts on mobile devices: RF-13700 & RF-13702. Unlike [~manovotn] issues, my are reproducible on {{5.0.0.Alpha3}}. > Backport the chart components to RichFaces 4.5 components module > ---------------------------------------------------------------- > > Key: RF-13583 > URL: https://issues.jboss.org/browse/RF-13583 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Backport the chart components to RichFaces 4.5 components module -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:59:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:59:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13702) Charts Mobile Showcase - initial rendering is broken and with JS errors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13702: ----------------------------- Steps to Reproduce: # deploy Showcase # load on mobile device: http://yourIpAddress:8080/showcase/#chart:simple # see that there are no charts rendered and that there are JS errors # see that after a refresh it is working correctly was: # deploy Showcase # load: http://yourIpAddress:8080/showcase/#chart:simple # see that there are no charts rendered and that there are JS errors # see that after a refresh it is working correctly > Charts Mobile Showcase - initial rendering is broken and with JS errors > ----------------------------------------------------------------------- > > Key: RF-13702 > URL: https://issues.jboss.org/browse/RF-13702 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, mobile > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Attachments: chartRenderingError.PNG > > > When the charts demo from Showcase is initially loaded on mobile device (tested on tablet), then there are JS errors, and the output is broken. > After full refresh of the page it is rendered correctly. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:59:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:59:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13700) Charts Mobile Showcase demo on tablets - bars are overlapping In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13700: ----------------------------- Steps to Reproduce: # deploy showcase # load on mobile device: http://youIpAddress:8080/showcase/#chart:simple # see that in Bar chart, some bars are overlapping was: # deploy showcase # load on tablet device: http://youIpAddress:8080/showcase/#chart:simple # see that in Bar chart, some bars are overlapping > Charts Mobile Showcase demo on tablets - bars are overlapping > ------------------------------------------------------------- > > Key: RF-13700 > URL: https://issues.jboss.org/browse/RF-13700 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Attachments: barChartOverlapping.PNG > > > Bars in the showcase chart demo are overlapping. It is probably issue of responsiveness. It is reproducible on Mobile showcase demo, accessing on tablets. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 08:59:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 26 Jun 2014 08:59:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13700) Charts Mobile Showcase demo - bars are overlapping In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13700: ----------------------------- Summary: Charts Mobile Showcase demo - bars are overlapping (was: Charts Mobile Showcase demo on tablets - bars are overlapping) > Charts Mobile Showcase demo - bars are overlapping > -------------------------------------------------- > > Key: RF-13700 > URL: https://issues.jboss.org/browse/RF-13700 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Attachments: barChartOverlapping.PNG > > > Bars in the showcase chart demo are overlapping. It is probably issue of responsiveness. It is reproducible on Mobile showcase demo, accessing on tablets. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 11:15:26 2014 From: issues at jboss.org (Yannick Valot (JIRA)) Date: Thu, 26 Jun 2014 11:15:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13703) Nested UIDataAdaptor restoring stale data because of reentrancy problem In-Reply-To: References: Message-ID: Yannick Valot created RF-13703: ---------------------------------- Summary: Nested UIDataAdaptor restoring stale data because of reentrancy problem Key: RF-13703 URL: https://issues.jboss.org/browse/RF-13703 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.1 Environment: (Windows 7. Java 6. Jetty 7.6.9 or Tomcat 6.0.37) Reporter: Yannick Valot I am encountering a reentrancy problem with nested UIDataAdaptor components. For instance something like : When a view contains nested UIDataAdaptor components, each UIDataAdaptor component has its own internal store for saving the saved state of child components (saveChildState/restoreChildState). Since "inputText" is included in both tables, each one may save and restore the value of the component in its internal store. For instance, when "outer" is on key 0 and inner is on key "2", both "outer" and "inner" may store the state values for myText "outer:0:inner:2:myText" in their "childState" property. I guess that most of the time, only "inner" will actually store useful values, because most of calls on "setRowKey" for outer will be done when "inner" has its rowkey set to null. Unfortunately, this is not always the case. For instance, if I decide to visit the component tree while processing an event for "myText", outer will perform a setRowKey while inner has its own rowKey to a significant value (for instance, 2), the result being that inner's value will be erased by outer's. To try and explain with a little more detail... Let's say that we are processing an event on "outer:1:inner:0:myText", and we start a (nested) visit of the tree : 1) "outer" will at some point perform a setRowKey(0) 2) It will then do a restoreChildState for myText. since "inner" has rowKey set to 0, it will restore "outer's" value for "outer:0:inner:0:myText". 3) A bit later on during the visit, inner will do "setRowKey(0)". It will first save the current value for "outer:0:inner:0:myText" (which comes from outer's backup of it, restored on step 2) The result of this process is that "outer"'s backup of "outer:0:inner:0:myText" overwrites "inner"'s backup for it. This is problematic because this leads, sometimes, to an old and obsolete backup of state taking place of the current value. This may happen several HTTP requests later. I've found a solution for this problem by not storing the saved state in the UIDataAdaptor, but in the target component itself. In this manner, there can only be one backup of the data. Such a modification is actually hinted at in UIDataAdaptor's source code : "// TODO - use local map - children save their state themselves using visitors", although my modification is simpler (it's still UIDataAdaptor that saves the state, in the same manner, only in a different place). This bug is quite complex and extracting a testcase will take some time, but I am willing to do so if requested. I can also offer my patch for the problem once I have finalized it. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 11:27:24 2014 From: issues at jboss.org (Yannick Valot (JIRA)) Date: Thu, 26 Jun 2014 11:27:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11093) UIDataAdaptor context variable backup broken (reentrance problem) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979715#comment-12979715 ] Yannick Valot commented on RF-11093: ------------------------------------ Hello, we've been using this patch in production for quite some time now. Please tell me how I can help include this patch, or if there is any reason why you would not want to include it. > UIDataAdaptor context variable backup broken (reentrance problem) > ----------------------------------------------------------------- > > Key: RF-11093 > URL: https://issues.jboss.org/browse/RF-11093 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final > Environment: Windows XP, Java 6, Tomcat 6.0.24, Mojarra 2.0.2. > Reporter: Yannick Valot > Fix For: 5-Future > > Attachments: UIDataAdaptor.java.patch > > > I am encountering a reentrance problem with org.richfaces.component.UIDataAdaptor (using it as a dataTable). > I need to perform a visit of the component tree while executing an action on a command link in one row of the same table. > > ... some stuff here ... > > ... some stuff here ... > > After the action on the command link has visited the component tree, myItem is no longer available in context. > When the UIDataAdaptor sets or resets the "myItem" context variable, it backs up any previous value by calling captureOrigValue(FacesContext), and later restores it by calling restoreOrigValue(FacesContext), but it looks as if the visit backs the variable up twice (in a nested fashion), and it erases myItem between the two backups : > - backup variable (old value is correctly backed up) (in visitTree(VisitContext visitContext, VisitCallback callback)) > - erase variable (setRowKey(facesContext, null) in same function) > - erase variable (doVisitChildren(VisitContext context, boolean visitRows)) > - erase variable (visitTree(VisitContext visitContext, VisitCallback callback)) > - backup variable (erases backed up value) (walk(FacesContext faces, DataVisitor visitor, Object argument)) > - ... > - restore value (restores null) (walk(FacesContext faces, DataVisitor visitor, Object argument)) > - restore value (restores null) (in visitTree(VisitContext visitContext, VisitCallback callback)) > etc. > The problem can be solved by *stacking* backed up variables, instead of storing them in a simple attribute, to allow for any kind of reentrance. > (I do not say that this is the best possible patch, but it has solved the problem for me). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 13:55:24 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 26 Jun 2014 13:55:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13697) fileupload: maxFilesQuantity + multiple select: can upload more files than the limit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13697. -------------------------------- Assignee: Michal Petrov Resolution: Done > fileupload: maxFilesQuantity + multiple select: can upload more files than the limit > ------------------------------------------------------------------------------------ > > Key: RF-13697 > URL: https://issues.jboss.org/browse/RF-13697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: Tried on EAP 6.3.0.ER8, FF 30 > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > > Can add more files than @maxFilesQuantity to upload when using multiselect after some files have been added before. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Thu Jun 26 16:25:24 2014 From: issues at jboss.org (Kalle Richter (JIRA)) Date: Thu, 26 Jun 2014 16:25:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13704) Add link to rich:layout successor layout:layout In-Reply-To: References: Message-ID: Kalle Richter created RF-13704: ---------------------------------- Summary: Add link to rich:layout successor layout:layout Key: RF-13704 URL: https://issues.jboss.org/browse/RF-13704 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: migration, third-party Reporter: Kalle Richter Priority: Trivial The 3.3.x -> 4.x migration guide at https://community.jboss.org/wiki/RichFaces33-4xMigrationGuideUnleashed states that rich:layout has been replaced by/moved to the third-party project/namespace layout:layout. Where can it be found? Please add a link in the guide directly or an explanation if necessary as $SEARCH_ENGINE doesn't seem to find anything useful. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 28 11:22:24 2014 From: issues at jboss.org (Kalle Richter (JIRA)) Date: Sat, 28 Jun 2014 11:22:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13050) Showcase - not all demos have references for beans which are used in them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980102#comment-12980102 ] Kalle Richter commented on RF-13050: ------------------------------------ List update: * rich:treeModelRecursiveAdaptor (http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=treeAdaptors&sample=treeModelRecursiveAdaptor&skin=blueSky) > Showcase - not all demos have references for beans which are used in them > ------------------------------------------------------------------------- > > Key: RF-13050 > URL: https://issues.jboss.org/browse/RF-13050 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj H?ska > Fix For: 5-Tracking > > > There are some demos in showcase which do not have references for the beans source code, which are used in them. > Each contains the facelet source code, but the beans are missing. > It is so for example in demos: > * extended data table - basic usage > * collapsible subtable > * data scroller > and others. I will update the list once you indicate that we are going to fix this. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sat Jun 28 11:24:24 2014 From: issues at jboss.org (Kalle Richter (JIRA)) Date: Sat, 28 Jun 2014 11:24:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13050) Showcase - not all demos have references for beans which are used in them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980103#comment-12980103 ] Kalle Richter commented on RF-13050: ------------------------------------ Affects version 4.3.7 as well (strange that I can't add this in the metadata). > Showcase - not all demos have references for beans which are used in them > ------------------------------------------------------------------------- > > Key: RF-13050 > URL: https://issues.jboss.org/browse/RF-13050 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj H?ska > Fix For: 5-Tracking > > > There are some demos in showcase which do not have references for the beans source code, which are used in them. > Each contains the facelet source code, but the beans are missing. > It is so for example in demos: > * extended data table - basic usage > * collapsible subtable > * data scroller > and others. I will update the list once you indicate that we are going to fix this. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Sun Jun 29 06:58:24 2014 From: issues at jboss.org (Kalle Richter (JIRA)) Date: Sun, 29 Jun 2014 06:58:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13705) Clearify the relation between leaf and nodes attribute of rich:treeModelAdaptor In-Reply-To: References: Message-ID: Kalle Richter created RF-13705: ---------------------------------- Summary: Clearify the relation between leaf and nodes attribute of rich:treeModelAdaptor Key: RF-13705 URL: https://issues.jboss.org/browse/RF-13705 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.3.7 Reporter: Kalle Richter The javadoc states that both attributes are responsible for determining leafs, but there's no statement about what happens if they're both specified and - if it is possible to specify both - which takes precedence. It is currently not possible to get started with rich:tree due to missing demos (see https://issues.jboss.org/browse/RF-13050), so I consider this rather important. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 02:21:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 30 Jun 2014 02:21:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13697) fileupload: maxFilesQuantity + multiple select: can upload more files than the limit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13697: ----------------------------- Fix Version/s: 4.5.0.Alpha3 > fileupload: maxFilesQuantity + multiple select: can upload more files than the limit > ------------------------------------------------------------------------------------ > > Key: RF-13697 > URL: https://issues.jboss.org/browse/RF-13697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: Tried on EAP 6.3.0.ER8, FF 30 > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > Can add more files than @maxFilesQuantity to upload when using multiselect after some files have been added before. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 02:27:24 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 30 Jun 2014 02:27:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13697) fileupload: maxFilesQuantity + multiple select: can upload more files than the limit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek closed RF-13697. ---------------------------- Verified in 4.5 Metamer, closing. > fileupload: maxFilesQuantity + multiple select: can upload more files than the limit > ------------------------------------------------------------------------------------ > > Key: RF-13697 > URL: https://issues.jboss.org/browse/RF-13697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: Tried on EAP 6.3.0.ER8, FF 30 > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > Can add more files than @maxFilesQuantity to upload when using multiselect after some files have been added before. See steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 02:29:24 2014 From: issues at jboss.org (Jozef Hartinger (JIRA)) Date: Mon, 30 Jun 2014 02:29:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13692) Photoalbum can not be deployed to WildFly 8.0.x or 8.1.x due to Weld exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980510#comment-12980510 ] Jozef Hartinger commented on RF-13692: -------------------------------------- CDI 1.1 requires strict checking of when BeanManager methods are invoked. The non-portable mode is the correct solution in this case. The rules got more lenient in CDI 1.2 so the non-portable mode will not be required again with Weld 2.2. As for the other issue the log message describes the problem clearly. The interceptors specification requires that: {quote} Lifecycle callback interceptor methods defined on a target class have the following signature: void () {quote} org.richfaces.photoalbum.manager.Authenticator violates this requirement. In previos versions of Weld this was not checked properly thus the application works on EAP. > Photoalbum can not be deployed to WildFly 8.0.x or 8.1.x due to Weld exception > ------------------------------------------------------------------------------ > > Key: RF-13692 > URL: https://issues.jboss.org/browse/RF-13692 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > > There is an error during deployment of Photoalbum example on WildFly 8.1.0.Final or 8.0.0.Final > {code} > 09:28:51,675 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getBeans() is not available during application initialization > at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerValidated(BeanManagerProxy.java:159) > at org.jboss.weld.bean.builtin.BeanManagerProxy.getBeans(BeanManagerProxy.java:91) > at org.jboss.solder.core.CoreExtension.failIfWeldExtensionsDetected(CoreExtension.java:215) > at org.jboss.solder.core.CoreExtension.afterBeanDiscovery(CoreExtension.java:208) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:266) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:125) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:232) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:169) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:128) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:102) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:63) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:35) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:55) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:372) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:79) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:37) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:55) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:372) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:79) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > ... 3 more > {code} > and > {code} > JBAS014775: New missing/unsatisfied dependencies: > service jboss.deployment.unit."richfaces-photoalbum.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService, JBAS014799: ... and 23 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService, JBAS014799: ... and 22 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.VIEW."org.richfaces.photoalbum.model.actions.IAlbumAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.VIEW."org.richfaces.photoalbum.model.actions.IEventAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.VIEW."org.richfaces.photoalbum.model.actions.IImageAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.VIEW."org.richfaces.photoalbum.search.ISearchAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.VIEW."org.richfaces.photoalbum.model.actions.IShelfAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.VIEW."org.richfaces.photoalbum.model.actions.IUserAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START, service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START, JBAS014799: ... and 16 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START, JBAS014799: ... and 4 more ] > service jboss.persistenceunit."richfaces-photoalbum.war#photoAlbum" (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START, service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService, JBAS014799: ... and 13 more ] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > {code} > Note that it *works* on EAP 6.2.3.GA and EAP 6.3.0.ER8 > Both WildFly containers use Weld 2.1.x, so it is not a problem with Weld 2.2.x integration. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 04:03:24 2014 From: issues at jboss.org (Marcel Kolsteren (JIRA)) Date: Mon, 30 Jun 2014 04:03:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: Marcel Kolsteren created RF-13706: ------------------------------------- Summary: dequeued Ajax request not processed correctly if its source element has been updated Key: RF-13706 URL: https://issues.jboss.org/browse/RF-13706 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.3.7 Reporter: Marcel Kolsteren I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: {noformat}
{noformat} The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 04:05:24 2014 From: issues at jboss.org (Marcel Kolsteren (JIRA)) Date: Mon, 30 Jun 2014 04:05:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kolsteren updated RF-13706: ---------------------------------- Attachment: queuetest.zip Maven project with sample application > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 04:05:26 2014 From: issues at jboss.org (Marcel Kolsteren (JIRA)) Date: Mon, 30 Jun 2014 04:05:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980534#comment-12980534 ] Marcel Kolsteren edited comment on RF-13706 at 6/30/14 4:04 AM: ---------------------------------------------------------------- Added attachments was (Author: marcelkolsteren): Maven project with sample application > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 04:05:27 2014 From: issues at jboss.org (Marcel Kolsteren (JIRA)) Date: Mon, 30 Jun 2014 04:05:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kolsteren updated RF-13706: ---------------------------------- Attachment: richfaces-core-4.3.8-SNAPSHOT.patch.zip > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 04:07:25 2014 From: issues at jboss.org (Marcel Kolsteren (JIRA)) Date: Mon, 30 Jun 2014 04:07:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kolsteren updated RF-13706: ---------------------------------- Component/s: core > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 04:07:25 2014 From: issues at jboss.org (Marcel Kolsteren (JIRA)) Date: Mon, 30 Jun 2014 04:07:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kolsteren updated RF-13706: ---------------------------------- Component/s: (was: component-a4j-core) > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 08:09:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 30 Jun 2014 08:09:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13707) Photoalbum: incorrect account details shown after creating a new one In-Reply-To: References: Message-ID: Juraj H?ska created RF-13707: -------------------------------- Summary: Photoalbum: incorrect account details shown after creating a new one Key: RF-13707 URL: https://issues.jboss.org/browse/RF-13707 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.3.8 Reporter: Juraj H?ska When user create a new account in Photoalbum application there are shown account details, which are incorrect: * missing login, first name, surname * wrong sex value (there is always female) * missing Birthday and email -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 08:11:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 30 Jun 2014 08:11:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13707) Photoalbum: incorrect account details shown after creating a new one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13707: ----------------------------- Description: When user create a new account in Photoalbum application there are shown account details, which are incorrect: * missing login, first name, surname * wrong sex value (there is always female - I tried other than my photos, so the problem will be somewhere else :) ) * missing Birthday and email was: When user create a new account in Photoalbum application there are shown account details, which are incorrect: * missing login, first name, surname * wrong sex value (there is always female) * missing Birthday and email > Photoalbum: incorrect account details shown after creating a new one > -------------------------------------------------------------------- > > Key: RF-13707 > URL: https://issues.jboss.org/browse/RF-13707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.8 > Reporter: Juraj H?ska > > When user create a new account in Photoalbum application there are shown account details, which are incorrect: > * missing login, first name, surname > * wrong sex value (there is always female - I tried other than my photos, so the problem will be somewhere else :) ) > * missing Birthday and email -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 08:11:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 30 Jun 2014 08:11:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13707) Photoalbum: incorrect account details shown after creating a new one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13707: ----------------------------- Description: When user create a new account in Photoalbum application there are shown account details, which are incorrect: * missing login, first name, surname * wrong sex value (there is always female - I tried other than my photos as avatars, so the problem will be somewhere else :) ) * missing Birthday and email was: When user create a new account in Photoalbum application there are shown account details, which are incorrect: * missing login, first name, surname * wrong sex value (there is always female - I tried other than my photos, so the problem will be somewhere else :) ) * missing Birthday and email > Photoalbum: incorrect account details shown after creating a new one > -------------------------------------------------------------------- > > Key: RF-13707 > URL: https://issues.jboss.org/browse/RF-13707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.8 > Reporter: Juraj H?ska > > When user create a new account in Photoalbum application there are shown account details, which are incorrect: > * missing login, first name, surname > * wrong sex value (there is always female - I tried other than my photos as avatars, so the problem will be somewhere else :) ) > * missing Birthday and email -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 08:39:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 30 Jun 2014 08:39:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13708) Photoalbum: refresh over index page throws error In-Reply-To: References: Message-ID: Juraj H?ska created RF-13708: -------------------------------- Summary: Photoalbum: refresh over index page throws error Key: RF-13708 URL: https://issues.jboss.org/browse/RF-13708 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.3.8 Environment: JBoss EAP 6.3.0.ER8 Reporter: Juraj H?ska Refresh over index page of Photoalbum throws: {code} 14:31:05,563 SEVERE [javax.enterprise.resource.webcontainer.jsf.renderkit] (http-/127.0.0.1:8080-5) javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. : javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. at com.sun.faces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.28.Final-redhat-1.jar:2.1.28.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] {code} After this error application cease to work. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 08:59:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 30 Jun 2014 08:59:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13708) Photoalbum: refresh over index page throws error In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980617#comment-12980617 ] Juraj H?ska commented on RF-13708: ---------------------------------- The issue was present in RichFaces 4.3.6.Final as well. > Photoalbum: refresh over index page throws error > ------------------------------------------------ > > Key: RF-13708 > URL: https://issues.jboss.org/browse/RF-13708 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.8 > Environment: JBoss EAP 6.3.0.ER8 > Reporter: Juraj H?ska > > Refresh over index page of Photoalbum throws: > {code} > 14:31:05,563 SEVERE [javax.enterprise.resource.webcontainer.jsf.renderkit] (http-/127.0.0.1:8080-5) javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. : javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. > at com.sun.faces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.28.Final-redhat-1.jar:2.1.28.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > {code} > After this error application cease to work. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 08:59:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 30 Jun 2014 08:59:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13708) Photoalbum: refresh over index page throws error In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13708: ----------------------------- Environment: container: JBoss EAP 6.3.0.ER8, other EAPS as well browsers: all was:JBoss EAP 6.3.0.ER8 > Photoalbum: refresh over index page throws error > ------------------------------------------------ > > Key: RF-13708 > URL: https://issues.jboss.org/browse/RF-13708 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.8 > Environment: container: JBoss EAP 6.3.0.ER8, other EAPS as well > browsers: all > Reporter: Juraj H?ska > > Refresh over index page of Photoalbum throws: > {code} > 14:31:05,563 SEVERE [javax.enterprise.resource.webcontainer.jsf.renderkit] (http-/127.0.0.1:8080-5) javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. : javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. > at com.sun.faces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.28.Final-redhat-1.jar:2.1.28.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > {code} > After this error application cease to work. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 09:05:24 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 30 Jun 2014 09:05:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13707) Photoalbum: incorrect account details shown after creating a new one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13707: ----------------------------- Labels: photoalbum (was: ) > Photoalbum: incorrect account details shown after creating a new one > -------------------------------------------------------------------- > > Key: RF-13707 > URL: https://issues.jboss.org/browse/RF-13707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.8 > Reporter: Juraj H?ska > Labels: photoalbum > > When user create a new account in Photoalbum application there are shown account details, which are incorrect: > * missing login, first name, surname > * wrong sex value (there is always female - I tried other than my photos as avatars, so the problem will be somewhere else :) ) > * missing Birthday and email -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 09:05:25 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 30 Jun 2014 09:05:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13708) Photoalbum: refresh over index page throws error In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13708: ----------------------------- Labels: photoalbum (was: ) > Photoalbum: refresh over index page throws error > ------------------------------------------------ > > Key: RF-13708 > URL: https://issues.jboss.org/browse/RF-13708 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.8 > Environment: container: JBoss EAP 6.3.0.ER8, other EAPS as well > browsers: all > Reporter: Juraj H?ska > Labels: photoalbum > > Refresh over index page of Photoalbum throws: > {code} > 14:31:05,563 SEVERE [javax.enterprise.resource.webcontainer.jsf.renderkit] (http-/127.0.0.1:8080-5) javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. : javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. > at com.sun.faces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.28.Final-redhat-1.jar:2.1.28.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > {code} > After this error application cease to work. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 12:11:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 12:11:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11093) UIDataAdaptor context variable backup broken (reentrance problem) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11093: ------------------------------- Description: I am encountering a reentrance problem with org.richfaces.component.UIDataAdaptor (using it as a dataTable). I need to perform a visit of the component tree while executing an action on a command link in one row of the same table. {code} ... some stuff here ... ... some stuff here ... {code} After the action on the command link has visited the component tree, myItem is no longer available in context. When the UIDataAdaptor sets or resets the "myItem" context variable, it backs up any previous value by calling captureOrigValue(FacesContext), and later restores it by calling restoreOrigValue(FacesContext), but it looks as if the visit backs the variable up twice (in a nested fashion), and it erases myItem between the two backups : - backup variable (old value is correctly backed up) (in visitTree(VisitContext visitContext, VisitCallback callback)) - erase variable (setRowKey(facesContext, null) in same function) - erase variable (doVisitChildren(VisitContext context, boolean visitRows)) - erase variable (visitTree(VisitContext visitContext, VisitCallback callback)) - backup variable (erases backed up value) (walk(FacesContext faces, DataVisitor visitor, Object argument)) - ... - restore value (restores null) (walk(FacesContext faces, DataVisitor visitor, Object argument)) - restore value (restores null) (in visitTree(VisitContext visitContext, VisitCallback callback)) etc. The problem can be solved by *stacking* backed up variables, instead of storing them in a simple attribute, to allow for any kind of reentrance. (I do not say that this is the best possible patch, but it has solved the problem for me). was: I am encountering a reentrance problem with org.richfaces.component.UIDataAdaptor (using it as a dataTable). I need to perform a visit of the component tree while executing an action on a command link in one row of the same table. ... some stuff here ... ... some stuff here ... After the action on the command link has visited the component tree, myItem is no longer available in context. When the UIDataAdaptor sets or resets the "myItem" context variable, it backs up any previous value by calling captureOrigValue(FacesContext), and later restores it by calling restoreOrigValue(FacesContext), but it looks as if the visit backs the variable up twice (in a nested fashion), and it erases myItem between the two backups : - backup variable (old value is correctly backed up) (in visitTree(VisitContext visitContext, VisitCallback callback)) - erase variable (setRowKey(facesContext, null) in same function) - erase variable (doVisitChildren(VisitContext context, boolean visitRows)) - erase variable (visitTree(VisitContext visitContext, VisitCallback callback)) - backup variable (erases backed up value) (walk(FacesContext faces, DataVisitor visitor, Object argument)) - ... - restore value (restores null) (walk(FacesContext faces, DataVisitor visitor, Object argument)) - restore value (restores null) (in visitTree(VisitContext visitContext, VisitCallback callback)) etc. The problem can be solved by *stacking* backed up variables, instead of storing them in a simple attribute, to allow for any kind of reentrance. (I do not say that this is the best possible patch, but it has solved the problem for me). > UIDataAdaptor context variable backup broken (reentrance problem) > ----------------------------------------------------------------- > > Key: RF-11093 > URL: https://issues.jboss.org/browse/RF-11093 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final > Environment: Windows XP, Java 6, Tomcat 6.0.24, Mojarra 2.0.2. > Reporter: Yannick Valot > Fix For: 5-Future > > Attachments: UIDataAdaptor.java.patch > > > I am encountering a reentrance problem with org.richfaces.component.UIDataAdaptor (using it as a dataTable). > I need to perform a visit of the component tree while executing an action on a command link in one row of the same table. > {code} > > ... some stuff here ... > > ... some stuff here ... > > {code} > After the action on the command link has visited the component tree, myItem is no longer available in context. > When the UIDataAdaptor sets or resets the "myItem" context variable, it backs up any previous value by calling captureOrigValue(FacesContext), and later restores it by calling restoreOrigValue(FacesContext), but it looks as if the visit backs the variable up twice (in a nested fashion), and it erases myItem between the two backups : > - backup variable (old value is correctly backed up) (in visitTree(VisitContext visitContext, VisitCallback callback)) > - erase variable (setRowKey(facesContext, null) in same function) > - erase variable (doVisitChildren(VisitContext context, boolean visitRows)) > - erase variable (visitTree(VisitContext visitContext, VisitCallback callback)) > - backup variable (erases backed up value) (walk(FacesContext faces, DataVisitor visitor, Object argument)) > - ... > - restore value (restores null) (walk(FacesContext faces, DataVisitor visitor, Object argument)) > - restore value (restores null) (in visitTree(VisitContext visitContext, VisitCallback callback)) > etc. > The problem can be solved by *stacking* backed up variables, instead of storing them in a simple attribute, to allow for any kind of reentrance. > (I do not say that this is the best possible patch, but it has solved the problem for me). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 12:15:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 12:15:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11093) UIDataAdaptor context variable backup broken (reentrance problem) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980728#comment-12980728 ] Brian Leathem commented on RF-11093: ------------------------------------ [~yvalot] if you formulate your patch as a git pull request against RichFaces 4.5 we'll review the code changes and kick off our tests to check for regressions. See this howto for details on creating a pull request (Note however that you'll want to create your PR against the {{4.5.x}} branch, rather than against the {{master}} branch): https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA > UIDataAdaptor context variable backup broken (reentrance problem) > ----------------------------------------------------------------- > > Key: RF-11093 > URL: https://issues.jboss.org/browse/RF-11093 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.Final > Environment: Windows XP, Java 6, Tomcat 6.0.24, Mojarra 2.0.2. > Reporter: Yannick Valot > Fix For: 5-Future > > Attachments: UIDataAdaptor.java.patch > > > I am encountering a reentrance problem with org.richfaces.component.UIDataAdaptor (using it as a dataTable). > I need to perform a visit of the component tree while executing an action on a command link in one row of the same table. > {code} > > ... some stuff here ... > > ... some stuff here ... > > {code} > After the action on the command link has visited the component tree, myItem is no longer available in context. > When the UIDataAdaptor sets or resets the "myItem" context variable, it backs up any previous value by calling captureOrigValue(FacesContext), and later restores it by calling restoreOrigValue(FacesContext), but it looks as if the visit backs the variable up twice (in a nested fashion), and it erases myItem between the two backups : > - backup variable (old value is correctly backed up) (in visitTree(VisitContext visitContext, VisitCallback callback)) > - erase variable (setRowKey(facesContext, null) in same function) > - erase variable (doVisitChildren(VisitContext context, boolean visitRows)) > - erase variable (visitTree(VisitContext visitContext, VisitCallback callback)) > - backup variable (erases backed up value) (walk(FacesContext faces, DataVisitor visitor, Object argument)) > - ... > - restore value (restores null) (walk(FacesContext faces, DataVisitor visitor, Object argument)) > - restore value (restores null) (in visitTree(VisitContext visitContext, VisitCallback callback)) > etc. > The problem can be solved by *stacking* backed up variables, instead of storing them in a simple attribute, to allow for any kind of reentrance. > (I do not say that this is the best possible patch, but it has solved the problem for me). -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 12:17:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 12:17:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13050) Showcase - not all demos have references for beans which are used in them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13050: ------------------------------- Fix Version/s: 4.5-Tracking (was: 5-Tracking) > Showcase - not all demos have references for beans which are used in them > ------------------------------------------------------------------------- > > Key: RF-13050 > URL: https://issues.jboss.org/browse/RF-13050 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.7, 5.0.0.Alpha1 > Reporter: Juraj H?ska > Fix For: 4.5-Tracking > > > There are some demos in showcase which do not have references for the beans source code, which are used in them. > Each contains the facelet source code, but the beans are missing. > It is so for example in demos: > * extended data table - basic usage > * collapsible subtable > * data scroller > and others. I will update the list once you indicate that we are going to fix this. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 12:17:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 12:17:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13050) Showcase - not all demos have references for beans which are used in them In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13050: ------------------------------- Affects Version/s: 4.3.7 > Showcase - not all demos have references for beans which are used in them > ------------------------------------------------------------------------- > > Key: RF-13050 > URL: https://issues.jboss.org/browse/RF-13050 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.7, 5.0.0.Alpha1 > Reporter: Juraj H?ska > Fix For: 4.5-Tracking > > > There are some demos in showcase which do not have references for the beans source code, which are used in them. > Each contains the facelet source code, but the beans are missing. > It is so for example in demos: > * extended data table - basic usage > * collapsible subtable > * data scroller > and others. I will update the list once you indicate that we are going to fix this. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:31:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:31:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13709) Remove the chart components from the RichFaces showcase In-Reply-To: References: Message-ID: Brian Leathem created RF-13709: ---------------------------------- Summary: Remove the chart components from the RichFaces showcase Key: RF-13709 URL: https://issues.jboss.org/browse/RF-13709 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Assignee: Brian Leathem Priority: Minor Fix For: 4.5.0.Alpha3 The chart components need additional work to function in a mobile environment. In the mean time we should remove them from the mobile showcase. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:33:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:33:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13702) Charts Mobile Showcase - initial rendering is broken and with JS errors In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13702. -------------------------------- Assignee: Brian Leathem Resolution: Won't Fix Chart components won't be supported on mobile for the time being. We'll remove them from the mobile showcase in RF-13709. > Charts Mobile Showcase - initial rendering is broken and with JS errors > ----------------------------------------------------------------------- > > Key: RF-13702 > URL: https://issues.jboss.org/browse/RF-13702 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, mobile > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Brian Leathem > Attachments: chartRenderingError.PNG > > > When the charts demo from Showcase is initially loaded on mobile device (tested on tablet), then there are JS errors, and the output is broken. > After full refresh of the page it is rendered correctly. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:33:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:33:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13700) Charts Mobile Showcase demo - bars are overlapping In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13700. -------------------------------- Assignee: Brian Leathem Resolution: Won't Fix Chart components won't be supported on mobile for the time being. We'll remove them from the mobile showcase in RF-13709. > Charts Mobile Showcase demo - bars are overlapping > -------------------------------------------------- > > Key: RF-13700 > URL: https://issues.jboss.org/browse/RF-13700 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Brian Leathem > Attachments: barChartOverlapping.PNG > > > Bars in the showcase chart demo are overlapping. It is probably issue of responsiveness. It is reproducible on Mobile showcase demo, accessing on tablets. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:33:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:33:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13698) RF 4.5 Chart title does not render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13698: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > RF 4.5 Chart title does not render > ---------------------------------- > > Key: RF-13698 > URL: https://issues.jboss.org/browse/RF-13698 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > FF/Chrome > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > The title of the chart is not rendered above the chart. This affects all kinds of charts, eg. line, pie and bar. > I created Metamer samples of charts for 4.5.x where this can be tested (not automatically until public JS API for charts will be available). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:33:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:33:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13699) RF 4.5 Chart attribute 'zoom' does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13699: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > RF 4.5 Chart attribute 'zoom' does not work > ------------------------------------------- > > Key: RF-13699 > URL: https://issues.jboss.org/browse/RF-13699 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > Latest Chrome/FF > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > The attribute 'zoom' does not work, setting it to true has no effect and user cannot zoom the chart. This attribute is only available for line chart. > I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:35:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:35:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13701) RF 4.5 Bar chart plotClick malfunctioning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13701: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > RF 4.5 Bar chart plotClick malfunctioning > ----------------------------------------- > > Key: RF-13701 > URL: https://issues.jboss.org/browse/RF-13701 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > Latest Chrome/FF > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > > When interacting with bar chart where {{onplotclick}} and {{plotClickListener}} are set, it does not react when last bar in the series is clicked (eg .no request is sent for server side event and no JS executed for onplotclick). See steps to reproduce, in case they are not clear ask me for more details. > I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:35:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:35:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13585) Re-factor the components demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13585: ------------------------------- Assignee: Juraj H?ska (was: Brian Leathem) > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > > Re-factor the components demo to work with RichFaces 4.5 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:37:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:37:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13638) Upgrade CKEditor to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13638: ------------------------------- Labels: needs-backport (was: ) > Upgrade CKEditor to 4.3 > ----------------------- > > Key: RF-13638 > URL: https://issues.jboss.org/browse/RF-13638 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: barbara b > Assignee: Luk?? Fry? > Labels: needs-backport > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > All current versions of Richfaces are working with CKEditor 3.6.6. Would it be possible to make an upgrade of CKEditor to a version 4.3? Some plugins for CKEditor are only working with the 4.X versions of the editor. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:37:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:37:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13695) Upgrade CSSParser for RF 5.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13695: ------------------------------- Fix Version/s: 5-Tracking > Upgrade CSSParser for RF 5.x > ---------------------------- > > Key: RF-13695 > URL: https://issues.jboss.org/browse/RF-13695 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha4 > Reporter: Matej Novotny > Priority: Minor > Fix For: 5-Tracking > > > As suggested in RF-13641, we should update CSSParser in RF 5 as well. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:41:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:41:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13671) Upgrade Arquillian PhantomJS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13671: ------------------------------- Fix Version/s: 4.5-Tracking (was: 5.0.0.Alpha4) (was: 4.5.0.Alpha3) > Upgrade Arquillian PhantomJS > ---------------------------- > > Key: RF-13671 > URL: https://issues.jboss.org/browse/RF-13671 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.5.0.Alpha2 > Reporter: Ji?? ?tefek > Assignee: Ji?? ?tefek > Fix For: 4.5-Tracking > > > Upgrade to version 1.1.3.Final -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:41:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:41:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13690) DataTable in uiRepeat - scrolling in table makes columns unsorted again In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13690: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > DataTable in uiRepeat - scrolling in table makes columns unsorted again > ----------------------------------------------------------------------- > > Key: RF-13690 > URL: https://issues.jboss.org/browse/RF-13690 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > > When {{DataTable}} is nested in {{uiRepeat}}, then scrolling over the table with {{dataScroller}} makes sorting according to some column broken - the columns are unsorted. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:41:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:41:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13691) EDT in uiRepeat - selection corrupted in multiple paged table In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13691: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > EDT in uiRepeat - selection corrupted in multiple paged table > ------------------------------------------------------------- > > Key: RF-13691 > URL: https://issues.jboss.org/browse/RF-13691 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > > When {{EDT}} is in {{uiRepeat}} and has multiple pages, then selection of rows functionality does not work as expected. > It seems that there is a problem with row indices. Please see steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:43:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:43:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13692) Photoalbum can not be deployed to WildFly 8.0.x or 8.1.x due to Weld exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13692: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Photoalbum can not be deployed to WildFly 8.0.x or 8.1.x due to Weld exception > ------------------------------------------------------------------------------ > > Key: RF-13692 > URL: https://issues.jboss.org/browse/RF-13692 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > > There is an error during deployment of Photoalbum example on WildFly 8.1.0.Final or 8.0.0.Final > {code} > 09:28:51,675 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getBeans() is not available during application initialization > at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerValidated(BeanManagerProxy.java:159) > at org.jboss.weld.bean.builtin.BeanManagerProxy.getBeans(BeanManagerProxy.java:91) > at org.jboss.solder.core.CoreExtension.failIfWeldExtensionsDetected(CoreExtension.java:215) > at org.jboss.solder.core.CoreExtension.afterBeanDiscovery(CoreExtension.java:208) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:266) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:125) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:232) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:169) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:128) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:102) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:63) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:35) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:55) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:372) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:79) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:37) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:55) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:372) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:79) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > ... 3 more > {code} > and > {code} > JBAS014775: New missing/unsatisfied dependencies: > service jboss.deployment.unit."richfaces-photoalbum.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService, JBAS014799: ... and 23 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService, JBAS014799: ... and 22 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.VIEW."org.richfaces.photoalbum.model.actions.IAlbumAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.VIEW."org.richfaces.photoalbum.model.actions.IEventAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.VIEW."org.richfaces.photoalbum.model.actions.IImageAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.VIEW."org.richfaces.photoalbum.search.ISearchAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.VIEW."org.richfaces.photoalbum.model.actions.IShelfAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.VIEW."org.richfaces.photoalbum.model.actions.IUserAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START, service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START, JBAS014799: ... and 16 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START, JBAS014799: ... and 4 more ] > service jboss.persistenceunit."richfaces-photoalbum.war#photoAlbum" (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START, service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService, JBAS014799: ... and 13 more ] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > {code} > Note that it *works* on EAP 6.2.3.GA and EAP 6.3.0.ER8 > Both WildFly containers use Weld 2.1.x, so it is not a problem with Weld 2.2.x integration. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:43:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:43:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13694) Update README files for RichFaces 4.5.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13694: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Update README files for RichFaces 4.5.x > --------------------------------------- > > Key: RF-13694 > URL: https://issues.jboss.org/browse/RF-13694 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Priority: Minor > Fix For: 4.5.0.Alpha3 > > > {{README.md}} and {{dist/src/main/resources/txt/readme.txt}} need to be updated with RichFaces 4.5.x. > For {{README.md}} e.g.: > * change of the title to RichFaces 4.5 > * remove "New approach to styling based on LESS" > * alter "Smooth Migration from RF4 to RF5" > and other -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:45:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:45:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13696) Port fix for RF-13685 - ExtendedPartialViewContext.release causes IllegalStateException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13696: ------------------------------- Fix Version/s: 5-Tracking > Port fix for RF-13685 - ExtendedPartialViewContext.release causes IllegalStateException > --------------------------------------------------------------------------------------- > > Key: RF-13696 > URL: https://issues.jboss.org/browse/RF-13696 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha3 > Reporter: Juraj H?ska > Fix For: 5-Tracking > > > This issues was resolved in 4.5.0.Alpha3. Please consider porting of the fix to 5.x branch as well. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:47:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:47:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13703) Nested UIDataAdaptor restoring stale data because of reentrancy problem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13703: ------------------------------- Description: I am encountering a reentrancy problem with nested UIDataAdaptor components. For instance something like : {code} {code} When a view contains nested UIDataAdaptor components, each UIDataAdaptor component has its own internal store for saving the saved state of child components (saveChildState/restoreChildState). Since "inputText" is included in both tables, each one may save and restore the value of the component in its internal store. For instance, when "outer" is on key 0 and inner is on key "2", both "outer" and "inner" may store the state values for myText "outer:0:inner:2:myText" in their "childState" property. I guess that most of the time, only "inner" will actually store useful values, because most of calls on "setRowKey" for outer will be done when "inner" has its rowkey set to null. Unfortunately, this is not always the case. For instance, if I decide to visit the component tree while processing an event for "myText", outer will perform a setRowKey while inner has its own rowKey to a significant value (for instance, 2), the result being that inner's value will be erased by outer's. To try and explain with a little more detail... Let's say that we are processing an event on "outer:1:inner:0:myText", and we start a (nested) visit of the tree : 1) "outer" will at some point perform a setRowKey(0) 2) It will then do a restoreChildState for myText. since "inner" has rowKey set to 0, it will restore "outer's" value for "outer:0:inner:0:myText". 3) A bit later on during the visit, inner will do "setRowKey(0)". It will first save the current value for "outer:0:inner:0:myText" (which comes from outer's backup of it, restored on step 2) The result of this process is that "outer"'s backup of "outer:0:inner:0:myText" overwrites "inner"'s backup for it. This is problematic because this leads, sometimes, to an old and obsolete backup of state taking place of the current value. This may happen several HTTP requests later. I've found a solution for this problem by not storing the saved state in the UIDataAdaptor, but in the target component itself. In this manner, there can only be one backup of the data. Such a modification is actually hinted at in UIDataAdaptor's source code : "// TODO - use local map - children save their state themselves using visitors", although my modification is simpler (it's still UIDataAdaptor that saves the state, in the same manner, only in a different place). This bug is quite complex and extracting a testcase will take some time, but I am willing to do so if requested. I can also offer my patch for the problem once I have finalized it. was: I am encountering a reentrancy problem with nested UIDataAdaptor components. For instance something like : When a view contains nested UIDataAdaptor components, each UIDataAdaptor component has its own internal store for saving the saved state of child components (saveChildState/restoreChildState). Since "inputText" is included in both tables, each one may save and restore the value of the component in its internal store. For instance, when "outer" is on key 0 and inner is on key "2", both "outer" and "inner" may store the state values for myText "outer:0:inner:2:myText" in their "childState" property. I guess that most of the time, only "inner" will actually store useful values, because most of calls on "setRowKey" for outer will be done when "inner" has its rowkey set to null. Unfortunately, this is not always the case. For instance, if I decide to visit the component tree while processing an event for "myText", outer will perform a setRowKey while inner has its own rowKey to a significant value (for instance, 2), the result being that inner's value will be erased by outer's. To try and explain with a little more detail... Let's say that we are processing an event on "outer:1:inner:0:myText", and we start a (nested) visit of the tree : 1) "outer" will at some point perform a setRowKey(0) 2) It will then do a restoreChildState for myText. since "inner" has rowKey set to 0, it will restore "outer's" value for "outer:0:inner:0:myText". 3) A bit later on during the visit, inner will do "setRowKey(0)". It will first save the current value for "outer:0:inner:0:myText" (which comes from outer's backup of it, restored on step 2) The result of this process is that "outer"'s backup of "outer:0:inner:0:myText" overwrites "inner"'s backup for it. This is problematic because this leads, sometimes, to an old and obsolete backup of state taking place of the current value. This may happen several HTTP requests later. I've found a solution for this problem by not storing the saved state in the UIDataAdaptor, but in the target component itself. In this manner, there can only be one backup of the data. Such a modification is actually hinted at in UIDataAdaptor's source code : "// TODO - use local map - children save their state themselves using visitors", although my modification is simpler (it's still UIDataAdaptor that saves the state, in the same manner, only in a different place). This bug is quite complex and extracting a testcase will take some time, but I am willing to do so if requested. I can also offer my patch for the problem once I have finalized it. > Nested UIDataAdaptor restoring stale data because of reentrancy problem > ----------------------------------------------------------------------- > > Key: RF-13703 > URL: https://issues.jboss.org/browse/RF-13703 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Environment: (Windows 7. Java 6. Jetty 7.6.9 or Tomcat 6.0.37) > Reporter: Yannick Valot > > I am encountering a reentrancy problem with nested UIDataAdaptor components. For instance something like : > {code} > > > > > > {code} > When a view contains nested UIDataAdaptor components, each UIDataAdaptor component has its own internal store for saving the saved state of child components (saveChildState/restoreChildState). Since "inputText" is included in both tables, each one may save and restore the value of the component in its internal store. > For instance, when "outer" is on key 0 and inner is on key "2", both "outer" and "inner" may store the state values for myText "outer:0:inner:2:myText" in their "childState" property. > I guess that most of the time, only "inner" will actually store useful values, because most of calls on "setRowKey" for outer will be done when "inner" has its rowkey set to null. Unfortunately, this is not always the case. > For instance, if I decide to visit the component tree while processing an event for "myText", outer will perform a setRowKey while inner has its own rowKey to a significant value (for instance, 2), the result being that inner's value will be erased by > outer's. > To try and explain with a little more detail... Let's say that we are processing an event on "outer:1:inner:0:myText", and we start a (nested) visit of the tree : > 1) "outer" will at some point perform a setRowKey(0) > 2) It will then do a restoreChildState for myText. since "inner" has rowKey set to 0, it will restore "outer's" value for "outer:0:inner:0:myText". > 3) A bit later on during the visit, inner will do "setRowKey(0)". It will first save the current value for "outer:0:inner:0:myText" (which comes from outer's backup of it, restored on step 2) > The result of this process is that "outer"'s backup of "outer:0:inner:0:myText" overwrites "inner"'s backup for it. This is problematic because this leads, sometimes, to an old and obsolete backup > of state taking place of the current value. This may happen several HTTP requests later. > I've found a solution for this problem by not storing the saved state in the UIDataAdaptor, but in the target component itself. In this manner, there can only be one backup of the data. Such a modification is actually hinted at in UIDataAdaptor's source code : "// TODO - use local map - children save their state themselves using visitors", although my modification is simpler > (it's still UIDataAdaptor that saves the state, in the same manner, only in a different place). > This bug is quite complex and extracting a testcase will take some time, but I am willing to do so if requested. I can also offer my patch for the problem once I have finalized it. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:47:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:47:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13703) Nested UIDataAdaptor restoring stale data because of reentrancy problem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13703: ------------------------------- Fix Version/s: 4.5-Tracking > Nested UIDataAdaptor restoring stale data because of reentrancy problem > ----------------------------------------------------------------------- > > Key: RF-13703 > URL: https://issues.jboss.org/browse/RF-13703 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Environment: (Windows 7. Java 6. Jetty 7.6.9 or Tomcat 6.0.37) > Reporter: Yannick Valot > Fix For: 4.5-Tracking > > > I am encountering a reentrancy problem with nested UIDataAdaptor components. For instance something like : > {code} > > > > > > {code} > When a view contains nested UIDataAdaptor components, each UIDataAdaptor component has its own internal store for saving the saved state of child components (saveChildState/restoreChildState). Since "inputText" is included in both tables, each one may save and restore the value of the component in its internal store. > For instance, when "outer" is on key 0 and inner is on key "2", both "outer" and "inner" may store the state values for myText "outer:0:inner:2:myText" in their "childState" property. > I guess that most of the time, only "inner" will actually store useful values, because most of calls on "setRowKey" for outer will be done when "inner" has its rowkey set to null. Unfortunately, this is not always the case. > For instance, if I decide to visit the component tree while processing an event for "myText", outer will perform a setRowKey while inner has its own rowKey to a significant value (for instance, 2), the result being that inner's value will be erased by > outer's. > To try and explain with a little more detail... Let's say that we are processing an event on "outer:1:inner:0:myText", and we start a (nested) visit of the tree : > 1) "outer" will at some point perform a setRowKey(0) > 2) It will then do a restoreChildState for myText. since "inner" has rowKey set to 0, it will restore "outer's" value for "outer:0:inner:0:myText". > 3) A bit later on during the visit, inner will do "setRowKey(0)". It will first save the current value for "outer:0:inner:0:myText" (which comes from outer's backup of it, restored on step 2) > The result of this process is that "outer"'s backup of "outer:0:inner:0:myText" overwrites "inner"'s backup for it. This is problematic because this leads, sometimes, to an old and obsolete backup > of state taking place of the current value. This may happen several HTTP requests later. > I've found a solution for this problem by not storing the saved state in the UIDataAdaptor, but in the target component itself. In this manner, there can only be one backup of the data. Such a modification is actually hinted at in UIDataAdaptor's source code : "// TODO - use local map - children save their state themselves using visitors", although my modification is simpler > (it's still UIDataAdaptor that saves the state, in the same manner, only in a different place). > This bug is quite complex and extracting a testcase will take some time, but I am willing to do so if requested. I can also offer my patch for the problem once I have finalized it. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:49:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:49:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13703) Nested UIDataAdaptor restoring stale data because of reentrancy problem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980772#comment-12980772 ] Brian Leathem commented on RF-13703: ------------------------------------ Thanks for reporting the issue; I've scheduled this issue for tracking. The use case in which the problem sounds like an uncommon use case - it is unlikely we will get to investigate any time soon. Any work you do on providing a test-case or fix will help greatly in seeing this issue resolved. > Nested UIDataAdaptor restoring stale data because of reentrancy problem > ----------------------------------------------------------------------- > > Key: RF-13703 > URL: https://issues.jboss.org/browse/RF-13703 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Environment: (Windows 7. Java 6. Jetty 7.6.9 or Tomcat 6.0.37) > Reporter: Yannick Valot > Fix For: 4.5-Tracking > > > I am encountering a reentrancy problem with nested UIDataAdaptor components. For instance something like : > {code} > > > > > > {code} > When a view contains nested UIDataAdaptor components, each UIDataAdaptor component has its own internal store for saving the saved state of child components (saveChildState/restoreChildState). Since "inputText" is included in both tables, each one may save and restore the value of the component in its internal store. > For instance, when "outer" is on key 0 and inner is on key "2", both "outer" and "inner" may store the state values for myText "outer:0:inner:2:myText" in their "childState" property. > I guess that most of the time, only "inner" will actually store useful values, because most of calls on "setRowKey" for outer will be done when "inner" has its rowkey set to null. Unfortunately, this is not always the case. > For instance, if I decide to visit the component tree while processing an event for "myText", outer will perform a setRowKey while inner has its own rowKey to a significant value (for instance, 2), the result being that inner's value will be erased by > outer's. > To try and explain with a little more detail... Let's say that we are processing an event on "outer:1:inner:0:myText", and we start a (nested) visit of the tree : > 1) "outer" will at some point perform a setRowKey(0) > 2) It will then do a restoreChildState for myText. since "inner" has rowKey set to 0, it will restore "outer's" value for "outer:0:inner:0:myText". > 3) A bit later on during the visit, inner will do "setRowKey(0)". It will first save the current value for "outer:0:inner:0:myText" (which comes from outer's backup of it, restored on step 2) > The result of this process is that "outer"'s backup of "outer:0:inner:0:myText" overwrites "inner"'s backup for it. This is problematic because this leads, sometimes, to an old and obsolete backup > of state taking place of the current value. This may happen several HTTP requests later. > I've found a solution for this problem by not storing the saved state in the UIDataAdaptor, but in the target component itself. In this manner, there can only be one backup of the data. Such a modification is actually hinted at in UIDataAdaptor's source code : "// TODO - use local map - children save their state themselves using visitors", although my modification is simpler > (it's still UIDataAdaptor that saves the state, in the same manner, only in a different place). > This bug is quite complex and extracting a testcase will take some time, but I am willing to do so if requested. I can also offer my patch for the problem once I have finalized it. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:53:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:53:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13704) Add link to rich:layout successor layout:layout In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13704. -------------------------------- Labels: (was: richfaces) Resolution: Rejected As per the notes in the wiki article "Layout component is not official RichFaces component", and there is no plan to do so as the component is largely obsolete with JSF 2. You can ask the wiki article author [~Strannik] to provide a link in his wiki article. > Add link to rich:layout successor layout:layout > ----------------------------------------------- > > Key: RF-13704 > URL: https://issues.jboss.org/browse/RF-13704 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: migration, third-party > Reporter: Kalle Richter > Priority: Trivial > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The 3.3.x -> 4.x migration guide at https://community.jboss.org/wiki/RichFaces33-4xMigrationGuideUnleashed states that rich:layout has been replaced by/moved to the third-party project/namespace layout:layout. Where can it be found? Please add a link in the guide directly or an explanation if necessary as $SEARCH_ENGINE doesn't seem to find anything useful. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:53:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:53:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13705) Clearify the relation between leaf and nodes attribute of rich:treeModelAdaptor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13705: ------------------------------- Fix Version/s: 4.5-Tracking > Clearify the relation between leaf and nodes attribute of rich:treeModelAdaptor > ------------------------------------------------------------------------------- > > Key: RF-13705 > URL: https://issues.jboss.org/browse/RF-13705 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.7 > Reporter: Kalle Richter > Fix For: 4.5-Tracking > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The javadoc states that both attributes are responsible for determining leafs, but there's no statement about what happens if they're both specified and - if it is possible to specify both - which takes precedence. > It is currently not possible to get started with rich:tree due to missing demos (see https://issues.jboss.org/browse/RF-13050), so I consider this rather important. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:55:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:55:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980774#comment-12980774 ] Brian Leathem commented on RF-13706: ------------------------------------ RichFaces 4.3.7 is not compatible with JSF 2.2 / WildFly 8. Can you please verify that you observe this behaviour with a recent RichFaces 4.5 SNAPSHOT? (We'll have a RichFaces 4.5.0.Alpha3 release available in a couple of weeks). > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Labels: waiting_on_user > Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:55:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:55:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13706: ------------------------------- Labels: waiting_on_user (was: ) > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Labels: waiting_on_user > Attachments: queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:57:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:57:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13707) Photoalbum: incorrect account details shown after creating a new one In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13707: ------------------------------- Fix Version/s: 4.5-Tracking > Photoalbum: incorrect account details shown after creating a new one > -------------------------------------------------------------------- > > Key: RF-13707 > URL: https://issues.jboss.org/browse/RF-13707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.8 > Reporter: Juraj H?ska > Labels: photoalbum > Fix For: 4.5-Tracking > > > When user create a new account in Photoalbum application there are shown account details, which are incorrect: > * missing login, first name, surname > * wrong sex value (there is always female - I tried other than my photos as avatars, so the problem will be somewhere else :) ) > * missing Birthday and email -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 14:57:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 14:57:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13708) Photoalbum: refresh over index page throws error In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13708: ------------------------------- Fix Version/s: 4.5-Tracking > Photoalbum: refresh over index page throws error > ------------------------------------------------ > > Key: RF-13708 > URL: https://issues.jboss.org/browse/RF-13708 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.8 > Environment: container: JBoss EAP 6.3.0.ER8, other EAPS as well > browsers: all > Reporter: Juraj H?ska > Labels: photoalbum > Fix For: 4.5-Tracking > > > Refresh over index page of Photoalbum throws: > {code} > 14:31:05,563 SEVERE [javax.enterprise.resource.webcontainer.jsf.renderkit] (http-/127.0.0.1:8080-5) javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. : javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. > at com.sun.faces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.28.Final-redhat-1.jar:2.1.28.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > {code} > After this error application cease to work. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:09:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:09:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13675) Showcase: chart component improvements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13675: ---------------------------------- Assignee: Brian Leathem (was: Luk?? Macko) > Showcase: chart component improvements > -------------------------------------- > > Key: RF-13675 > URL: https://issues.jboss.org/browse/RF-13675 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Luk?? Macko > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.5.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:09:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:09:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13651) Integration tests failing in chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13651: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > Integration tests failing in chrome > ----------------------------------- > > Key: RF-13651 > URL: https://issues.jboss.org/browse/RF-13651 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Matej Novotny > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The framework tests pass in phantomjs but some fail in chrome. > Resolution of this issue involves running and stabilizing the tests in all supported browsers. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:11:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:11:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13660) RichFaces 4.5 integration tests - error after test execution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13660: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > RichFaces 4.5 integration tests - error after test execution > ------------------------------------------------------------ > > Key: RF-13660 > URL: https://issues.jboss.org/browse/RF-13660 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Environment: AS: Wildfly > Browser: PhantomJS > Reporter: Matej Novotny > Assignee: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > This issue originated from RF-13591. > There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/src/test/integration/org/richfaces/integration/resource/ITResourceMapping.java]. > The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines. > Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5/56/console]. > The exception in server console is: > {code} > 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException > at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:] > at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:] > at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:] > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] > at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:] > at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:11:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:11:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13673) Backport the plain skin fix from RF 5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13673: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Backport the plain skin fix from RF 5 > ------------------------------------- > > Key: RF-13673 > URL: https://issues.jboss.org/browse/RF-13673 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: skinning > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Backport RF-11103. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:11:27 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:11:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13675) Showcase: chart component improvements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13675: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Showcase: chart component improvements > -------------------------------------- > > Key: RF-13675 > URL: https://issues.jboss.org/browse/RF-13675 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Luk?? Macko > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:11:27 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:11:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13678) Render @all does not work for nested a4j:region in collapsibleSubTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13678: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Render @all does not work for nested a4j:region in collapsibleSubTable > ---------------------------------------------------------------------- > > Key: RF-13678 > URL: https://issues.jboss.org/browse/RF-13678 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Suppose nested {{regions}} in a {{collapsibleSubTable}}. > Those regions are not updated when a {{commandButton}} with {{render}} attribute set to {{@all}} is submitted. > IMHO it is somehow connected with RF-13677, however, this issue occurs only with combination of {{regions}} and {{collapsibleSubTable}}, other iteration components works in this matter. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:11:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:11:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13585) Re-factor the components demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13585: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Re-factor the components demo to work with RichFaces 4.5 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:11:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:11:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13653) Update component namespaces in 4.5 examples In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13653: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Update component namespaces in 4.5 examples > ------------------------------------------- > > Key: RF-13653 > URL: https://issues.jboss.org/browse/RF-13653 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > With the exception of showcase, all examples use the r namespace, it needs to be changed back to a4j/rich. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:11:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:11:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13682) Stateless view: CSS stylesheets not included in head after form submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13682: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > Stateless view: CSS stylesheets not included in head after form submit > ---------------------------------------------------------------------- > > Key: RF-13682 > URL: https://issues.jboss.org/browse/RF-13682 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: OpenSuse 13.1 x64 > OpenJDK 1.7.0_51 > Apache Tomcat 8.0.8 > JSF: org.glassfish:javax.faces:2.1.28 > Reporter: Tony Cramer > Fix For: 4.5.0.Alpha3 > > Attachments: rf-demo-skinning.zip, rf-demo-skinning_and_style.zip > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If view is stateless Issue 1. skinning.css is not included after submitting a form at all. > Issue 2. Any other stylesheets manually included with h:outputStylesheet are not included in head but in body after submit. > Maven project reproducing the issue attached. > Please use "rf-demo-skinning_and_style.zip" - reproduces both issues. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:27 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:27 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13687: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > TabPanel header is not updated after switching of tabs > ------------------------------------------------------ > > Key: RF-13687 > URL: https://issues.jboss.org/browse/RF-13687 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3, 5.0.0.Alpha4 > Reporter: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13651) Integration tests failing in chrome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13651: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 3, 4.5.0.Alpha3 - Sprint 4, 4.5.0.Alpha3 - Sprint 5 (was: 4.5.0.Alpha3 - Sprint 3, 4.5.0.Alpha3 - Sprint 4) > Integration tests failing in chrome > ----------------------------------- > > Key: RF-13651 > URL: https://issues.jboss.org/browse/RF-13651 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Brian Leathem > Assignee: Matej Novotny > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The framework tests pass in phantomjs but some fail in chrome. > Resolution of this issue involves running and stabilizing the tests in all supported browsers. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:28 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13660) RichFaces 4.5 integration tests - error after test execution In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13660: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4, 4.5.0.Alpha3 - Sprint 5 (was: 4.5.0.Alpha3 - Sprint 4) > RichFaces 4.5 integration tests - error after test execution > ------------------------------------------------------------ > > Key: RF-13660 > URL: https://issues.jboss.org/browse/RF-13660 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha2 > Environment: AS: Wildfly > Browser: PhantomJS > Reporter: Matej Novotny > Assignee: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > This issue originated from RF-13591. > There is an error in server log after execution of [ITResourceMapping|https://github.com/richfaces/richfaces/blob/4.5.x/core/src/test/integration/org/richfaces/integration/resource/ITResourceMapping.java]. > The test itself passes (use PhantomJS) and afterwards there is an error in server console. This does not affect the build as everything gets completed however it results in Jenkins job failure on some machines. > Currently the Jenkins job passes (machine running the tests was changed) but before it was failing after execution of this particular test. See the [Jenkins job resulsts|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/4.5/job/richfaces-4.5/56/console]. > The exception in server console is: > {code} > 12:36:37,481 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.NullPointerException > at org.richfaces.application.ServiceTracker.release(ServiceTracker.java:135) [richfaces.jar:] > at org.richfaces.application.InitializationListener.onStop(InitializationListener.java:93) [richfaces.jar:] > at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:165) [richfaces.jar:] > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.5.jar:2.2.5] > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.5-jbossorg-3.jar:] > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) [jsf-impl-2.2.5-jbossorg-3.jar:] > at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.0.Final.jar:8.0.0.Final] > at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:314) [jsf-impl-2.2.5-jbossorg-3.jar:] > at io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:185) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:216) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:557) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stopContext(UndertowDeploymentService.java:117) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:100) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13673) Backport the plain skin fix from RF 5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13673: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4, 4.5.0.Alpha3 - Sprint 5 (was: 4.5.0.Alpha3 - Sprint 4) > Backport the plain skin fix from RF 5 > ------------------------------------- > > Key: RF-13673 > URL: https://issues.jboss.org/browse/RF-13673 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: skinning > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Backport RF-11103. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13675) Showcase: chart component improvements In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13675: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4, 4.5.0.Alpha3 - Sprint 5 (was: 4.5.0.Alpha3 - Sprint 4) > Showcase: chart component improvements > -------------------------------------- > > Key: RF-13675 > URL: https://issues.jboss.org/browse/RF-13675 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Luk?? Macko > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:29 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:29 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13678) Render @all does not work for nested a4j:region in collapsibleSubTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13678: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 4, 4.5.0.Alpha3 - Sprint 5 (was: 4.5.0.Alpha3 - Sprint 4) > Render @all does not work for nested a4j:region in collapsibleSubTable > ---------------------------------------------------------------------- > > Key: RF-13678 > URL: https://issues.jboss.org/browse/RF-13678 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Assignee: Michal Petrov > Labels: regression > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Suppose nested {{regions}} in a {{collapsibleSubTable}}. > Those regions are not updated when a {{commandButton}} with {{render}} attribute set to {{@all}} is submitted. > IMHO it is somehow connected with RF-13677, however, this issue occurs only with combination of {{regions}} and {{collapsibleSubTable}}, other iteration components works in this matter. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:30 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:30 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13583) Backport the chart components to RichFaces 4.5 components module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13583: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 1, 4.5.0.Alpha3 - Sprint 2, 4.5.0.Alpha3 - Sprint 3, 4.5.0.Alpha3 - Sprint 5 (was: 4.5.0.Alpha3 - Sprint 1, 4.5.0.Alpha3 - Sprint 2, 4.5.0.Alpha3 - Sprint 3) > Backport the chart components to RichFaces 4.5 components module > ---------------------------------------------------------------- > > Key: RF-13583 > URL: https://issues.jboss.org/browse/RF-13583 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Luk?? Macko > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Backport the chart components to RichFaces 4.5 components module -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:30 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:30 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13597) Drag and drop support for file upload In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13597: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 2, 4.5.0.Alpha3 - Sprint 5 (was: 4.5.0.Alpha3 - Sprint 2) > Drag and drop support for file upload > ------------------------------------- > > Key: RF-13597 > URL: https://issues.jboss.org/browse/RF-13597 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.1.0.Final > Reporter: abhishek vijra > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Drag/Drop support should be added to file upload component . > Like the primefaces fileUploadDnd : http://www.primefaces.org/showcase/ui/fileUploadDnd.jsf -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:30 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:30 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13585) Re-factor the components demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13585: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 1, 4.5.0.Alpha3 - Sprint 5 (was: 4.5.0.Alpha3 - Sprint 1) > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Re-factor the components demo to work with RichFaces 4.5 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:31 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:31 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13653) Update component namespaces in 4.5 examples In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13653: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 5 > Update component namespaces in 4.5 examples > ------------------------------------------- > > Key: RF-13653 > URL: https://issues.jboss.org/browse/RF-13653 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > With the exception of showcase, all examples use the r namespace, it needs to be changed back to a4j/rich. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:31 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:31 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13652) Forward port the 4.3.7 fixes into the 4.5.x branch In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13652: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 3, 4.5.0.Alpha3 - Sprint 5 (was: 4.5.0.Alpha3 - Sprint 3) > Forward port the 4.3.7 fixes into the 4.5.x branch > -------------------------------------------------- > > Key: RF-13652 > URL: https://issues.jboss.org/browse/RF-13652 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:31 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:31 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13664) EDT firstChild call will return a text element when the source code is formatted to have one element per line In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13664: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 3, 4.5.0.Alpha3 - Sprint 5 (was: 4.5.0.Alpha3 - Sprint 3) > EDT firstChild call will return a text element when the source code is formatted to have one element per line > ------------------------------------------------------------------------------------------------------------- > > Key: RF-13664 > URL: https://issues.jboss.org/browse/RF-13664 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Formatting the generated html and viewing the result in chrome leads to an error in the EDT call: > {{this.frozenHeaderPartElement.firstChild.rows}}. This is because when the element is followed by a newline, a text element is returned from the firstChild call. > Some solutions to this are discussed in the stackoverflow question: > http://stackoverflow.com/questions/2299807/element-firstchild-is-returning-textnode-instead-of-an-object-in-ff > I recommend we use jQuery here to resolve the first child in a cross-browser way. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:32 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:32 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13682) Stateless view: CSS stylesheets not included in head after form submit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13682: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 5 > Stateless view: CSS stylesheets not included in head after form submit > ---------------------------------------------------------------------- > > Key: RF-13682 > URL: https://issues.jboss.org/browse/RF-13682 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: OpenSuse 13.1 x64 > OpenJDK 1.7.0_51 > Apache Tomcat 8.0.8 > JSF: org.glassfish:javax.faces:2.1.28 > Reporter: Tony Cramer > Fix For: 4.5.0.Alpha3 > > Attachments: rf-demo-skinning.zip, rf-demo-skinning_and_style.zip > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If view is stateless Issue 1. skinning.css is not included after submitting a form at all. > Issue 2. Any other stylesheets manually included with h:outputStylesheet are not included in head but in body after submit. > Maven project reproducing the issue attached. > Please use "rf-demo-skinning_and_style.zip" - reproduces both issues. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:32 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:32 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13687: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 5 > TabPanel header is not updated after switching of tabs > ------------------------------------------------------ > > Key: RF-13687 > URL: https://issues.jboss.org/browse/RF-13687 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3, 5.0.0.Alpha4 > Reporter: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13690) DataTable in uiRepeat - scrolling in table makes columns unsorted again In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13690: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > DataTable in uiRepeat - scrolling in table makes columns unsorted again > ----------------------------------------------------------------------- > > Key: RF-13690 > URL: https://issues.jboss.org/browse/RF-13690 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When {{DataTable}} is nested in {{uiRepeat}}, then scrolling over the table with {{dataScroller}} makes sorting according to some column broken - the columns are unsorted. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13691) EDT in uiRepeat - selection corrupted in multiple paged table In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13691: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > EDT in uiRepeat - selection corrupted in multiple paged table > ------------------------------------------------------------- > > Key: RF-13691 > URL: https://issues.jboss.org/browse/RF-13691 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When {{EDT}} is in {{uiRepeat}} and has multiple pages, then selection of rows functionality does not work as expected. > It seems that there is a problem with row indices. Please see steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13692) Photoalbum can not be deployed to WildFly 8.0.x or 8.1.x due to Weld exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13692: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Photoalbum can not be deployed to WildFly 8.0.x or 8.1.x due to Weld exception > ------------------------------------------------------------------------------ > > Key: RF-13692 > URL: https://issues.jboss.org/browse/RF-13692 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > There is an error during deployment of Photoalbum example on WildFly 8.1.0.Final or 8.0.0.Final > {code} > 09:28:51,675 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getBeans() is not available during application initialization > at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerValidated(BeanManagerProxy.java:159) > at org.jboss.weld.bean.builtin.BeanManagerProxy.getBeans(BeanManagerProxy.java:91) > at org.jboss.solder.core.CoreExtension.failIfWeldExtensionsDetected(CoreExtension.java:215) > at org.jboss.solder.core.CoreExtension.afterBeanDiscovery(CoreExtension.java:208) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:266) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:125) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:232) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:169) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:128) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:102) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:63) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:35) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:55) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:372) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:79) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:37) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:55) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:372) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:79) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > ... 3 more > {code} > and > {code} > JBAS014775: New missing/unsatisfied dependencies: > service jboss.deployment.unit."richfaces-photoalbum.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService, JBAS014799: ... and 23 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService, JBAS014799: ... and 22 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.VIEW."org.richfaces.photoalbum.model.actions.IAlbumAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.VIEW."org.richfaces.photoalbum.model.actions.IEventAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.VIEW."org.richfaces.photoalbum.model.actions.IImageAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.VIEW."org.richfaces.photoalbum.search.ISearchAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.VIEW."org.richfaces.photoalbum.model.actions.IShelfAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.VIEW."org.richfaces.photoalbum.model.actions.IUserAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START, service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START, JBAS014799: ... and 16 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START, JBAS014799: ... and 4 more ] > service jboss.persistenceunit."richfaces-photoalbum.war#photoAlbum" (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START, service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService, JBAS014799: ... and 13 more ] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > {code} > Note that it *works* on EAP 6.2.3.GA and EAP 6.3.0.ER8 > Both WildFly containers use Weld 2.1.x, so it is not a problem with Weld 2.2.x integration. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13694) Update README files for RichFaces 4.5.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13694: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Update README files for RichFaces 4.5.x > --------------------------------------- > > Key: RF-13694 > URL: https://issues.jboss.org/browse/RF-13694 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Priority: Minor > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > {{README.md}} and {{dist/src/main/resources/txt/readme.txt}} need to be updated with RichFaces 4.5.x. > For {{README.md}} e.g.: > * change of the title to RichFaces 4.5 > * remove "New approach to styling based on LESS" > * alter "Smooth Migration from RF4 to RF5" > and other -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13694) Update README files for RichFaces 4.5.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13694: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 6 > Update README files for RichFaces 4.5.x > --------------------------------------- > > Key: RF-13694 > URL: https://issues.jboss.org/browse/RF-13694 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Priority: Minor > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > {{README.md}} and {{dist/src/main/resources/txt/readme.txt}} need to be updated with RichFaces 4.5.x. > For {{README.md}} e.g.: > * change of the title to RichFaces 4.5 > * remove "New approach to styling based on LESS" > * alter "Smooth Migration from RF4 to RF5" > and other -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13698) RF 4.5 Chart title does not render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13698: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > RF 4.5 Chart title does not render > ---------------------------------- > > Key: RF-13698 > URL: https://issues.jboss.org/browse/RF-13698 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > FF/Chrome > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The title of the chart is not rendered above the chart. This affects all kinds of charts, eg. line, pie and bar. > I created Metamer samples of charts for 4.5.x where this can be tested (not automatically until public JS API for charts will be available). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:36 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13699) RF 4.5 Chart attribute 'zoom' does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13699: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > RF 4.5 Chart attribute 'zoom' does not work > ------------------------------------------- > > Key: RF-13699 > URL: https://issues.jboss.org/browse/RF-13699 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > Latest Chrome/FF > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The attribute 'zoom' does not work, setting it to true has no effect and user cannot zoom the chart. This attribute is only available for line chart. > I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:36 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13701) RF 4.5 Bar chart plotClick malfunctioning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13701: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > RF 4.5 Bar chart plotClick malfunctioning > ----------------------------------------- > > Key: RF-13701 > URL: https://issues.jboss.org/browse/RF-13701 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > Latest Chrome/FF > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When interacting with bar chart where {{onplotclick}} and {{plotClickListener}} are set, it does not react when last bar in the series is clicked (eg .no request is sent for server side event and no JS executed for onplotclick). See steps to reproduce, in case they are not clear ask me for more details. > I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13690) DataTable in uiRepeat - scrolling in table makes columns unsorted again In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13690: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 5 > DataTable in uiRepeat - scrolling in table makes columns unsorted again > ----------------------------------------------------------------------- > > Key: RF-13690 > URL: https://issues.jboss.org/browse/RF-13690 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When {{DataTable}} is nested in {{uiRepeat}}, then scrolling over the table with {{dataScroller}} makes sorting according to some column broken - the columns are unsorted. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13691) EDT in uiRepeat - selection corrupted in multiple paged table In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13691: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 5 > EDT in uiRepeat - selection corrupted in multiple paged table > ------------------------------------------------------------- > > Key: RF-13691 > URL: https://issues.jboss.org/browse/RF-13691 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Labels: regression > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When {{EDT}} is in {{uiRepeat}} and has multiple pages, then selection of rows functionality does not work as expected. > It seems that there is a problem with row indices. Please see steps to reproduce. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13692) Photoalbum can not be deployed to WildFly 8.0.x or 8.1.x due to Weld exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13692: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 5 > Photoalbum can not be deployed to WildFly 8.0.x or 8.1.x due to Weld exception > ------------------------------------------------------------------------------ > > Key: RF-13692 > URL: https://issues.jboss.org/browse/RF-13692 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj H?ska > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > There is an error during deployment of Photoalbum example on WildFly 8.1.0.Final or 8.0.0.Final > {code} > 09:28:51,675 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getBeans() is not available during application initialization > at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerValidated(BeanManagerProxy.java:159) > at org.jboss.weld.bean.builtin.BeanManagerProxy.getBeans(BeanManagerProxy.java:91) > at org.jboss.solder.core.CoreExtension.failIfWeldExtensionsDetected(CoreExtension.java:215) > at org.jboss.solder.core.CoreExtension.afterBeanDiscovery(CoreExtension.java:208) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:266) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:125) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:253) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:232) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:169) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:128) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:102) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:63) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:35) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:55) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:372) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:79) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:37) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:55) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:372) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:79) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:92) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > ... 3 more > {code} > and > {code} > JBAS014775: New missing/unsatisfied dependencies: > service jboss.deployment.unit."richfaces-photoalbum.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService, JBAS014799: ... and 23 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService, JBAS014799: ... and 22 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.VIEW."org.richfaces.photoalbum.model.actions.IAlbumAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.VIEW."org.richfaces.photoalbum.model.actions.IEventAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.VIEW."org.richfaces.photoalbum.model.actions.IImageAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.VIEW."org.richfaces.photoalbum.search.ISearchAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.SearchAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.VIEW."org.richfaces.photoalbum.model.actions.IShelfAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.ShelfAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.VIEW."org.richfaces.photoalbum.model.actions.IUserAction".LOCAL (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.WeldInstantiator] > service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."com.sun.faces.config.ConfigureListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.VersionBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."managed-bean.org.richfaces.skin.SkinBean".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.resourceLoader.servlet.ResourceListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeFilter".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.exception.CatchExceptionFilter".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldInitialListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] > service jboss.deployment.unit."richfaces-photoalbum.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > service jboss.deployment.unit."richfaces-photoalbum.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START, service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.UserAction.START, JBAS014799: ... and 16 more ] > service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."richfaces-photoalbum.war".component.AlbumAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.ImageAction.START, service jboss.deployment.unit."richfaces-photoalbum.war".component.EventAction.START, JBAS014799: ... and 4 more ] > service jboss.persistenceunit."richfaces-photoalbum.war#photoAlbum" (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".component."org.jboss.solder.servlet.event.ServletEventBridgeServlet".START, service jboss.deployment.unit."richfaces-photoalbum.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService, JBAS014799: ... and 13 more ] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum (missing) dependents: [service jboss.deployment.unit."richfaces-photoalbum.war".deploymentCompleteService] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum] > service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./richfaces-photoalbum.UndertowDeploymentInfoService] > {code} > Note that it *works* on EAP 6.2.3.GA and EAP 6.3.0.ER8 > Both WildFly containers use Weld 2.1.x, so it is not a problem with Weld 2.2.x integration. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13698) RF 4.5 Chart title does not render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13698: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 5 > RF 4.5 Chart title does not render > ---------------------------------- > > Key: RF-13698 > URL: https://issues.jboss.org/browse/RF-13698 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > FF/Chrome > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The title of the chart is not rendered above the chart. This affects all kinds of charts, eg. line, pie and bar. > I created Metamer samples of charts for 4.5.x where this can be tested (not automatically until public JS API for charts will be available). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13699) RF 4.5 Chart attribute 'zoom' does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13699: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 5 > RF 4.5 Chart attribute 'zoom' does not work > ------------------------------------------- > > Key: RF-13699 > URL: https://issues.jboss.org/browse/RF-13699 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > Latest Chrome/FF > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The attribute 'zoom' does not work, setting it to true has no effect and user cannot zoom the chart. This attribute is only available for line chart. > I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13701) RF 4.5 Bar chart plotClick malfunctioning In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13701: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 5 > RF 4.5 Bar chart plotClick malfunctioning > ----------------------------------------- > > Key: RF-13701 > URL: https://issues.jboss.org/browse/RF-13701 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3 > Environment: Wildfly 8.0 > Latest Chrome/FF > Reporter: Matej Novotny > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When interacting with bar chart where {{onplotclick}} and {{plotClickListener}} are set, it does not react when last bar in the series is clicked (eg .no request is sent for server side event and no JS executed for onplotclick). See steps to reproduce, in case they are not clear ask me for more details. > I created Metamer samples of charts for 4.5.x where this can be tested (only manually for the time being). > This works in RF 5, so this has to be connected to backporting charts component (RF-13583) to 4.5.x. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:13:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 15:13:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13709) Remove the chart components from the RichFaces showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13709: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 5 > Remove the chart components from the RichFaces showcase > ------------------------------------------------------- > > Key: RF-13709 > URL: https://issues.jboss.org/browse/RF-13709 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The chart components need additional work to function in a mobile environment. In the mean time we should remove them from the mobile showcase. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 15:57:24 2014 From: issues at jboss.org (Marcel Kolsteren (JIRA)) Date: Mon, 30 Jun 2014 15:57:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kolsteren updated RF-13706: ---------------------------------- Attachment: queuetest-javaee6.zip > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Labels: waiting_on_user > Attachments: queuetest-javaee6.zip, queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 16:13:24 2014 From: issues at jboss.org (Marcel Kolsteren (JIRA)) Date: Mon, 30 Jun 2014 16:13:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980789#comment-12980789 ] Marcel Kolsteren commented on RF-13706: --------------------------------------- In order to verify that the problem also occurs in a context that is supported by RichFaces 4.3.7, I created a Java EE 6 variant of my sample application (see new attachment), deployed it in JBoss EAP 6.2.0.GA (which uses JSF 2.1), and observed the same behavior. Can you direct me to a Maven repository that contains RichFaces 4.5 snapshots? I can't find them in the JBoss repository. > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Labels: waiting_on_user > Attachments: queuetest-javaee6.zip, queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 16:18:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 16:18:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13706: ------------------------------- Labels: (was: waiting_on_user) > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Attachments: queuetest-javaee6.zip, queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 16:20:26 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 16:20:26 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980790#comment-12980790 ] Brian Leathem commented on RF-13706: ------------------------------------ This is great [~marcelkolsteren], thanks for verifying against JSF 2.1. Could you formulate your patch as a RichFaces 4.3 pull request (PR)? We can then review the patch and run our tests to check against regressions from the PR. The git repo is: https://github.com/richfaces4/core Instructions on creating a PR (for RichFaces 5) can be found here: https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Attachments: queuetest-javaee6.zip, queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 16:32:24 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 16:32:24 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13585) Re-factor the components demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13585: ---------------------------------- Assignee: Brian Leathem (was: Juraj H?ska) > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Re-factor the components demo to work with RichFaces 4.5 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 16:32:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 16:32:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13585) Re-factor the components demo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-13585: -------------------------------- > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Re-factor the components demo to work with RichFaces 4.5 -- This message was sent by Atlassian JIRA (v6.2.6#6264) From issues at jboss.org Mon Jun 30 17:46:25 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 30 Jun 2014 17:46:25 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13706: ---------------------------------- Assignee: Juraj H?ska I've reviewed the PR, and it looks reasonable. Please check that it does not introduce any regressions. > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Assignee: Juraj H?ska > Attachments: queuetest-javaee6.zip, queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > > > > > > > > > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264)