From issues at jboss.org Tue Apr 1 04:29:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 1 Apr 2014 04:29:13 -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 ] Pavol Pitonak updated RF-13593: ------------------------------- Steps to Reproduce: # deploy Metamer # open http://localhost:8080/metamer/faces/components/a4jPush/simple.xhtml in IE8 # watch console in Developer Tools > 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: Pavol Pitonak > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 04:31:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 1 Apr 2014 04:31:13 -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 ] Pavol Pitonak reassigned RF-13593: ---------------------------------- Assignee: Brian Leathem (was: Pavol Pitonak) [~bleathem], I was able to reproduce this issue (see Steps to Reproduce). > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 04:33:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 1 Apr 2014 04:33:13 -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 ] Pavol Pitonak updated RF-13593: ------------------------------- Tester: Pavol Pitonak > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 09:01:14 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Tue, 1 Apr 2014 09:01:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13537) Autocomplete: onbegin attribute igniored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958084#comment-12958084 ] Matej Novotny commented on RF-13537: ------------------------------------ In RFPL-2257 I created tests for autocomplete handlers and came across this problem. Automated test for this can be found [here|https://github.com/richfaces/richfaces-qa/blob/4.3.x/metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/richAutocomplete/TestAutocompleteAttributes.java#L119]. > Autocomplete: onbegin attribute igniored > ---------------------------------------- > > Key: RF-13537 > URL: https://issues.jboss.org/browse/RF-13537 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Fix For: 4.3.6 > > > "onbegin" attribute of rich:autocomplete is always ignored! > I suggest next fix: > In file Autocomplete.js: > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > rf.ajax(this.id, event, {parameters: params, error: ajaxError, complete:ajaxSuccess}); > } > {code} > for fixing, we must replace on > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > var parameters_extended = {parameters: params, error: ajaxError, complete:ajaxSuccess}; > if (this.options.onbegin != undefined) { > parameters_extended.begin = this.options.onbegin; > } > rf.ajax(this.id, event, parameters_extended); > } > {code} > I can create pull request if everything ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 10:05:14 2014 From: issues at jboss.org (Thomas Eichberger (JIRA)) Date: Tue, 1 Apr 2014 10:05:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13594) Column width of rich:extendedDataTable with rich:dataScroller In-Reply-To: References: Message-ID: Thomas Eichberger created RF-13594: -------------------------------------- Summary: Column width of rich:extendedDataTable with rich:dataScroller Key: RF-13594 URL: https://issues.jboss.org/browse/RF-13594 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-ScrollableDataTable Affects Versions: 4.2.3.Final Environment: Windows 7 + IE / Firefox Reporter: Thomas Eichberger I implemented a sortable rich:extendedDataTable with its according rich:dataScroller. After the table is filled resizing columns of the table works as supposed. When the page is changed by using the datascroller the column headers remain with the changed width, but the data columns are displayed with default column width. Because of this behavior the table is displayed distorted totally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 10:13:14 2014 From: issues at jboss.org (Thomas Eichberger (JIRA)) Date: Tue, 1 Apr 2014 10:13:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13594) Column width of rich:extendedDataTable with rich:dataScroller In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Eichberger updated RF-13594: ----------------------------------- Attachment: screenshot.png > Column width of rich:extendedDataTable with rich:dataScroller > ------------------------------------------------------------- > > Key: RF-13594 > URL: https://issues.jboss.org/browse/RF-13594 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.2.3.Final > Environment: Windows 7 + IE / Firefox > Reporter: Thomas Eichberger > Attachments: screenshot.png > > > I implemented a sortable rich:extendedDataTable with its according rich:dataScroller. After the table is filled resizing columns of the table works as supposed. When the page is changed by using the datascroller the column headers remain with the changed width, but the data columns are displayed with default column width. Because of this behavior the table is displayed distorted totally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 12:23:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 1 Apr 2014 12:23:13 -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 ] Brian Leathem reopened RF-13160: -------------------------------- Assignee: (was: Brian Leathem) Reopneing for 4.5 > 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 > Fix For: 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 12:23:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 1 Apr 2014 12:23:13 -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 ] Brian Leathem updated RF-13160: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 12:27:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 1 Apr 2014 12:27:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13587) rich:autocomplete - suggestion box doesn't show up at all In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13587: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 2 > rich:autocomplete - suggestion box doesn't show up at all > --------------------------------------------------------- > > Key: RF-13587 > URL: https://issues.jboss.org/browse/RF-13587 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Implementation: JSF-2.2.6 mojarra, Mojarra 2.2.5 > Server: WebLogic 12.1.2.1, WildFly 8.0.0.Final > Browser: Chrome 33, Firefox 27 > Java: 1.7 > Reporter: Amit Tikoo > Labels: richfaces > Fix For: 4.5.0.Alpha3 > > > I am using a component but the suggestion box just doesn't show up. Here is a simple case I'm trying: > XHTML: > {code} > > > > #{station} > > > > {code} > JAVA: > {code} > public List autocomplete1(String request){ > List suggestions = new ArrayList(); > suggestions.add("test 1"); > suggestions.add("test 2"); > suggestions.add("test 3"); > suggestions.add("test 4"); > return suggestions; > } > {code} > This shows up in logging (using ) > {code} > error[14:47:03.644]: Received 'error at malformedXML' event from > error[14:47:03.644]: [status=200] During update: javax.faces.ViewState not found > {code} > Also i can see the suggestion if i switch the mode to "Client" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 12:27:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 1 Apr 2014 12:27:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13591) RichFaces 4.5 not compilable because of integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13591: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 2 > RichFaces 4.5 not compilable because of integration tests > --------------------------------------------------------- > > 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 > Priority: Blocker > Fix For: 4.5.0.Alpha3 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 12:29:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 1 Apr 2014 12:29:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13591) RichFaces 4.5 not compilable because of integration tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13591: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 1 (was: 4.5.0.Alpha3 - Sprint 2) > RichFaces 4.5 not compilable because of integration tests > --------------------------------------------------------- > > 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 > Priority: Blocker > Fix For: 4.5.0.Alpha3 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 17:03:12 2014 From: issues at jboss.org (Michael B (JIRA)) Date: Tue, 1 Apr 2014 17:03:12 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: Michael B created RF-13595: ------------------------------ Summary: rich:validator doesn't work when loaded via ajax (re-render) Key: RF-13595 URL: https://issues.jboss.org/browse/RF-13595 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.3.5 Environment: RF 4.3.5 Mojarra 2.1.27 Java 7 Update 51 x64 Tomcat 7.0.52 Firefox 28.0 + Firebug Reporter: Michael B When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to missing JS function av_xxxxxxxxx. As already described in further detail in a comment to this JIRA here: https://issues.jboss.org/browse/RF-12031 I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText like for example rich:calendar. The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) added on the client side when a component becomes visible on ajax response re-rendering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 17:07:12 2014 From: issues at jboss.org (Michael B (JIRA)) Date: Tue, 1 Apr 2014 17:07:12 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael B updated RF-13595: --------------------------- Attachment: validationTest.zip This is a minimal eclipse project to reproduce the problem. Add RF 4.3.5 jars to WEB-INF/lib folder as well as javax.faces-2.1.27.jar to run the project against tomcat. > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) added on the client side when a component becomes visible on ajax response re-rendering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 17:07:12 2014 From: issues at jboss.org (Michael B (JIRA)) Date: Tue, 1 Apr 2014 17:07:12 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958242#comment-12958242 ] Michael B edited comment on RF-13595 at 4/1/14 5:06 PM: -------------------------------------------------------- This is a minimal eclipse project to reproduce the problem. Add RF 4.3.5 jars and dependencies to WEB-INF/lib folder as well as javax.faces-2.1.27.jar to run the project against tomcat. was (Author: michaelb80): This is a minimal eclipse project to reproduce the problem. Add RF 4.3.5 jars to WEB-INF/lib folder as well as javax.faces-2.1.27.jar to run the project against tomcat. > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) added on the client side when a component becomes visible on ajax response re-rendering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 17:09:13 2014 From: issues at jboss.org (Michael B (JIRA)) Date: Tue, 1 Apr 2014 17:09:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12031) rich:validator does not work after re render (ajax) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958243#comment-12958243 ] Michael B commented on RF-12031: -------------------------------- I've filed a new issue which can be found here: https://issues.jboss.org/browse/RF-13595 > rich:validator does not work after re render (ajax) > --------------------------------------------------- > > Key: RF-12031 > URL: https://issues.jboss.org/browse/RF-12031 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.2.0.Final > Environment: browsers: Firefox, Chrome > Reporter: Andries Ehlers > Assignee: Luk?? Fry? > Priority: Minor > > When you have a simple inputText component with rich:validator inside, validation works perfectly when you move focus away from the component - validation messages display, e.g: > {code:xml|borderStyle=solid} > > > > > {code} > If the above code resides in a panel, which is conditionally rendered, then ceases to function when you re-render the panel with ajax, eg: > {code:xml|borderStyle=solid} > > > > > > >
> > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 17:13:13 2014 From: issues at jboss.org (Michael B (JIRA)) Date: Tue, 1 Apr 2014 17:13:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael B updated RF-13595: --------------------------- Description: When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to missing JS function av_xxxxxxxxx. As already described in further detail in a comment to this JIRA here: https://issues.jboss.org/browse/RF-12031 I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) added on the client side when a component becomes visible on ajax response re-rendering. Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... was: When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to missing JS function av_xxxxxxxxx. As already described in further detail in a comment to this JIRA here: https://issues.jboss.org/browse/RF-12031 I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText like for example rich:calendar. The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) added on the client side when a component becomes visible on ajax response re-rendering. > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 17:13:13 2014 From: issues at jboss.org (Michael B (JIRA)) Date: Tue, 1 Apr 2014 17:13:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael B updated RF-13595: --------------------------- Description: When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. As already described in further detail in a comment to this JIRA here: https://issues.jboss.org/browse/RF-12031 I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) added on the client side when a component becomes visible on ajax response re-rendering. Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... was: When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to missing JS function av_xxxxxxxxx. As already described in further detail in a comment to this JIRA here: https://issues.jboss.org/browse/RF-12031 I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) added on the client side when a component becomes visible on ajax response re-rendering. Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 1 17:15:14 2014 From: issues at jboss.org (Michael B (JIRA)) Date: Tue, 1 Apr 2014 17:15:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael B updated RF-13595: --------------------------- Description: When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. As already described in further detail in a comment to this JIRA here: https://issues.jboss.org/browse/RF-12031 I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... was: When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. As already described in further detail in a comment to this JIRA here: https://issues.jboss.org/browse/RF-12031 I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) added on the client side when a component becomes visible on ajax response re-rendering. Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 03:21:13 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 2 Apr 2014 03:21:13 -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 ] Michal Petrov reassigned RF-13160: ---------------------------------- Assignee: Michal Petrov > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 04:05:14 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 2 Apr 2014 04:05:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12865) Correct deferred partial response ending by leveraging PVC wrapper chain In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-12865: ------------------------------- Labels: jsf (was: jsf needs-qe) > Correct deferred partial response ending by leveraging PVC wrapper chain > ------------------------------------------------------------------------ > > Key: RF-12865 > URL: https://issues.jboss.org/browse/RF-12865 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core, third-party > Affects Versions: 4.3.1 > Environment: weblogic 10.3.4, Myfaces 2.1.10, Richfaces 4.3.1, OmniFaces1.3 > Reporter: blam lam > Assignee: Luk?? Fry? > Labels: jsf > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > After submit from a a4j:commandButton, it fail to re-render / update other component on the page. > This problem only appear in MyFaces. It does not happens in Mojarra. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 04:23:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 2 Apr 2014 04:23:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13537) Autocomplete: onbegin attribute ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-13537: ------------------------------- Summary: Autocomplete: onbegin attribute ignored (was: Autocomplete: onbegin attribute igniored) > Autocomplete: onbegin attribute ignored > --------------------------------------- > > Key: RF-13537 > URL: https://issues.jboss.org/browse/RF-13537 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Fix For: 4.3.6 > > > "onbegin" attribute of rich:autocomplete is always ignored! > I suggest next fix: > In file Autocomplete.js: > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > rf.ajax(this.id, event, {parameters: params, error: ajaxError, complete:ajaxSuccess}); > } > {code} > for fixing, we must replace on > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > var parameters_extended = {parameters: params, error: ajaxError, complete:ajaxSuccess}; > if (this.options.onbegin != undefined) { > parameters_extended.begin = this.options.onbegin; > } > rf.ajax(this.id, event, parameters_extended); > } > {code} > I can create pull request if everything ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 04:37:13 2014 From: issues at jboss.org (Lutz Ulrich (JIRA)) Date: Wed, 2 Apr 2014 04:37:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13452) UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lutz Ulrich updated RF-13452: ----------------------------- Workaround Description: When you create a UIDataAdaptor dynamically, replace the UIDataAdaptor by your own ComponentSystemEventListener. Unsubscribe UIDataAdator from itself: {{dataAdaptor.unsubscribeFromEvent(PostAddToViewEvent.class, dataAdaptor)}}. Create your own ComponentSystemEventListener and register it: {{dataAdaptor.subscribeToEvent(PostAddToViewEvent.class, new MyListener())}} In your {{MyListener}}'s implementation of {{processEvent(ComponentSystemEvent)}}: unsubscribe the UIDataAdaptor,too, but delegate to it: {{event.getComponent().unsubscribeFromEven((PostRestoreStateEvent.class, event.getComponent());}} {{event.getComponent().processEvent(event);}} Workaround: Workaround Exists > UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor > ------------------------------------------------------------------------------------- > > Key: RF-13452 > URL: https://issues.jboss.org/browse/RF-13452 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.4 > Environment: Mojarra 2.1.?? - 2.1.26 > Reporter: Lutz Ulrich > Labels: UIDataAdaptor, UIDataTable, dynamical-add > Fix For: 5-Tracking > > > Whenever a component which is based on {{org.richfaces.component.UIDataAdaptor}} is added dynamically, NPE occurs in the next RESTORE_VIEW Phase when using Mojarra 2.1.x. > My first guess was, that this would be an error in Mojarra (issue 2152, see https://java.net/jira/browse/JAVASERVERFACES-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ), > which occurs whenever a sub-class of {{UIComponent}} registers itself as {{javax.faces.event.SystemEventListener}} for > {{javax.faces.event.PostAddToViewEvent}} in ist constructor, just like {{UIDataAdaptor}} does. > Now, Manfred Riem of Mojarra argues (in the very issue named above), that registering for PostAddToView in the constructor is a design flaw in itself. > Note that the error occurs with every UIComponent which is added dynamically and which registers itself as PostAddToView listener in its constructor. For the Mojarra issue, I provided a simple component which extends the standard JSF HtmlOutputText and registers itself in its constructor, too. Baam - same error. So maybe more components of RichFaces are affected - not just those based on {{UIDataAdaptor}}. > For completion, here is a stack trace: > {quote} > Schwerwiegend: java.lang.NullPointerException > at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2526) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2111) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:289) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247) > at javax.faces.component.UIComponentBase.publishAfterViewEvents(UIComponentBase.java:2203) > at javax.faces.component.UIComponentBase.doPostAddProcessing(UIComponentBase.java:1885) > at javax.faces.component.UIComponentBase.setParent(UIComponentBase.java:405) > at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2637) > at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2609) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicAdd(FaceletPartialStateManagementStrategy.java:421) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicActions(FaceletPartialStateManagementStrategy.java:247) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreView(FaceletPartialStateManagementStrategy.java:570) > at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:138) > at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:653) > at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:142) > at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) > at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:192) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 04:49:13 2014 From: issues at jboss.org (Lutz Ulrich (JIRA)) Date: Wed, 2 Apr 2014 04:49:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13452) UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958352#comment-12958352 ] Lutz Ulrich commented on RF-13452: ---------------------------------- Some notes on the issue: First, it seems redundant that UIDataAdaptor subscribes itself for {{PostRestoreStateEvent}}. If I get the JSF specification right (JSF 2.0, section 2.2.1), processEvent(ComponentSystemEvent) has to be invoked by the JSF implementation anyway for each UIComponent when it is restored. Debugging Mojarra (2.1.28) indicates that this actually happens. Furthermore, I just added a workaround description. The most simple solution for you to fix the Problem seems to be to just implement some {{ComponentSystemEventListener}} and register an instance of that class on the {{UIDataAdaptor}} for {{PostAddToViewEvent}}, instead of the {{UIDataAdaptor}}. The listener's implementation of {{processEvent(ComponentSystemEvent)}} just delegates: {{event.getComponent().processEvent(event)}}. > UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor > ------------------------------------------------------------------------------------- > > Key: RF-13452 > URL: https://issues.jboss.org/browse/RF-13452 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.4 > Environment: Mojarra 2.1.?? - 2.1.26 > Reporter: Lutz Ulrich > Labels: UIDataAdaptor, UIDataTable, dynamical-add > Fix For: 5-Tracking > > > Whenever a component which is based on {{org.richfaces.component.UIDataAdaptor}} is added dynamically, NPE occurs in the next RESTORE_VIEW Phase when using Mojarra 2.1.x. > My first guess was, that this would be an error in Mojarra (issue 2152, see https://java.net/jira/browse/JAVASERVERFACES-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ), > which occurs whenever a sub-class of {{UIComponent}} registers itself as {{javax.faces.event.SystemEventListener}} for > {{javax.faces.event.PostAddToViewEvent}} in ist constructor, just like {{UIDataAdaptor}} does. > Now, Manfred Riem of Mojarra argues (in the very issue named above), that registering for PostAddToView in the constructor is a design flaw in itself. > Note that the error occurs with every UIComponent which is added dynamically and which registers itself as PostAddToView listener in its constructor. For the Mojarra issue, I provided a simple component which extends the standard JSF HtmlOutputText and registers itself in its constructor, too. Baam - same error. So maybe more components of RichFaces are affected - not just those based on {{UIDataAdaptor}}. > For completion, here is a stack trace: > {quote} > Schwerwiegend: java.lang.NullPointerException > at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2526) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2111) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:289) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247) > at javax.faces.component.UIComponentBase.publishAfterViewEvents(UIComponentBase.java:2203) > at javax.faces.component.UIComponentBase.doPostAddProcessing(UIComponentBase.java:1885) > at javax.faces.component.UIComponentBase.setParent(UIComponentBase.java:405) > at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2637) > at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2609) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicAdd(FaceletPartialStateManagementStrategy.java:421) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicActions(FaceletPartialStateManagementStrategy.java:247) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreView(FaceletPartialStateManagementStrategy.java:570) > at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:138) > at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:653) > at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:142) > at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) > at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:192) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 04:49:13 2014 From: issues at jboss.org (Lutz Ulrich (JIRA)) Date: Wed, 2 Apr 2014 04:49:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13452) UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lutz Ulrich updated RF-13452: ----------------------------- Environment: Mojarra 2.1.?? - 2.1.28 (was: Mojarra 2.1.?? - 2.1.26) > UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor > ------------------------------------------------------------------------------------- > > Key: RF-13452 > URL: https://issues.jboss.org/browse/RF-13452 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.4 > Environment: Mojarra 2.1.?? - 2.1.28 > Reporter: Lutz Ulrich > Labels: UIDataAdaptor, UIDataTable, dynamical-add > Fix For: 5-Tracking > > > Whenever a component which is based on {{org.richfaces.component.UIDataAdaptor}} is added dynamically, NPE occurs in the next RESTORE_VIEW Phase when using Mojarra 2.1.x. > My first guess was, that this would be an error in Mojarra (issue 2152, see https://java.net/jira/browse/JAVASERVERFACES-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ), > which occurs whenever a sub-class of {{UIComponent}} registers itself as {{javax.faces.event.SystemEventListener}} for > {{javax.faces.event.PostAddToViewEvent}} in ist constructor, just like {{UIDataAdaptor}} does. > Now, Manfred Riem of Mojarra argues (in the very issue named above), that registering for PostAddToView in the constructor is a design flaw in itself. > Note that the error occurs with every UIComponent which is added dynamically and which registers itself as PostAddToView listener in its constructor. For the Mojarra issue, I provided a simple component which extends the standard JSF HtmlOutputText and registers itself in its constructor, too. Baam - same error. So maybe more components of RichFaces are affected - not just those based on {{UIDataAdaptor}}. > For completion, here is a stack trace: > {quote} > Schwerwiegend: java.lang.NullPointerException > at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2526) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2111) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:289) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247) > at javax.faces.component.UIComponentBase.publishAfterViewEvents(UIComponentBase.java:2203) > at javax.faces.component.UIComponentBase.doPostAddProcessing(UIComponentBase.java:1885) > at javax.faces.component.UIComponentBase.setParent(UIComponentBase.java:405) > at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2637) > at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2609) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicAdd(FaceletPartialStateManagementStrategy.java:421) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicActions(FaceletPartialStateManagementStrategy.java:247) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreView(FaceletPartialStateManagementStrategy.java:570) > at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:138) > at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:653) > at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:142) > at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) > at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:192) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 04:49:13 2014 From: issues at jboss.org (Lutz Ulrich (JIRA)) Date: Wed, 2 Apr 2014 04:49:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13452) UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lutz Ulrich updated RF-13452: ----------------------------- Affects Version/s: 4.3.5 > UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor > ------------------------------------------------------------------------------------- > > Key: RF-13452 > URL: https://issues.jboss.org/browse/RF-13452 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.4, 4.3.5 > Environment: Mojarra 2.1.?? - 2.1.28 > Reporter: Lutz Ulrich > Labels: UIDataAdaptor, UIDataTable, dynamical-add > Fix For: 5-Tracking > > > Whenever a component which is based on {{org.richfaces.component.UIDataAdaptor}} is added dynamically, NPE occurs in the next RESTORE_VIEW Phase when using Mojarra 2.1.x. > My first guess was, that this would be an error in Mojarra (issue 2152, see https://java.net/jira/browse/JAVASERVERFACES-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ), > which occurs whenever a sub-class of {{UIComponent}} registers itself as {{javax.faces.event.SystemEventListener}} for > {{javax.faces.event.PostAddToViewEvent}} in ist constructor, just like {{UIDataAdaptor}} does. > Now, Manfred Riem of Mojarra argues (in the very issue named above), that registering for PostAddToView in the constructor is a design flaw in itself. > Note that the error occurs with every UIComponent which is added dynamically and which registers itself as PostAddToView listener in its constructor. For the Mojarra issue, I provided a simple component which extends the standard JSF HtmlOutputText and registers itself in its constructor, too. Baam - same error. So maybe more components of RichFaces are affected - not just those based on {{UIDataAdaptor}}. > For completion, here is a stack trace: > {quote} > Schwerwiegend: java.lang.NullPointerException > at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2526) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2111) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:289) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247) > at javax.faces.component.UIComponentBase.publishAfterViewEvents(UIComponentBase.java:2203) > at javax.faces.component.UIComponentBase.doPostAddProcessing(UIComponentBase.java:1885) > at javax.faces.component.UIComponentBase.setParent(UIComponentBase.java:405) > at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2637) > at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2609) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicAdd(FaceletPartialStateManagementStrategy.java:421) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicActions(FaceletPartialStateManagementStrategy.java:247) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreView(FaceletPartialStateManagementStrategy.java:570) > at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:138) > at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:653) > at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:142) > at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) > at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:192) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 06:51:12 2014 From: issues at jboss.org (Mohammad Weshah (JIRA)) Date: Wed, 2 Apr 2014 06:51:12 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13596) rich:collapsiblePanel dose not has disabled attribute , support it In-Reply-To: References: Message-ID: Mohammad Weshah created RF-13596: ------------------------------------ Summary: rich:collapsiblePanel dose not has disabled attribute , support it Key: RF-13596 URL: https://issues.jboss.org/browse/RF-13596 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.3.5 Reporter: Mohammad Weshah -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 06:53:13 2014 From: issues at jboss.org (Mohammad Weshah (JIRA)) Date: Wed, 2 Apr 2014 06:53:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13596) rich:collapsiblePanel dose not has disabled attribute , support it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Weshah updated RF-13596: --------------------------------- https://community.jboss.org/message/865893?et=watches.email.thread#865893 > rich:collapsiblePanel dose not has disabled attribute , support it > ------------------------------------------------------------------ > > Key: RF-13596 > URL: https://issues.jboss.org/browse/RF-13596 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: Mohammad Weshah > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 06:53:13 2014 From: issues at jboss.org (Mohammad Weshah (JIRA)) Date: Wed, 2 Apr 2014 06:53:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13596) rich:collapsiblePanel dose not has disabled attribute , support it In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Weshah updated RF-13596: --------------------------------- Priority: Minor (was: Major) > rich:collapsiblePanel dose not has disabled attribute , support it > ------------------------------------------------------------------ > > Key: RF-13596 > URL: https://issues.jboss.org/browse/RF-13596 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: Mohammad Weshah > Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 07:23:13 2014 From: issues at jboss.org (Valiantsin Shukaila (JIRA)) Date: Wed, 2 Apr 2014 07:23:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11427) rich:tab - actionListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958412#comment-12958412 ] Valiantsin Shukaila commented on RF-11427: ------------------------------------------ Maybe I can contact you for instructions in more intercative way somewhere? The last command fails for me. I spent few hours trying to run it, on jbossas-managed-7-1 it doesn't launch at all because can not find some kind of server config or soemthing like that. When I tried launching on jbossas-managed-7 profile it launches but firefox blinks with 404 page and test fails at the beginning. Need to have some detailed instruction on running this. > rich:tab - actionListener > ------------------------- > > Key: RF-11427 > URL: https://issues.jboss.org/browse/RF-11427 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1 > Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d > Metamer 4.1.0-SNAPSHOT r.22728 > Mojarra 2.1.2-FCS > Apache Tomcat 7.0.16 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 18.0.1025.168 @ Linux i686 > Reporter: Jan Papousek > Labels: ci_issue > Fix For: 5-Tracking > > > It seems that the actionListener attribute doesn't work. > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # open tab2 > # open tab1 (action and action listener are invoked) > # open tab2 > # open tab1 (action and action listener are *NOT* invoked) > # open tab1 (action and action listener are invoked) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 07:43:14 2014 From: issues at jboss.org (Lutz Ulrich (JIRA)) Date: Wed, 2 Apr 2014 07:43:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13452) UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958352#comment-12958352 ] Lutz Ulrich edited comment on RF-13452 at 4/2/14 7:42 AM: ---------------------------------------------------------- Some notes on the issue: First, it seems redundant that {{UIDataAdaptor}} subscribes itself for {{PostRestoreStateEvent}}. If I get the JSF specification right (JSF 2.0, section 2.2.1), processEvent(ComponentSystemEvent) has to be invoked by the JSF implementation anyway for each UIComponent when it is restored. Debugging Mojarra (2.1.28) indicates that this actually happens. Furthermore, I just added a workaround description. The most simple solution for you to fix the problem seems to be to just implement some {{ComponentSystemEventListener}} and register an instance of that class on the {{UIDataAdaptor}} for {{PostAddToViewEvent}}, instead of the {{UIDataAdaptor}}. The listener's implementation of {{processEvent(ComponentSystemEvent)}} just delegates: {{event.getComponent().processEvent(event)}}. Also note that {{UIFileUpload}} imposes a similar Problem, because {{AbstractFileUpload}} is a listener for {{PostAddToViewEvent}} by annotation as well. was (Author: lutzulrich): Some notes on the issue: First, it seems redundant that UIDataAdaptor subscribes itself for {{PostRestoreStateEvent}}. If I get the JSF specification right (JSF 2.0, section 2.2.1), processEvent(ComponentSystemEvent) has to be invoked by the JSF implementation anyway for each UIComponent when it is restored. Debugging Mojarra (2.1.28) indicates that this actually happens. Furthermore, I just added a workaround description. The most simple solution for you to fix the Problem seems to be to just implement some {{ComponentSystemEventListener}} and register an instance of that class on the {{UIDataAdaptor}} for {{PostAddToViewEvent}}, instead of the {{UIDataAdaptor}}. The listener's implementation of {{processEvent(ComponentSystemEvent)}} just delegates: {{event.getComponent().processEvent(event)}}. > UIDataAdaptor must not register as listener for PostAddToViewEvent in its constructor > ------------------------------------------------------------------------------------- > > Key: RF-13452 > URL: https://issues.jboss.org/browse/RF-13452 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.4, 4.3.5 > Environment: Mojarra 2.1.?? - 2.1.28 > Reporter: Lutz Ulrich > Labels: UIDataAdaptor, UIDataTable, dynamical-add > Fix For: 5-Tracking > > > Whenever a component which is based on {{org.richfaces.component.UIDataAdaptor}} is added dynamically, NPE occurs in the next RESTORE_VIEW Phase when using Mojarra 2.1.x. > My first guess was, that this would be an error in Mojarra (issue 2152, see https://java.net/jira/browse/JAVASERVERFACES-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ), > which occurs whenever a sub-class of {{UIComponent}} registers itself as {{javax.faces.event.SystemEventListener}} for > {{javax.faces.event.PostAddToViewEvent}} in ist constructor, just like {{UIDataAdaptor}} does. > Now, Manfred Riem of Mojarra argues (in the very issue named above), that registering for PostAddToView in the constructor is a design flaw in itself. > Note that the error occurs with every UIComponent which is added dynamically and which registers itself as PostAddToView listener in its constructor. For the Mojarra issue, I provided a simple component which extends the standard JSF HtmlOutputText and registers itself in its constructor, too. Baam - same error. So maybe more components of RichFaces are affected - not just those based on {{UIDataAdaptor}}. > For completion, here is a stack trace: > {quote} > Schwerwiegend: java.lang.NullPointerException > at javax.faces.component.UIComponent$ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2526) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2111) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:289) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247) > at javax.faces.component.UIComponentBase.publishAfterViewEvents(UIComponentBase.java:2203) > at javax.faces.component.UIComponentBase.doPostAddProcessing(UIComponentBase.java:1885) > at javax.faces.component.UIComponentBase.setParent(UIComponentBase.java:405) > at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2637) > at javax.faces.component.UIComponentBase$ChildrenList.add(UIComponentBase.java:2609) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicAdd(FaceletPartialStateManagementStrategy.java:421) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreDynamicActions(FaceletPartialStateManagementStrategy.java:247) > at com.sun.faces.application.view.FaceletPartialStateManagementStrategy.restoreView(FaceletPartialStateManagementStrategy.java:570) > at com.sun.faces.application.StateManagerImpl.restoreView(StateManagerImpl.java:138) > at com.sun.faces.application.view.ViewHandlingStrategy.restoreView(ViewHandlingStrategy.java:123) > at com.sun.faces.application.view.FaceletViewHandlingStrategy.restoreView(FaceletViewHandlingStrategy.java:653) > at com.sun.faces.application.view.MultiViewHandler.restoreView(MultiViewHandler.java:142) > at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) > at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:301) > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:192) > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) > at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 07:43:14 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 2 Apr 2014 07:43:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958421#comment-12958421 ] Pavol Pitonak commented on RF-13592: ------------------------------------ I could not reproduce in Metamer. [~igor_ab], according to web.xml and localhost.har it seems that you're running a portlet. Can you reproduce outside of portal environment? Secondly, it's normal that a4j:push starts working after some time (in my environment ca. 20 seconds). Can you try to enable the push, disable it, enable it again and wait 20-30 second before generating a message? > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Pavol Pitonak > Priority: Critical > Attachments: a4j.log, localhost.har, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 07:45:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 2 Apr 2014 07:45:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-13592: ------------------------------- Labels: waiting_on_user (was: ) > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Pavol Pitonak > Priority: Critical > Labels: waiting_on_user > Attachments: a4j.log, localhost.har, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 10:17:28 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 2 Apr 2014 10:17:28 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11427) rich:tab - actionListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958528#comment-12958528 ] Pavol Pitonak commented on RF-11427: ------------------------------------ It's my fault. The correct steps to reproduce are: # git clone https://github.com/richfaces/richfaces-qa.git # cd richfaces-qa # git checkout 4.3.x # mvn clean install -DskipTests # cd metamer/ftest # mvn clean verify -P jbossas-managed-7-1 -Dtest=TestTabPanel#testImmediate > rich:tab - actionListener > ------------------------- > > Key: RF-11427 > URL: https://issues.jboss.org/browse/RF-11427 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1 > Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d > Metamer 4.1.0-SNAPSHOT r.22728 > Mojarra 2.1.2-FCS > Apache Tomcat 7.0.16 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 18.0.1025.168 @ Linux i686 > Reporter: Jan Papousek > Labels: ci_issue > Fix For: 5-Tracking > > > It seems that the actionListener attribute doesn't work. > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # open tab2 > # open tab1 (action and action listener are invoked) > # open tab2 > # open tab1 (action and action listener are *NOT* invoked) > # open tab1 (action and action listener are invoked) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 11:33:13 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 2 Apr 2014 11:33:13 -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:comment-tabpanel&focusedCommentId=12958568#comment-12958568 ] Michal Petrov commented on RF-13514: ------------------------------------ {quote}it is required to click on add button more than one times eg. upload a file and then try to add next file, you need to click on add more times - in Metamer{quote} Should work now, the button was bigger than the clickable element. {quote}maxFilesQuantity attribute does not work, has no effect{quote} This wasn't working with drag'n'drop but it should have been working with adding files manually. Was it not the case? {quote}keydown not fired{quote} When is it supposed fire? I'll have to check AS, it looks like even the old fileUpload isn't working there. > 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 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 11:45:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 11:45:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958577#comment-12958577 ] Brian Leathem commented on RF-13595: ------------------------------------ To be clear, the workaround suggest of using a4j:ajax instead of f:ajax does not work for you? > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 11:55:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 11:55:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13537) Autocomplete: onbegin attribute ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958579#comment-12958579 ] Brian Leathem commented on RF-13537: ------------------------------------ [~mitalex], [~rustock0], [~littlie], [~mpatelekom], [~markus.meisterernst.2014], [~vorgehen], [~yaskovsergey], [~raild], [~libal] vote stacking from a single company is not appreciated. It makes our task as Open Source developers more difficult by making it harder to triage and prioritize issues. Please don't do it. > Autocomplete: onbegin attribute ignored > --------------------------------------- > > Key: RF-13537 > URL: https://issues.jboss.org/browse/RF-13537 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Fix For: 4.3.6 > > > "onbegin" attribute of rich:autocomplete is always ignored! > I suggest next fix: > In file Autocomplete.js: > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > rf.ajax(this.id, event, {parameters: params, error: ajaxError, complete:ajaxSuccess}); > } > {code} > for fixing, we must replace on > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > var parameters_extended = {parameters: params, error: ajaxError, complete:ajaxSuccess}; > if (this.options.onbegin != undefined) { > parameters_extended.begin = this.options.onbegin; > } > rf.ajax(this.id, event, parameters_extended); > } > {code} > I can create pull request if everything ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 11:57:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 11:57:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13537) Autocomplete: onbegin attribute ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958579#comment-12958579 ] Brian Leathem edited comment on RF-13537 at 4/2/14 11:56 AM: ------------------------------------------------------------- [~mitalex], [~rustock0], [~littlie], [~mpatelekom], [~markus.meisterernst.2014], [~vorgehen], [~yaskovsergey], [~raild], [~libal] vote stacking from a single company is not appreciated. It makes our task as Open Source developers more difficult by making it harder to triage and prioritize issues. Please don't do it. -- Sorry, I commented on the wrong issue :P was (Author: bleathem): [~mitalex], [~rustock0], [~littlie], [~mpatelekom], [~markus.meisterernst.2014], [~vorgehen], [~yaskovsergey], [~raild], [~libal] vote stacking from a single company is not appreciated. It makes our task as Open Source developers more difficult by making it harder to triage and prioritize issues. Please don't do it. > Autocomplete: onbegin attribute ignored > --------------------------------------- > > Key: RF-13537 > URL: https://issues.jboss.org/browse/RF-13537 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Fix For: 4.3.6 > > > "onbegin" attribute of rich:autocomplete is always ignored! > I suggest next fix: > In file Autocomplete.js: > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > rf.ajax(this.id, event, {parameters: params, error: ajaxError, complete:ajaxSuccess}); > } > {code} > for fixing, we must replace on > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > var parameters_extended = {parameters: params, error: ajaxError, complete:ajaxSuccess}; > if (this.options.onbegin != undefined) { > parameters_extended.begin = this.options.onbegin; > } > rf.ajax(this.id, event, parameters_extended); > } > {code} > I can create pull request if everything ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 11:57:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 11:57:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13537) Autocomplete: onbegin attribute ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13537: ------------------------------- Comment: was deleted (was: [~mitalex], [~rustock0], [~littlie], [~mpatelekom], [~markus.meisterernst.2014], [~vorgehen], [~yaskovsergey], [~raild], [~libal] vote stacking from a single company is not appreciated. It makes our task as Open Source developers more difficult by making it harder to triage and prioritize issues. Please don't do it. -- Sorry, I commented on the wrong issue :P) > Autocomplete: onbegin attribute ignored > --------------------------------------- > > Key: RF-13537 > URL: https://issues.jboss.org/browse/RF-13537 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Fix For: 4.3.6 > > > "onbegin" attribute of rich:autocomplete is always ignored! > I suggest next fix: > In file Autocomplete.js: > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > rf.ajax(this.id, event, {parameters: params, error: ajaxError, complete:ajaxSuccess}); > } > {code} > for fixing, we must replace on > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > var parameters_extended = {parameters: params, error: ajaxError, complete:ajaxSuccess}; > if (this.options.onbegin != undefined) { > parameters_extended.begin = this.options.onbegin; > } > rf.ajax(this.id, event, parameters_extended); > } > {code} > I can create pull request if everything ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 11:57:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 11:57:14 -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:comment-tabpanel&focusedCommentId=12958581#comment-12958581 ] Brian Leathem commented on RF-13593: ------------------------------------ [~mitalex], [~rustock0], [~littlie], [~mpatelekom], [~markus.meisterernst.2014], [~vorgehen], [~yaskovsergey], [~raild], [~libal] vote stacking from a single company is not appreciated. It makes our task as Open Source developers more difficult by making it harder to triage and prioritize issues. Please don't do it. > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 12:01:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 12:01:14 -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:comment-tabpanel&focusedCommentId=12958582#comment-12958582 ] Brian Leathem commented on RF-13593: ------------------------------------ This seems possibly related to this Atmosphere issue: http://atmosphere-framework.2306103.n4.nabble.com/v2-0-6-IE8-fails-to-access-ajaxRequest-status-td4656953.html > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 12:01:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 12:01:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13594) Column width of rich:extendedDataTable with rich:dataScroller In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958583#comment-12958583 ] Brian Leathem commented on RF-13594: ------------------------------------ Can you try with a more recent release of RichFaces (eg 4.3.5)? > Column width of rich:extendedDataTable with rich:dataScroller > ------------------------------------------------------------- > > Key: RF-13594 > URL: https://issues.jboss.org/browse/RF-13594 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.2.3.Final > Environment: Windows 7 + IE / Firefox > Reporter: Thomas Eichberger > Attachments: screenshot.png > > > I implemented a sortable rich:extendedDataTable with its according rich:dataScroller. After the table is filled resizing columns of the table works as supposed. When the page is changed by using the datascroller the column headers remain with the changed width, but the data columns are displayed with default column width. Because of this behavior the table is displayed distorted totally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 12:03:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 12:03:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13596) Add a disabled attribute to rich:collapsiblePanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13596: ------------------------------- Summary: Add a disabled attribute to rich:collapsiblePanel (was: rich:collapsiblePanel dose not has disabled attribute , support it) > Add a disabled attribute to rich:collapsiblePanel > ------------------------------------------------- > > Key: RF-13596 > URL: https://issues.jboss.org/browse/RF-13596 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: Mohammad Weshah > Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 12:03:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 12:03:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13596) Add a disabled attribute to rich:collapsiblePanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13596: ------------------------------- Forum Reference: https://community.jboss.org/message/865893?et=watches.email.thread#865893 > Add a disabled attribute to rich:collapsiblePanel > ------------------------------------------------- > > Key: RF-13596 > URL: https://issues.jboss.org/browse/RF-13596 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: Mohammad Weshah > Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 12:03:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 12:03:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13596) Add a disabled attribute to rich:collapsiblePanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13596: ------------------------------- Fix Version/s: 4.5-Tracking > Add a disabled attribute to rich:collapsiblePanel > ------------------------------------------------- > > Key: RF-13596 > URL: https://issues.jboss.org/browse/RF-13596 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: Mohammad Weshah > Priority: Minor > Fix For: 4.5-Tracking > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 12:03:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 12:03:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13596) Add a disabled attribute to rich:collapsiblePanel In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13596: ------------------------------- Comment: was deleted (was: https://community.jboss.org/message/865893?et=watches.email.thread#865893) > Add a disabled attribute to rich:collapsiblePanel > ------------------------------------------------- > > Key: RF-13596 > URL: https://issues.jboss.org/browse/RF-13596 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: Mohammad Weshah > Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 12:15:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 12:15:13 -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: ------------------------------- Assignee: Luk?? Macko > 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 > > > Backport the chart components to RichFaces 4.5 components module -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 13:05:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 13:05:13 -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 ] Brian Leathem updated RF-12132: ------------------------------- Forum Reference: https://community.jboss.org/message/727494#727494, https://community.jboss.org/thread/233741 (was: https://community.jboss.org/message/727494#727494) > 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 > Environment: Myfaces 2.1.6 > Tomcat 6.0.35 > Reporter: Michael Heinen > Fix For: 5-Tracking > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 13:07:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 13:07:13 -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 ] Brian Leathem reassigned RF-12132: ---------------------------------- Assignee: Pavol Pitonak QE are we able to re-reproduce this issue? From the 2nd of the referenced forum references it seems the problem is intermittent. Perhaps we need to setup a framework test and repeat it a large number of times to see if it fails. > 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 > Environment: Myfaces 2.1.6 > Tomcat 6.0.35 > Reporter: Michael Heinen > Assignee: Pavol Pitonak > Fix For: 5-Tracking > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 13:07:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 13:07:13 -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 ] Brian Leathem updated RF-12132: ------------------------------- Labels: needs-qe (was: ) > 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 > Environment: Myfaces 2.1.6 > Tomcat 6.0.35 > Reporter: Michael Heinen > Assignee: Pavol Pitonak > Labels: needs-qe > Fix For: 5-Tracking > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 13:15:13 2014 From: issues at jboss.org (Michael B (JIRA)) Date: Wed, 2 Apr 2014 13:15:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958609#comment-12958609 ] Michael B commented on RF-13595: -------------------------------- And that's exactly what we tested: The workaround with a4j:ajax executes the validation (after the first JS error occurs) and surely works in a simple example like the given test project, but produces other problems in more complex page layouts with various components. Also the workaround ist not applicable for other input components like rich:calendar etc. where the component stops working. You could replace the inputText in the test application by the rich:calendar component and of course also change the input field/validator in the backing bean to a java.util.Date. Effect is, that the validation fails when you select a date in the calendar pop-up and the pop-up does not close due to the processing error in JS. That's why I think that's a more general problem with JS loading that affects more than what could be solved with the workaround - unfortunately... > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 13:27:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 2 Apr 2014 13:27:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13595: ---------------------------------- Assignee: Pavol Pitonak Thanks for the clarification [~michaelb80]. [~ppitonak] can we look at the provided sample and determine if we indeed hava an underlying issue here? > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Assignee: Pavol Pitonak > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 2 13:27:13 2014 From: issues at jboss.org (SBS JIRA Integration (JIRA)) Date: Wed, 2 Apr 2014 13:27:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13587) rich:autocomplete - suggestion box doesn't show up at all In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SBS JIRA Integration updated RF-13587: -------------------------------------- Forum Reference: https://community.jboss.org/message/863447#863447 > rich:autocomplete - suggestion box doesn't show up at all > --------------------------------------------------------- > > Key: RF-13587 > URL: https://issues.jboss.org/browse/RF-13587 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Implementation: JSF-2.2.6 mojarra, Mojarra 2.2.5 > Server: WebLogic 12.1.2.1, WildFly 8.0.0.Final > Browser: Chrome 33, Firefox 27 > Java: 1.7 > Reporter: Amit Tikoo > Labels: richfaces > Fix For: 4.5.0.Alpha3 > > > I am using a component but the suggestion box just doesn't show up. Here is a simple case I'm trying: > XHTML: > {code} > > > > #{station} > > > > {code} > JAVA: > {code} > public List autocomplete1(String request){ > List suggestions = new ArrayList(); > suggestions.add("test 1"); > suggestions.add("test 2"); > suggestions.add("test 3"); > suggestions.add("test 4"); > return suggestions; > } > {code} > This shows up in logging (using ) > {code} > error[14:47:03.644]: Received 'error at malformedXML' event from > error[14:47:03.644]: [status=200] During update: javax.faces.ViewState not found > {code} > Also i can see the suggestion if i switch the mode to "Client" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 3 02:41:13 2014 From: issues at jboss.org (abhishek vijra (JIRA)) Date: Thu, 3 Apr 2014 02:41:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13597) Drag and drop support for file upload In-Reply-To: References: Message-ID: abhishek vijra created RF-13597: ----------------------------------- Summary: 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 Drag/Drop support should be added to file upload component . Like the primefaces fileUploadDnd : http://www.primefaces.org/showcase/ui/fileUploadDnd.jsf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 3 02:53:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 3 Apr 2014 02:53:13 -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:comment-tabpanel&focusedCommentId=12958748#comment-12958748 ] Juraj H?ska commented on RF-13514: ---------------------------------- # {{maxFilesQuantity}} - for me it is the other way round, attribute works correctly when adding files with D&D, it does not work when adding files manually. The add button does not disappear nor there is any other restriction to upload more files. # {{keydown}} - IMHO it should be fired when a user has focus on {{fileUpload}} component and press key (without further releasing). Other key related handlers do not work as well ({{onkeyup}}, {{onkeypress}}) > 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 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 3 06:15:14 2014 From: issues at jboss.org (Valiantsin Shukaila (JIRA)) Date: Thu, 3 Apr 2014 06:15:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11427) rich:tab - actionListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958830#comment-12958830 ] Valiantsin Shukaila commented on RF-11427: ------------------------------------------ So pull request was updated to fix immediate attribute functionality. Please verify. > rich:tab - actionListener > ------------------------- > > Key: RF-11427 > URL: https://issues.jboss.org/browse/RF-11427 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1 > Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d > Metamer 4.1.0-SNAPSHOT r.22728 > Mojarra 2.1.2-FCS > Apache Tomcat 7.0.16 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 18.0.1025.168 @ Linux i686 > Reporter: Jan Papousek > Labels: ci_issue > Fix For: 5-Tracking > > > It seems that the actionListener attribute doesn't work. > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # open tab2 > # open tab1 (action and action listener are invoked) > # open tab2 > # open tab1 (action and action listener are *NOT* invoked) > # open tab1 (action and action listener are invoked) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 3 08:39:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 3 Apr 2014 08:39:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11427) rich:tab - actionListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958893#comment-12958893 ] Pavol Pitonak commented on RF-11427: ------------------------------------ Hi, all tests for switchable components pass now but action/action listener is not working correctly. Both action and action listener are invoked in fourth phase (update model values) and fifth phase (invoke application) is skipped. [~bleathem], since we are adding action and action listener to the r:tab, shouldn't we add them also to r:accordionItem and r:togglePanelItem? Are they expected to work in the same way as those in r:panelMenuItem? > rich:tab - actionListener > ------------------------- > > Key: RF-11427 > URL: https://issues.jboss.org/browse/RF-11427 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1 > Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d > Metamer 4.1.0-SNAPSHOT r.22728 > Mojarra 2.1.2-FCS > Apache Tomcat 7.0.16 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 18.0.1025.168 @ Linux i686 > Reporter: Jan Papousek > Labels: ci_issue > Fix For: 5-Tracking > > > It seems that the actionListener attribute doesn't work. > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # open tab2 > # open tab1 (action and action listener are invoked) > # open tab2 > # open tab1 (action and action listener are *NOT* invoked) > # open tab1 (action and action listener are invoked) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 3 08:39:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Thu, 3 Apr 2014 08:39:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13595: ---------------------------------- Assignee: Matej Novotny (was: Pavol Pitonak) > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Assignee: Matej Novotny > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 3 10:15:14 2014 From: issues at jboss.org (Valiantsin Shukaila (JIRA)) Date: Thu, 3 Apr 2014 10:15:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11427) rich:tab - actionListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958971#comment-12958971 ] Valiantsin Shukaila commented on RF-11427: ------------------------------------------ Just updated the commit. Now action and actionListener is invoked on necessary phase and immediate works fine. Please check. > rich:tab - actionListener > ------------------------- > > Key: RF-11427 > URL: https://issues.jboss.org/browse/RF-11427 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1 > Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d > Metamer 4.1.0-SNAPSHOT r.22728 > Mojarra 2.1.2-FCS > Apache Tomcat 7.0.16 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 18.0.1025.168 @ Linux i686 > Reporter: Jan Papousek > Labels: ci_issue > Fix For: 5-Tracking > > > It seems that the actionListener attribute doesn't work. > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # open tab2 > # open tab1 (action and action listener are invoked) > # open tab2 > # open tab1 (action and action listener are *NOT* invoked) > # open tab1 (action and action listener are invoked) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 04:39:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 4 Apr 2014 04:39:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11427) rich:tab - actionListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-11427: ---------------------------------- Assignee: Brian Leathem Thanks [~Trims], it works fine now. [~bleathem], the is a checkstyle violation on line 580 and it needs to be rebased to lastest master. IMHO we can handle these minor issues, WDYT? > rich:tab - actionListener > ------------------------- > > Key: RF-11427 > URL: https://issues.jboss.org/browse/RF-11427 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1 > Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d > Metamer 4.1.0-SNAPSHOT r.22728 > Mojarra 2.1.2-FCS > Apache Tomcat 7.0.16 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 18.0.1025.168 @ Linux i686 > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: ci_issue > Fix For: 5-Tracking > > > It seems that the actionListener attribute doesn't work. > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # open tab2 > # open tab1 (action and action listener are invoked) > # open tab2 > # open tab1 (action and action listener are *NOT* invoked) > # open tab1 (action and action listener are invoked) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 05:05:14 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Fri, 4 Apr 2014 05:05:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11768) rich:inplaceSelect - @onlisthide and @onlistshow attributes don't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959197#comment-12959197 ] Matej Novotny commented on RF-11768: ------------------------------------ This issue is still reproducible in all branches (4.3.x, 4.5.x and 5.x). I created [tests|https://github.com/richfaces/richfaces-qa/blob/4.3.x/metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/richInplaceSelect/TestInplaceSelectAttributes.java#L550] in all branches and marked them as Future and IssueTracking. > rich:inplaceSelect - @onlisthide and @onlistshow attributes don't work > ---------------------------------------------------------------------- > > Key: RF-11768 > URL: https://issues.jboss.org/browse/RF-11768 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.1.0.CR2 > Reporter: Jan Papousek > Fix For: 5-Tracking > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 05:23:13 2014 From: issues at jboss.org (Igor Bolshakov (JIRA)) Date: Fri, 4 Apr 2014 05:23:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Bolshakov updated RF-13592: -------------------------------- Attachment: push-test.zip Sample application project > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Pavol Pitonak > Priority: Critical > Labels: waiting_on_user > Attachments: a4j.log, localhost.har, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 05:33:13 2014 From: issues at jboss.org (Igor Bolshakov (JIRA)) Date: Fri, 4 Apr 2014 05:33:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Bolshakov updated RF-13592: -------------------------------- Attachment: push-test.zip Test application project > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Pavol Pitonak > Priority: Critical > Labels: waiting_on_user > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 05:43:13 2014 From: issues at jboss.org (Igor Bolshakov (JIRA)) Date: Fri, 4 Apr 2014 05:43:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959205#comment-12959205 ] Igor Bolshakov edited comment on RF-13592 at 4/4/14 5:42 AM: ------------------------------------------------------------- Please, use test application maven project. We don't use portlets anymore. This is only old context parameter we forgot to clean up. Anyway we built sample application and we deployed it under Tomcat Version 8.0.5 and Tomcat Version 7.0.52. Bug is reproduced on both J2EE containers. To test just build WAR and deploy it. Open in browser url http://localhost:8080/sample/pages/push.xhtml. Below is result of "mvn -v" command on my local machine: {quote}Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100) Maven home: B:\tools\maven Java version: 1.7.0_45, vendor: Oracle Corporation Java home: B:\tools\jdk\jre Default locale: de_DE, platform encoding: UTF-8 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"{quote} was (Author: igor_ab): Test application project > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Pavol Pitonak > Priority: Critical > Labels: waiting_on_user > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 08:29:13 2014 From: issues at jboss.org (Wang Liyu (JIRA)) Date: Fri, 4 Apr 2014 08:29:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: Wang Liyu created RF-13598: ------------------------------ Summary: Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 Key: RF-13598 URL: https://issues.jboss.org/browse/RF-13598 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: compatibility Affects Versions: 4.3.5, 4.2.3.Final Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ Reporter: Wang Liyu Priority: Critical See the https://community.jboss.org/thread/239391 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 08:39:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 4 Apr 2014 08:39:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13559) Backport RF-13018 (a4j:commandButton wrong actions performed) to RF 4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959278#comment-12959278 ] Pavol Pitonak commented on RF-13559: ------------------------------------ Verified in 4.3.6. Can be closed after verified in 4.5.0.Alpha3. > Backport RF-13018 (a4j:commandButton wrong actions performed) to RF 4 > --------------------------------------------------------------------- > > Key: RF-13559 > URL: https://issues.jboss.org/browse/RF-13559 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.3.Final, 4.3.2 > Reporter: Jon?? Trantina > Assignee: Michal Petrov > Fix For: 4.3.6, 4.5.0.Alpha3 > > > Backport fix for RF-13018 from RF 5 to RF 4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 08:51:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 4 Apr 2014 08:51:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13531) selects: cannot select option on IE11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13531. ------------------------------ > selects: cannot select option on IE11 > ------------------------------------- > > Key: RF-13531 > URL: https://issues.jboss.org/browse/RF-13531 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > Environment: IE 11 > Reporter: Ji?? ?tefek > Assignee: Brian Leathem > Labels: IE11 > Fix For: 4.3.6 > > > 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. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}. > ** 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 08:55:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 4 Apr 2014 08:55:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13453) There is no way to extend class org.richfaces.renderkit.ExtendedDataTableRenderer properly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak closed RF-13453. ------------------------------ Verified > There is no way to extend class org.richfaces.renderkit.ExtendedDataTableRenderer properly > ------------------------------------------------------------------------------------------ > > Key: RF-13453 > URL: https://issues.jboss.org/browse/RF-13453 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Roman Chigvintsev > Assignee: Roman Chigvintsev > Fix For: 4.3.6 > > > It's impossible to override some methods of class {{org.richfaces.renderkit.ExtendedDataTableRenderer}} (e.g. {{void encodeBody(RendererState state)}}) because internal classes and enums have private access level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 10:05:40 2014 From: issues at jboss.org (Thomas Eichberger (JIRA)) Date: Fri, 4 Apr 2014 10:05:40 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13594) Column width of rich:extendedDataTable with rich:dataScroller In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Eichberger resolved RF-13594. ------------------------------------ Resolution: Done Hi Brian, many thanks for your reply. It seems to be fixed in the new versions. Best regards Thomas > Column width of rich:extendedDataTable with rich:dataScroller > ------------------------------------------------------------- > > Key: RF-13594 > URL: https://issues.jboss.org/browse/RF-13594 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.2.3.Final > Environment: Windows 7 + IE / Firefox > Reporter: Thomas Eichberger > Attachments: screenshot.png > > > I implemented a sortable rich:extendedDataTable with its according rich:dataScroller. After the table is filled resizing columns of the table works as supposed. When the page is changed by using the datascroller the column headers remain with the changed width, but the data columns are displayed with default column width. Because of this behavior the table is displayed distorted totally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 12:32:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 4 Apr 2014 12:32:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13594) Column width of rich:extendedDataTable with rich:dataScroller In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-13594: -------------------------------- > Column width of rich:extendedDataTable with rich:dataScroller > ------------------------------------------------------------- > > Key: RF-13594 > URL: https://issues.jboss.org/browse/RF-13594 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.2.3.Final > Environment: Windows 7 + IE / Firefox > Reporter: Thomas Eichberger > Attachments: screenshot.png > > > I implemented a sortable rich:extendedDataTable with its according rich:dataScroller. After the table is filled resizing columns of the table works as supposed. When the page is changed by using the datascroller the column headers remain with the changed width, but the data columns are displayed with default column width. Because of this behavior the table is displayed distorted totally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 12:32:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 4 Apr 2014 12:32:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13594) Column width of rich:extendedDataTable with rich:dataScroller In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13594. -------------------------------- Resolution: Out of Date > Column width of rich:extendedDataTable with rich:dataScroller > ------------------------------------------------------------- > > Key: RF-13594 > URL: https://issues.jboss.org/browse/RF-13594 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-ScrollableDataTable > Affects Versions: 4.2.3.Final > Environment: Windows 7 + IE / Firefox > Reporter: Thomas Eichberger > Attachments: screenshot.png > > > I implemented a sortable rich:extendedDataTable with its according rich:dataScroller. After the table is filled resizing columns of the table works as supposed. When the page is changed by using the datascroller the column headers remain with the changed width, but the data columns are displayed with default column width. Because of this behavior the table is displayed distorted totally. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 4 12:34:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 4 Apr 2014 12:34:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13598: ---------------------------------- Assignee: Pavol Pitonak QE, please verify > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Pavol Pitonak > Priority: Critical > > See the https://community.jboss.org/thread/239391 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Apr 6 02:05:12 2014 From: issues at jboss.org (Luis Garcia (JIRA)) Date: Sun, 6 Apr 2014 02:05:12 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12491) Datatable model is accessed in tab panel which is not rendered using switch type "server" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12949187#comment-12949187 ] Luis Garcia edited comment on RF-12491 at 4/6/14 2:03 AM: ---------------------------------------------------------- I recently tested this with RichFaces 5.0.0 Alpha3 and JSF 2.2 on Wildfly 8.0 Final The issue is still present - The test were conducted using a set of Dynamic Tabs with DataTables inside them. The data model for each DataTables was called upon - even if it wasn't the active Tab. was (Author: peter.falken): I recently tested this with RichFaces 5.0.0 Alpha3. The issue is still present - The test were conducted using a set of Dynamic Tabs with DataTables inside them. The data model for each DataTables was called upon - even if it wasn't the active Tab. > Datatable model is accessed in tab panel which is not rendered using switch type "server" > ----------------------------------------------------------------------------------------- > > Key: RF-12491 > URL: https://issues.jboss.org/browse/RF-12491 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.0.Final, 4.2.2.Final > Environment: Mojarra 2.1.20, JDK 1.6, JDK 1.7, Tomcat 7.0.x > Reporter: Denis Pasek > Labels: lazy-loaded > Fix For: 5-Tracking > > Attachments: richfaces-visittree.zip, stacktrace-richfaces.png > > > When a RichFaces Tab of a TabPanel contains a RichFaces DataTable the model of the DataTable is accessed even if the Tab is not rendered at all. > Since the retrieval of the data table data might include costly database operations this is a serious performance issue. > The issue seems to be related to the state saving of JSF: the methods are not called during encodeAll() but during state saving of view. > My own analysis shows that AbstractTogglePanel visitTree() implementation visits all tab panels sub tree but not only the active one. Additionally it seems that the UIDataAdaptor wants to visit all rows of table even if it is not rendered as JSF state saving runs in RENDER_RESPONSE phase (see attached stacktrace). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Apr 6 04:25:14 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Sun, 6 Apr 2014 04:25:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959507#comment-12959507 ] Juraj H?ska commented on RF-13250: ---------------------------------- Verified for 4.3.6.Final. > Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final > -------------------------------------------------------------- > > Key: RF-13250 > URL: https://issues.jboss.org/browse/RF-13250 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4, 4.3.5 > Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5 > Reporter: Milo van der Zee > Assignee: Juraj H?ska > Labels: memoryleak > Fix For: 4.3.6, 5.0.0.Alpha4 > > Attachments: rf.patch > > > Hello, > I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone. > I also started seeing this message lot's of times: > {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}} > I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory. > In the crashed system heap dump I see a lot of: > - AtomicBoolean (751.000, 15.0MB) > - ConcurrentLinkedQueue > - AtmospereRequest$Builder (60.042, 13.8MB) > To me it looks like it has something to do with Atmosphere. Any ideas? > Thanks, > Milo van der Zee -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 02:20:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 7 Apr 2014 02:20:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13511) Photoalbum: unite behaviour of dataScroller in FB/G+ and in own/predefined albums In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13511. ---------------------------- Verified that G+ albums are now behaving like the custom ones. Closing. > Photoalbum: unite behaviour of dataScroller in FB/G+ and in own/predefined albums > --------------------------------------------------------------------------------- > > Key: RF-13511 > URL: https://issues.jboss.org/browse/RF-13511 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.5 > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.6 > > > The dataScroller component behaves differently in G+/FB albums and in own/predefined albums. > The behaviour in own/predefined albums is imho better. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 02:32:12 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 7 Apr 2014 02:32:12 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13569) Photoalbum: the change of users avatar doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska reopened RF-13569: ------------------------------ Reopening the issue because: The objection number 2. is still present. Changing of the avatar does not work. Also other profile information (e.g. First name) is not updated. > Photoalbum: the change of users avatar doesn't work > --------------------------------------------------- > > Key: RF-13569 > URL: https://issues.jboss.org/browse/RF-13569 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.6 > > > # After the user's avatar is changed, the avatar is not updated in comments or search results (already resolved by https://github.com/richfaces4/dev-examples/commit/942575579f4e80c2d8dac5c3e1e57f8e706ee0cc) > # the avatar is not updated in the users profile after a second change of the avatar (but is updated in search result and in comments) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 02:54:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 7 Apr 2014 02:54:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13598: ---------------------------------- Assignee: Brian Leathem (was: Pavol Pitonak) This issue is result of discussion on community forum. I commented on forum: {quote} I could reproduce this issue with a4j:jsFunction. Some of other components using ajax are broke too, e.g. tabPanel (ajax mode), accordion, collapsible panel, panel menu, inplace input, slider, spinner. {quote} > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > > See the https://community.jboss.org/thread/239391 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 03:00:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 7 Apr 2014 03:00:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13541) Photoalbum - JPA tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13541. ---------------------------- JPA tests are running and passing. Closing. > Photoalbum - JPA tests > ---------------------- > > Key: RF-13541 > URL: https://issues.jboss.org/browse/RF-13541 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha1 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.6 > > > In the photoalbum POM there's a profile for running some Arquillian tests. (Basic CRUD) > It's not currently runnable (outdated dependencies and/or settings). > Most of the tests are missing some dependencies but {{UserManagementTest}} and {{UserBeanTest}} seem to require a large number of class dependencies to run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 03:22:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 7 Apr 2014 03:22:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13540) Websphere incarnation of MyFaces renderes optimized resources multiple times In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13540. ---------------------------- As I do not have access to Websphere, leaving the verification to community. Closing. > Websphere incarnation of MyFaces renderes optimized resources multiple times > ---------------------------------------------------------------------------- > > Key: RF-13540 > URL: https://issues.jboss.org/browse/RF-13540 > Project: RichFaces > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.3.5, 5.0.0.Alpha3 > Environment: Myfaces/Websphere on all platforms > Reporter: Sebastian Cramer > Assignee: Sebastian Cramer > Labels: myfaces, websphere > Fix For: 4.3.6 > > > When enabling resource optimization the packed.js (and packed.css) are rendered multiple times. The previous fix for stock myfaces is not effective against IBM's myfaces impl. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 03:22:14 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 7 Apr 2014 03:22:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959507#comment-12959507 ] Juraj H?ska edited comment on RF-13250 at 4/7/14 3:22 AM: ---------------------------------------------------------- Verified for 4.3.6.Final. Can be closed when verified for 5.Alpha4. was (Author: jhuska): Verified for 4.3.6.Final. > Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final > -------------------------------------------------------------- > > Key: RF-13250 > URL: https://issues.jboss.org/browse/RF-13250 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4, 4.3.5 > Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5 > Reporter: Milo van der Zee > Assignee: Juraj H?ska > Labels: memoryleak > Fix For: 4.3.6, 5.0.0.Alpha4 > > Attachments: rf.patch > > > Hello, > I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone. > I also started seeing this message lot's of times: > {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}} > I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory. > In the crashed system heap dump I see a lot of: > - AtomicBoolean (751.000, 15.0MB) > - ConcurrentLinkedQueue > - AtmospereRequest$Builder (60.042, 13.8MB) > To me it looks like it has something to do with Atmosphere. Any ideas? > Thanks, > Milo van der Zee -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:22:13 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:22:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13599) fileupload: serverError on upload on WildFly In-Reply-To: References: Message-ID: Ji?? ?tefek created RF-13599: -------------------------------- Summary: fileupload: serverError on upload on WildFly Key: RF-13599 URL: https://issues.jboss.org/browse/RF-13599 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.3.6 Environment: WildFly 8.0.0.Final, (worked in EAP 6.2) Reporter: Ji?? ?tefek # deploy metamer and open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml # upload a file (size < 10KB) * expected: file is uploaded * have: server error -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:24:13 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:24:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13599) fileupload: serverError on upload on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13599: ----------------------------- Affects Version/s: 4.3.5 > fileupload: serverError on upload on WildFly > -------------------------------------------- > > Key: RF-13599 > URL: https://issues.jboss.org/browse/RF-13599 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5, 4.3.6 > Environment: WildFly 8.0.0.Final, (worked in EAP 6.2) > Reporter: Ji?? ?tefek > > # deploy metamer and open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml > # upload a file (size < 10KB) > * expected: file is uploaded > * have: server error -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:30:13 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:30:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek moved RFPL-3324 to RF-13600: ---------------------------------------- Project: RichFaces (was: RichFaces Planning) Key: RF-13600 (was: RFPL-3324) > metamer: malformedXML error on each ajax request > ------------------------------------------------ > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, EAP 6.2 > Reporter: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3. > 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) 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:32:12 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:32:12 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13600: ----------------------------- Description: Works in 5.0.x and 4.5.x Metamer but not in 4.3 (tried with RF 4.3.5, and 4.3.6). 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) 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} was: Works in 5.0.x and 4.5.x Metamer but not in 4.3. 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) 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} > metamer: malformedXML error on each ajax request > ------------------------------------------------ > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, EAP 6.2 > Reporter: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3 (tried with RF 4.3.5, and 4.3.6). > 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) 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:32:13 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:32:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13600: ----------------------------- Description: Works in 5.0.x and 4.5.x Metamer but not in 4.3 (tried with RF 4.3.5, and 4.3.6). 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} was: Works in 5.0.x and 4.5.x Metamer but not in 4.3 (tried with RF 4.3.5, and 4.3.6). 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) 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} > metamer: malformedXML error on each ajax request > ------------------------------------------------ > > Key: RF-13600 > URL: https://issues.jboss.org/browse/RF-13600 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, EAP 6.2 > Reporter: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3 (tried with RF 4.3.5, and 4.3.6). > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:40:13 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:40:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13600: ----------------------------- Affects Version/s: 4.3.6 > metamer: malformedXML error on each ajax request > ------------------------------------------------ > > 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.6 > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, EAP 6.2 > Reporter: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3 (tried with RF 4.3.5, and 4.3.6). > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:42:13 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:42:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13600: ----------------------------- Description: Works in 5.0.x and 4.5.x Metamer but not in 4.3 (works with RF 4.3.5). 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} was: Works in 5.0.x and 4.5.x Metamer but not in 4.3 (tried with RF 4.3.5, and 4.3.6). 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} > metamer: malformedXML error on each ajax request > ------------------------------------------------ > > 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.6 > Environment: 4.3.x Metamer > WildFly 8.0.0.Final, EAP 6.2 > Reporter: Ji?? ?tefek > > Works in 5.0.x and 4.5.x Metamer but not in 4.3 (works with RF 4.3.5). > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:42:13 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:42:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13600) metamer: malformedXML error on each ajax request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ji?? ?tefek updated RF-13600: ----------------------------- Environment: 4.3.x Metamer WildFly 8.0.0.Final, (works on EAP 6.2) was: 4.3.x Metamer WildFly 8.0.0.Final, EAP 6.2 > metamer: malformedXML error on each ajax request > ------------------------------------------------ > > 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.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 (works with RF 4.3.5). > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:44:14 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:44:14 -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 updated RF-13600: ----------------------------- Summary: metamer: malformedXML error on each ajax request on WildFly (was: metamer: malformedXML error on each ajax request) > 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.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 (works with RF 4.3.5). > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:44:14 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:44:14 -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 updated RF-13600: ----------------------------- Description: Works in 5.0.x and 4.5.x Metamer but not in 4.3 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} was: Works in 5.0.x and 4.5.x Metamer but not in 4.3 (works with RF 4.3.5). 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} > 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.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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:44:14 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:44:14 -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 updated RF-13600: ----------------------------- Affects Version/s: 4.3.5 > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 04:44:15 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Mon, 7 Apr 2014 04:44: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 updated RF-13600: ----------------------------- Description: 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} was: Works in 5.0.x and 4.5.x Metamer but not in 4.3 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} > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 7 07:04:13 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Mon, 7 Apr 2014 07:04:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959662#comment-12959662 ] Matej Novotny commented on RF-13595: ------------------------------------ [~michaelb80], first of all, thanks for the example it's much easier to reproduce something with it :-) Now as for results, I tried your example and indeed it does not work and behaves exactly as you described in the comment above. With added a4j:ajax it works (for this simple case - we already have such reproducer in Metamer), so I modified the example to rich:calendar and accordingly I changed validation method. Finally I added it to Metamer (testing app) - you can see the [xhtml page here|https://github.com/richfaces/richfaces-qa/blob/4.3.x/metamer/application/src/main/webapp/components/richValidator/rf-13595.xhtml] and the bean is [here|https://github.com/richfaces/richfaces-qa/blob/4.3.x/metamer/application/src/main/java/org/richfaces/tests/metamer/bean/issues/RF13595.java] and the test I created is [here|https://github.com/richfaces/richfaces-qa/blob/4.3.x/metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/richValidator/TestRF13595.java]. This example does not work anymore even with added a4j:ajax (in this case I used change event). Could you please confirm that this is what you meant by replacing the input field with calendar, eg. the use-case you meant? [~bleathem] as for simple example/reproducer we already have [this test|https://github.com/richfaces/richfaces-qa/blob/4.3.x/metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/richValidator/TestRF12031.java] which is mentioned in related RF-12031. That is why I created this more complex example where the workaround does not work. Is there anything else I can do? > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Assignee: Matej Novotny > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 03:34:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 8 Apr 2014 03:34:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: Juraj H?ska created RF-13601: -------------------------------- Summary: DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor Key: RF-13601 URL: https://issues.jboss.org/browse/RF-13601 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.3.6 Environment: Firefox 25 EAP & JBoss AS 7.1.1.Final Reporter: Juraj H?ska Priority: Critical {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. Sorting functionality does not work, the header facet is visually broken and following JS error is thrown into the console: {{TypeError: RichFaces.ui.DataTable is not a constructor}}. The rendered code contains following usage of the DataTable constructor: {code} new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) {code} It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 03:36:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 8 Apr 2014 03:36:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13601: ----------------------------- Attachment: brokenDataTableSortingHeaderColumns.png > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor > --------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Critical > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > Sorting functionality does not work, the header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 03:38:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 8 Apr 2014 03:38:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13601: ----------------------------- Steps to Reproduce: # deploy Metamer and load: http://localhost:8080/metamer/faces/components/richDataTable/sorting-using-column.xhtml # refresh the page, or set attribute {{sortMode}} to multi # see broken header of the table and JS error in the console > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor > --------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Critical > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > Sorting functionality does not work, the header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 03:40:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 8 Apr 2014 03:40:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13601: ----------------------------- Description: {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. The header facet is visually broken and following JS error is thrown into the console: {{TypeError: RichFaces.ui.DataTable is not a constructor}}. The rendered code contains following usage of the DataTable constructor: {code} new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) {code} It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. It worked in {{4.3.5.Final}}. was: {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. Sorting functionality does not work, the header facet is visually broken and following JS error is thrown into the console: {{TypeError: RichFaces.ui.DataTable is not a constructor}}. The rendered code contains following usage of the DataTable constructor: {code} new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) {code} It worked in {{4.3.5.Final}}. > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor > --------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Critical > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 03:48:14 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 8 Apr 2014 03:48:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13601: ----------------------------- Environment: Firefox 25 & Chrome EAP & JBoss AS 7.1.1.Final was: Firefox 25 EAP & JBoss AS 7.1.1.Final > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor > --------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 & Chrome > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Critical > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 03:48:14 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 8 Apr 2014 03:48:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959977#comment-12959977 ] Juraj H?ska commented on RF-13601: ---------------------------------- Chrome is throwing similar: {{Uncaught TypeError: undefined is not a function sorting-using-column.xhtml:244}} > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor > --------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 & Chrome > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Critical > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 03:50:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 8 Apr 2014 03:50:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959978#comment-12959978 ] Juraj H?ska commented on RF-13601: ---------------------------------- The showcase dataTable with sorting columns works fine. > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor > --------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 & Chrome > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Critical > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 03:52:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 8 Apr 2014 03:52:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12959979#comment-12959979 ] Pavol Pitonak commented on RF-11736: ------------------------------------ [~jstefek], please try to reproduce using either information in this issues or using reproducer in https://bugzilla.redhat.com/show_bug.cgi?id=1063222 > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Fix For: 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 05:02:13 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Tue, 8 Apr 2014 05:02:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960003#comment-12960003 ] Ji?? ?tefek commented on RF-11736: ---------------------------------- I can confirm, that this issue is still reproducible with latest RF 4 (and 4.5, 5). This issue can be reproduced in Metamer. # deploy Metamer and open http://localhost:8080/metamer/faces/components/richPopupPanel/simple.xhtml # set @top and @left to 'auto' (should be set by default) # set @domElementAttachment to 'parent' # open, close and open the popupPanel (the fastest way is with the JS API buttons) * have: the panel is relocated after the second open > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Fix For: 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 05:32:15 2014 From: issues at jboss.org (Igor Bolshakov (JIRA)) Date: Tue, 8 Apr 2014 05:32:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Bolshakov updated RF-13592: -------------------------------- Labels: (was: waiting_on_user) > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Pavol Pitonak > Priority: Critical > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 06:10:14 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 8 Apr 2014 06:10:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13592: ---------------------------------- Assignee: Juraj H?ska (was: Pavol Pitonak) Juraj, please try to reproduce with attached reproducer. > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Juraj H?ska > Priority: Critical > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 16:10:13 2014 From: issues at jboss.org (Michael B (JIRA)) Date: Tue, 8 Apr 2014 16:10:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960329#comment-12960329 ] Michael B commented on RF-13595: -------------------------------- Thanks for verifying the problem, - glad to hear that the test project was useful! And to answer your question: yes, that's exactly what I meant by replacing the inputText with the calendar component. I've also tried with some (of the many) other events which the calendar component provides, but with no success so far. Also I would imagine, that the same problem could also occur when using other input components with the validator (like rich:select etc.), but I haven't confirmed that by changing the test case so far. So basically having a workaround for the calendar component would by nice on the short run, but the general problem would still remain. BTW: the instanceof-check in the validation-method (Line 25) of your adapted test class should probably also be changed to a Date, otherwise the check would never work - even if the validation method would actually be invoked at some point... - but never mind that detail. > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Assignee: Matej Novotny > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 20:28:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 8 Apr 2014 20:28:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960362#comment-12960362 ] Brian Leathem commented on RF-13601: ------------------------------------ This is possibly a metamer issue. If I checkout the 4.3.5.20140113-Final metamer tag and run it against the staged RichFaces {{4.3.6.Final}} jars then everything works as expected. Please confirm this is a metamer issue. In the future we should consider verifying whether reported framework regressions are metamer regressions, as this took a fair amount of time to narrow down. > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor > --------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 & Chrome > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Priority: Critical > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 20:28:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 8 Apr 2014 20:28:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13601: ------------------------------- Assignee: Juraj H?ska > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor > --------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 & Chrome > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Critical > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 8 23:28:13 2014 From: issues at jboss.org (Walter Maidub (JIRA)) Date: Tue, 8 Apr 2014 23:28:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13602) Problem with ajax request in Internet Explorer 11 In-Reply-To: References: Message-ID: Walter Maidub created RF-13602: ---------------------------------- Summary: 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 Fix For: 4.0.0.Final 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.
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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 9 03:14:12 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 9 Apr 2014 03:14:12 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960386#comment-12960386 ] Juraj H?ska commented on RF-13601: ---------------------------------- I can confirm that it is metamer issue. Now trying to find the change which caused it. > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor > --------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 & Chrome > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Priority: Critical > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 9 03:14:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 9 Apr 2014 03:14:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13601: ----------------------------- Priority: Major (was: Critical) > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor > --------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 & Chrome > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 9 03:14:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 9 Apr 2014 03:14:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable i s not a constructor - Metamer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13601: ----------------------------- Summary: DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable i s not a constructor - Metamer (was: DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable is not a constructor) > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable i s not a constructor - Metamer > -------------------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 & Chrome > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 9 03:30:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 9 Apr 2014 03:30:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable i s not a constructor - Metamer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960390#comment-12960390 ] Juraj H?ska commented on RF-13601: ---------------------------------- The issue was introduced by [this|https://github.com/richfaces/richfaces-qa/commit/38b9b1192d2eab5510c5554b757516ad6b42e6d9] commit. Basically it does not work with {{SessionScoped}} managed bean. In {{4.3.5}}, the {{RichDataTableBean}} was {{ViewScoped}}. The motivation for changing the scope were testing of stateless views - RFPL-3267. > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable i s not a constructor - Metamer > -------------------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 & Chrome > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 9 04:06:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 9 Apr 2014 04:06:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13601) DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable i s not a constructor - Metamer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska resolved RF-13601. ------------------------------ Resolution: Rejected Rejected as it is not a bug of framework but bug in the Metamer application. It is caused by using both component binding and {{SessionScoped}} beans. Created RFPL-3325 with more info to fix the Metamer. > DataTable - when has sorting columns - TypeError: RichFaces.ui.DataTable i s not a constructor - Metamer > -------------------------------------------------------------------------------------------------------- > > Key: RF-13601 > URL: https://issues.jboss.org/browse/RF-13601 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.6 > Environment: Firefox 25 & Chrome > EAP & JBoss AS 7.1.1.Final > Reporter: Juraj H?ska > Assignee: Juraj H?ska > Labels: regression > Attachments: brokenDataTableSortingHeaderColumns.png > > > {{DataTable}} with multiple sorting columns does not work properly. After initial render it looks good, but then after refresh it is broken. > The header facet is visually broken and following JS error is thrown into the console: > {{TypeError: RichFaces.ui.DataTable is not a constructor}}. > The rendered code contains following usage of the DataTable constructor: > {code} > new RichFaces.ui.DataTable("form:richDataTable",{"ajaxEventOptions":{} } ) > {code} > It seems that the sorting functionality works even though there is JS error and it is visually broken. However, the functional tests failed so I need to investigate more. > It worked in {{4.3.5.Final}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 9 06:10:13 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 9 Apr 2014 06:10:13 -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=12960439#comment-12960439 ] Michal Petrov commented on RF-13600: ------------------------------------ There has been a change in viewState handling between JSF 2.0 and 2.2. In 2.0 the expected id of the viewState input element is {{form:javax.faces.ViewState}}, in 2.2 it's {{form:javax.faces.ViewState}}{color:red}{{:0}}{color}, the XML response from the server uses the old format while the JavaScript object handling the update expects the new one. There are similar failures if you deploy Metamer 5.0.x to AS 7.1.1. It's also been reported in [JAVASERVERFACES-2907|https://java.net/jira/browse/JAVASERVERFACES-2907] > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 9 07:50:13 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 9 Apr 2014 07:50:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13581) Remove components from the framework module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13581. -------------------------------- Resolution: Done I have removed components and component resources from framework, this also includes the chart component that will be ported into 4.5.x later. > Remove components from the framework module > ------------------------------------------- > > Key: RF-13581 > URL: https://issues.jboss.org/browse/RF-13581 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > RichFaes 4.5 has it's components in the components module. The components in the framework module should be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 9 07:52:13 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 9 Apr 2014 07:52:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13584) Backport the RF 5 component fixes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960471#comment-12960471 ] Michal Petrov commented on RF-13584: ------------------------------------ When I was removing the components (RF-13581) I have been comparing the files and merging where it seemed necessary, so some of these backports are already resolved. > Backport the RF 5 component fixes > --------------------------------- > > Key: RF-13584 > URL: https://issues.jboss.org/browse/RF-13584 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > Some fixes were applied to the RichFaces 5 components that should be backported to RF 4.5. These include (but are not limited to) the fixes labelled "45x": > https://issues.jboss.org/browse/RF-13520?jql=project%3DRF%20and%20labels%20%3D%2045x -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 9 11:10:14 2014 From: issues at jboss.org (Eddie Cheung (JIRA)) Date: Wed, 9 Apr 2014 11:10:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13443) Rerender after Ajax Request in Internet Explorer 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960567#comment-12960567 ] Eddie Cheung commented on RF-13443: ----------------------------------- Are you meaning this fix is under the latest Richface library? Or I should modify the ajax.js that you have mentioned? If latest RichFace library, would you please tell which version? If ajax.js, I don't really where it is (even you have mentioned richfaces-imp/ort/ajax4jsf/javascript/scripts). Many thanks! > Rerender after Ajax Request in Internet Explorer 11 > --------------------------------------------------- > > Key: RF-13443 > URL: https://issues.jboss.org/browse/RF-13443 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.3.4.Final > Reporter: Osman Y?ksel > Priority: Critical > Fix For: 3.Future > > > By using a4j:Funtcion in combination with "rerender" this is not working on Internet Explorer 11. The problem ist, that after Ajax-Request the Result in XML can not be correct append to the body. (Affects in version 3.3.4 Final) > Reason is simple: > Microsoft has changed the User-Agent for Internet Explorer 11 > Before: > IE10: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0) > Now: > IE11: Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv 11.0) like Gecko > Details: http://msdn.microsoft.com/en-us/library/ie/bg182625(v=vs.85).aspx > In richfaces-imp.jar there is the AJAX.js-File wich rerender the result ofthe Ajax-Request. Here is also Sarissa to identify the Browser. > Because of missing "msie", Sarissa can not identifiy an Internet Explorer 11 as an Internet Explorer. > That means, tha AJAX.js in "richfaces-imp/ort/ajax4jsf/javascript/scripts" has to be modify. > Before: > Sarissa._SARISSA_IS_IE = document.all && window.ActiveXObject && navigator.userAgent.toLowerCase().indexOf("msie") > -1 && navigator.userAgent.toLowerCase().indexOf("opera") == -1 > Now: > Sarissa._SARISSA_IS_IE = (document.all && window.ActiveXObject && navigator.userAgent.toLowerCase().indexOf("msie") > -1 && navigator.userAgent.toLowerCase().indexOf("opera") == -1) || (navigator.userAgent.toLowerCase().indexOf("like gecko") > -1 && navigator.userAgent.toLowerCase().indexOf("11.") > -1); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 03:14:13 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 10 Apr 2014 03:14:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13585) Drop 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 ] Michal Petrov resolved RF-13585. -------------------------------- Assignee: Michal Petrov Resolution: Done > Drop 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 10:34:15 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 10 Apr 2014 10:34:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960848#comment-12960848 ] Juraj H?ska commented on RF-13592: ---------------------------------- I have reproduced the issue with the attached reproducer. It can be reproduced on all these RichFaces versions: {{4.3.6, 4.3.5, 4.3.4}} and below. I have also reproduced it on JBoss AS 7.1.1.Final and on Tomcats with upgraded JSF impls. In Firefox, after trying to send a message on a re-rendered push, I am getting HTTP GET request with this error (also a reference to atmosphere.js file): {{code}} XML Parsing Error: no element found Location: moz-nullprincipal:{cb3f18af-a17e-4496-b336-40bee0e97e6b} Line Number 1, Column 1: {{code}} > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Juraj H?ska > Priority: Critical > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 10:34:16 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 10 Apr 2014 10:34:16 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12960848#comment-12960848 ] Juraj H?ska edited comment on RF-13592 at 4/10/14 10:32 AM: ------------------------------------------------------------ I have reproduced the issue with the attached reproducer. It can be reproduced on all these RichFaces versions: {{4.3.6, 4.3.5, 4.3.4}} and below. I have also reproduced it on JBoss AS 7.1.1.Final and on Tomcats with upgraded JSF impls. In Firefox, after trying to send a message on a re-rendered push, I am getting HTTP GET request with this error (also a reference to atmosphere.js file): {code} XML Parsing Error: no element found Location: moz-nullprincipal:{cb3f18af-a17e-4496-b336-40bee0e97e6b} Line Number 1, Column 1: {code} was (Author: jhuska): I have reproduced the issue with the attached reproducer. It can be reproduced on all these RichFaces versions: {{4.3.6, 4.3.5, 4.3.4}} and below. I have also reproduced it on JBoss AS 7.1.1.Final and on Tomcats with upgraded JSF impls. In Firefox, after trying to send a message on a re-rendered push, I am getting HTTP GET request with this error (also a reference to atmosphere.js file): {{code}} XML Parsing Error: no element found Location: moz-nullprincipal:{cb3f18af-a17e-4496-b336-40bee0e97e6b} Line Number 1, Column 1: {{code}} > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Juraj H?ska > Priority: Critical > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 10:44:13 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 10 Apr 2014 10:44:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13592: ----------------------------- Assignee: (was: Juraj H?ska) > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Priority: Critical > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 12:14:12 2014 From: issues at jboss.org (Nestor Armando Bohorquez (JIRA)) Date: Thu, 10 Apr 2014 12:14:12 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear In-Reply-To: References: Message-ID: Nestor Armando Bohorquez created RF-13603: --------------------------------------------- Summary: unsupported classversion 51.0 while deploying ear Key: RF-13603 URL: https://issues.jboss.org/browse/RF-13603 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 5.0.0.Alpha3 Environment: Windows 7, Weblogic 10.3.5, JDK 6 Reporter: Nestor Armando Bohorquez An exception is thrown when applicattion is been deployed: java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) at java.lang.ClassLoader.defineClass(ClassLoader.java:614) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) at java.lang.ClassLoader.loadClass(ClassLoader.java:305) at java.lang.ClassLoader.loadClass(ClassLoader.java:246) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) I'm using this in the web.xml file. Resource Servlet org.richfaces.servlet.ResourceServlet 1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:32:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:32:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11427) rich:tab - actionListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11427: ------------------------------- Fix Version/s: 4.3.7 (was: 5-Tracking) > rich:tab - actionListener > ------------------------- > > Key: RF-11427 > URL: https://issues.jboss.org/browse/RF-11427 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1 > Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d > Metamer 4.1.0-SNAPSHOT r.22728 > Mojarra 2.1.2-FCS > Apache Tomcat 7.0.16 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 18.0.1025.168 @ Linux i686 > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: ci_issue > Fix For: 4.3.7 > > > It seems that the actionListener attribute doesn't work. > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # open tab2 > # open tab1 (action and action listener are invoked) > # open tab2 > # open tab1 (action and action listener are *NOT* invoked) > # open tab1 (action and action listener are invoked) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:32:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:32:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11427) rich:tab - actionListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11427: ------------------------------- Labels: ci_issue patch_proposed (was: ci_issue) > rich:tab - actionListener > ------------------------- > > Key: RF-11427 > URL: https://issues.jboss.org/browse/RF-11427 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1 > Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d > Metamer 4.1.0-SNAPSHOT r.22728 > Mojarra 2.1.2-FCS > Apache Tomcat 7.0.16 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 18.0.1025.168 @ Linux i686 > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: ci_issue, patch_proposed > Fix For: 4.3.7 > > > It seems that the actionListener attribute doesn't work. > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # open tab2 > # open tab1 (action and action listener are invoked) > # open tab2 > # open tab1 (action and action listener are *NOT* invoked) > # open tab1 (action and action listener are invoked) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:34:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:34:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13569) Photoalbum: the change of users avatar doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13569: ------------------------------- Fix Version/s: 4.3.7 (was: 4.3.6) > Photoalbum: the change of users avatar doesn't work > --------------------------------------------------- > > Key: RF-13569 > URL: https://issues.jboss.org/browse/RF-13569 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.7 > > > # After the user's avatar is changed, the avatar is not updated in comments or search results (already resolved by https://github.com/richfaces4/dev-examples/commit/942575579f4e80c2d8dac5c3e1e57f8e706ee0cc) > # the avatar is not updated in the users profile after a second change of the avatar (but is updated in search result and in comments) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:36:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:36:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13592: ------------------------------- Fix Version/s: 4.3.7 > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Priority: Critical > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:36:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:36:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13592: ------------------------------- Labels: gss (was: ) > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Priority: Critical > Labels: gss > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:38:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:38:13 -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: ------------------------------- Fix Version/s: 4.3.7 > 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 > Fix For: 4.3.7 > > > Drag/Drop support should be added to file upload component . > Like the primefaces fileUploadDnd : http://www.primefaces.org/showcase/ui/fileUploadDnd.jsf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:38:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:38:13 -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: ------------------------------- Assignee: Michal Petrov > 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.3.7 > > > Drag/Drop support should be added to file upload component . > Like the primefaces fileUploadDnd : http://www.primefaces.org/showcase/ui/fileUploadDnd.jsf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:40:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:40:14 -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: ------------------------------- Fix Version/s: 4.5.0.Alpha3 (was: 4.3.7) > 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 > > > Drag/Drop support should be added to file upload component . > Like the primefaces fileUploadDnd : http://www.primefaces.org/showcase/ui/fileUploadDnd.jsf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:40:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:40:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13598: ------------------------------- Fix Version/s: 4.3.7 > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.7 > > > See the https://community.jboss.org/thread/239391 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:40:15 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:40:15 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13599) fileupload: serverError on upload on WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13599. -------------------------------- Resolution: Rejected This is a known issue involving the fileuplaod component and JSF 2.2. It will be addressed with the upcoming 4.5 release of RichFaces. > fileupload: serverError on upload on WildFly > -------------------------------------------- > > Key: RF-13599 > URL: https://issues.jboss.org/browse/RF-13599 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5, 4.3.6 > Environment: WildFly 8.0.0.Final, (worked in EAP 6.2) > Reporter: Ji?? ?tefek > > # deploy metamer and open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml > # upload a file (size < 10KB) > * expected: file is uploaded > * have: server error -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:42:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:42:13 -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 updated RF-13602: ------------------------------- Fix Version/s: (was: 4.0.0.Final) > 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 > Labels: ajax, ie11, problem > > 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. > > required="true" listWidth="320px" styleClass="rf-select-large-width"> > > execute="@this" > render="upload,seccionCarga" > listener="#{Bean.activarPanelCarga}" /> > > > > > > > > > > > > >
> styleClass="top" > . > . > . > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:42:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:42:13 -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 updated RF-13602: ------------------------------- Description: 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}
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? was: 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.
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? > 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 > Labels: ajax, ie11, problem > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:44:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:44:13 -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:comment-tabpanel&focusedCommentId=12960961#comment-12960961 ] Brian Leathem commented on RF-13602: ------------------------------------ This is likely a duplicate of RF-13531 that was resolved in the imminent RichFaces 4.3.6.Final release. Please confirm whether this is still an issue once that release has been made available. > 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 > Labels: ajax, ie11, problem > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:44:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:44:14 -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 updated RF-13602: ------------------------------- Labels: ie11 waiting_on_user (was: ajax ie11 problem) > 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 > Labels: ie11, waiting_on_user > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:46:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:46:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13603: ---------------------------------- Assignee: Pavol Pitonak QE please verify > unsupported classversion 51.0 while deploying ear > ------------------------------------------------- > > Key: RF-13603 > URL: https://issues.jboss.org/browse/RF-13603 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Environment: Windows 7, Weblogic 10.3.5, JDK 6 > Reporter: Nestor Armando Bohorquez > Assignee: Pavol Pitonak > Labels: ResourceServlet, classversion > > An exception is thrown when applicattion is been deployed: > {code} > java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) > at java.lang.ClassLoader.defineClass(ClassLoader.java:614) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) > at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) > at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) > at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) > at java.lang.ClassLoader.loadClass(ClassLoader.java:305) > at java.lang.ClassLoader.loadClass(ClassLoader.java:246) > at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) > at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) > at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) > at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) > at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) > at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) > at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) > at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) > at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) > at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) > at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) > at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) > at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) > at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) > at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) > at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) > at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) > {code} > I'm using this in the web.xml file. > {code} > > Resource Servlet > org.richfaces.servlet.ResourceServlet > 1 > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:46:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:46:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13603: ------------------------------- Steps to Reproduce: 1. Use this in web.xml: {code} Resource Servlet org.richfaces.servlet.ResourceServlet 1 {code} 2. Deploy was: 1. Use this in web.xml: Resource Servlet org.richfaces.servlet.ResourceServlet 1 2. Deploy > unsupported classversion 51.0 while deploying ear > ------------------------------------------------- > > Key: RF-13603 > URL: https://issues.jboss.org/browse/RF-13603 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Environment: Windows 7, Weblogic 10.3.5, JDK 6 > Reporter: Nestor Armando Bohorquez > Labels: ResourceServlet, classversion > > An exception is thrown when applicattion is been deployed: > {code} > java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) > at java.lang.ClassLoader.defineClass(ClassLoader.java:614) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) > at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) > at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) > at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) > at java.lang.ClassLoader.loadClass(ClassLoader.java:305) > at java.lang.ClassLoader.loadClass(ClassLoader.java:246) > at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) > at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) > at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) > at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) > at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) > at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) > at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) > at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) > at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) > at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) > at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) > at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) > at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) > at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) > at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) > at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) > at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) > {code} > I'm using this in the web.xml file. > {code} > > Resource Servlet > org.richfaces.servlet.ResourceServlet > 1 > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:46:14 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:46:14 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13603: ------------------------------- Description: An exception is thrown when applicattion is been deployed: {code} java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) at java.lang.ClassLoader.defineClass(ClassLoader.java:614) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) at java.lang.ClassLoader.loadClass(ClassLoader.java:305) at java.lang.ClassLoader.loadClass(ClassLoader.java:246) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) {code} I'm using this in the web.xml file. {code} Resource Servlet org.richfaces.servlet.ResourceServlet 1 {code} was: An exception is thrown when applicattion is been deployed: java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) at java.lang.ClassLoader.defineClass(ClassLoader.java:614) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) at java.lang.ClassLoader.loadClass(ClassLoader.java:305) at java.lang.ClassLoader.loadClass(ClassLoader.java:246) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) I'm using this in the web.xml file. Resource Servlet org.richfaces.servlet.ResourceServlet 1 > unsupported classversion 51.0 while deploying ear > ------------------------------------------------- > > Key: RF-13603 > URL: https://issues.jboss.org/browse/RF-13603 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Environment: Windows 7, Weblogic 10.3.5, JDK 6 > Reporter: Nestor Armando Bohorquez > Labels: ResourceServlet, classversion > > An exception is thrown when applicattion is been deployed: > {code} > java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) > at java.lang.ClassLoader.defineClass(ClassLoader.java:614) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) > at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) > at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) > at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) > at java.lang.ClassLoader.loadClass(ClassLoader.java:305) > at java.lang.ClassLoader.loadClass(ClassLoader.java:246) > at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) > at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) > at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) > at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) > at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) > at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) > at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) > at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) > at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) > at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) > at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) > at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) > at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) > at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) > at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) > at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) > at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) > {code} > I'm using this in the web.xml file. > {code} > > Resource Servlet > org.richfaces.servlet.ResourceServlet > 1 > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 10 18:48:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 10 Apr 2014 18:48:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13595: ------------------------------- Fix Version/s: 4.5-Tracking > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Assignee: Matej Novotny > Fix For: 4.5-Tracking > > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 11 03:32:13 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 11 Apr 2014 03:32:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13603: ---------------------------------- Assignee: Matej Novotny (was: Pavol Pitonak) > unsupported classversion 51.0 while deploying ear > ------------------------------------------------- > > Key: RF-13603 > URL: https://issues.jboss.org/browse/RF-13603 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Environment: Windows 7, Weblogic 10.3.5, JDK 6 > Reporter: Nestor Armando Bohorquez > Assignee: Matej Novotny > Labels: ResourceServlet, classversion > > An exception is thrown when applicattion is been deployed: > {code} > java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) > at java.lang.ClassLoader.defineClass(ClassLoader.java:614) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) > at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) > at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) > at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) > at java.lang.ClassLoader.loadClass(ClassLoader.java:305) > at java.lang.ClassLoader.loadClass(ClassLoader.java:246) > at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) > at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) > at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) > at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) > at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) > at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) > at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) > at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) > at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) > at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) > at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) > at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) > at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) > at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) > at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) > at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) > at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) > {code} > I'm using this in the web.xml file. > {code} > > Resource Servlet > org.richfaces.servlet.ResourceServlet > 1 > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 11 13:48:13 2014 From: issues at jboss.org (Serge Rogatch (JIRA)) Date: Fri, 11 Apr 2014 13:48:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13604) rich:editor doesn't render In-Reply-To: References: Message-ID: Serge Rogatch created RF-13604: ---------------------------------- Summary: rich:editor doesn't render Key: RF-13604 URL: https://issues.jboss.org/browse/RF-13604 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Serge Rogatch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 11 13:50:13 2014 From: issues at jboss.org (Serge Rogatch (JIRA)) Date: Fri, 11 Apr 2014 13:50:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13604) rich:editor doesn't render In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Serge Rogatch updated RF-13604: ------------------------------- Affects Version/s: 4.3.5 > rich:editor doesn't render > -------------------------- > > 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 > Reporter: Serge Rogatch > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 11 14:26:13 2014 From: issues at jboss.org (Serge Rogatch (JIRA)) Date: Fri, 11 Apr 2014 14:26:13 -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 ] Serge Rogatch updated RF-13604: ------------------------------- Summary: rich:editor is flickering on mouse hover (was: rich:editor doesn't render) Description: 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. Steps to Reproduce: 1. In Eclipse, create new Dynamic Web Project: select "GlassFish 4.0" as the target runtime, select 3.1 as Dynamic web module version, Default Configuration for GlassFish 4.0 as Configuration 2. Navigate to directory WebContent/WEB-INF/lib and put the following files there - cssparser-0.9.9.jar - guava-r09.jar - richfaces-components-api-4.3.5.Final.jav - richfaces-components-ui-4.3.5.Final.jar - richfaces-core-api-4.3.5.Final.jar - richfaces-core-impl-4.3.5.Final.jar - sac-1.3.jar 3. Right-click on the project in Eclipse, click Properties, then go to Project Facets and enable checkbox to the left of Java Server Faces (ensure that version is 2.2). Ensure that also the following checkboxes are enabled: - Dynamic Web Module, version 3.1 - Java, version 1.7 - JavaScript, version 1.0 Click "Apply" button, then click "OK" button. 4. Under WebContent directory, create new XHTML file called test.xhtml with the following content: Output from Editor (Updating) 5. Under Java Resources directory src, create file EditorBean.java with the following content: import javax.faces.bean.ManagedBean; import javax.faces.bean.SessionScoped; @ManagedBean(name="editorBean") @SessionScoped() public class EditorBean { private String value = ""; public String getValue() { return value; } public void setValue(String value) { this.value = value; } } 6. Right-click on test.xhtml, select "Debug As"->"Debug on Server", of the servers select GlassFish 4.0 and click button "Finish". 7. Navigate to the /faces/test.xhtml in Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659). 8. Hover the mouse over the toolbar of the editor. Note that the buttons of the editor start to move in unreasonable way (Internet Explorer) or tooltips of the buttons start to flicker (Chrome). Labels: editor glassfish jsf22 (was: ) 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) Affects: User Experience > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 11 14:32:12 2014 From: issues at jboss.org (Serge Rogatch (JIRA)) Date: Fri, 11 Apr 2014 14:32:12 -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 ] Serge Rogatch updated RF-13604: ------------------------------- Steps to Reproduce: 1. In Eclipse, create new Dynamic Web Project: select "GlassFish 4.0" as the target runtime, select 3.1 as Dynamic web module version, Default Configuration for GlassFish 4.0 as Configuration 2. Navigate to directory WebContent/WEB-INF/lib and put the following files there - cssparser-0.9.9.jar - guava-r09.jar - richfaces-components-api-4.3.5.Final.jav - richfaces-components-ui-4.3.5.Final.jar - richfaces-core-api-4.3.5.Final.jar - richfaces-core-impl-4.3.5.Final.jar - sac-1.3.jar 3. Right-click on the project in Eclipse, click Properties, then go to Project Facets and enable checkbox to the left of Java Server Faces (ensure that version is 2.2). Ensure that also the following checkboxes are enabled: - Dynamic Web Module, version 3.1 - Java, version 1.7 - JavaScript, version 1.0 Click "Apply" button, then click "OK" button. 4. Under WebContent directory, create new XHTML file called test.xhtml with the following content: Output from Editor (Updating) 5. Under Java Resources directory src, create file EditorBean.java with the following content: import javax.faces.bean.ManagedBean; import javax.faces.bean.SessionScoped; @ManagedBean(name="editorBean") @SessionScoped() public class EditorBean { private String value = ""; public String getValue() { return value; } public void setValue(String value) { this.value = value; } } 6. Right-click on test.xhtml, select "Debug As"->"Debug on Server", of the servers select GlassFish 4.0 and click button "Finish". 7. Navigate to the /faces/test.xhtml in Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659). 8. Hover the mouse over the toolbar of the editor. Note that the buttons of the editor start to move in unreasonable way (Internet Explorer) or tooltips of the buttons start to flicker (Chrome). was: 1. In Eclipse, create new Dynamic Web Project: select "GlassFish 4.0" as the target runtime, select 3.1 as Dynamic web module version, Default Configuration for GlassFish 4.0 as Configuration 2. Navigate to directory WebContent/WEB-INF/lib and put the following files there - cssparser-0.9.9.jar - guava-r09.jar - richfaces-components-api-4.3.5.Final.jav - richfaces-components-ui-4.3.5.Final.jar - richfaces-core-api-4.3.5.Final.jar - richfaces-core-impl-4.3.5.Final.jar - sac-1.3.jar 3. Right-click on the project in Eclipse, click Properties, then go to Project Facets and enable checkbox to the left of Java Server Faces (ensure that version is 2.2). Ensure that also the following checkboxes are enabled: - Dynamic Web Module, version 3.1 - Java, version 1.7 - JavaScript, version 1.0 Click "Apply" button, then click "OK" button. 4. Under WebContent directory, create new XHTML file called test.xhtml with the following content: Output from Editor (Updating) 5. Under Java Resources directory src, create file EditorBean.java with the following content: import javax.faces.bean.ManagedBean; import javax.faces.bean.SessionScoped; @ManagedBean(name="editorBean") @SessionScoped() public class EditorBean { private String value = ""; public String getValue() { return value; } public void setValue(String value) { this.value = value; } } 6. Right-click on test.xhtml, select "Debug As"->"Debug on Server", of the servers select GlassFish 4.0 and click button "Finish". 7. Navigate to the /faces/test.xhtml in Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659). 8. Hover the mouse over the toolbar of the editor. Note that the buttons of the editor start to move in unreasonable way (Internet Explorer) or tooltips of the buttons start to flicker (Chrome). > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 14 03:14:34 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Mon, 14 Apr 2014 03:14:34 -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 ] Pavol Pitonak reassigned RF-12132: ---------------------------------- Assignee: Ji?? ?tefek (was: Pavol Pitonak) Jiri, please try to reproduce. > 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 > Environment: Myfaces 2.1.6 > Tomcat 6.0.35 > Reporter: Michael Heinen > Assignee: Ji?? ?tefek > Labels: needs-qe > Fix For: 5-Tracking > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 14 04:54:33 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Mon, 14 Apr 2014 04:54:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12961521#comment-12961521 ] Matej Novotny commented on RF-13595: ------------------------------------ Indeed, the instanceof check is incorrect. I have already fixed that. > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Assignee: Matej Novotny > Fix For: 4.5-Tracking > > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 14 06:54:33 2014 From: issues at jboss.org (abhishek vijra (JIRA)) Date: Mon, 14 Apr 2014 06:54:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost In-Reply-To: References: Message-ID: abhishek vijra created RF-13605: ----------------------------------- Summary: a4j:ajax button click event gets lost Key: RF-13605 URL: https://issues.jboss.org/browse/RF-13605 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.3.6 Reporter: abhishek vijra Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 14 06:56:33 2014 From: issues at jboss.org (abhishek vijra (JIRA)) Date: Mon, 14 Apr 2014 06:56:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] abhishek vijra updated RF-13605: -------------------------------- > a4j:ajax button click event gets lost > ------------------------------------- > > Key: RF-13605 > URL: https://issues.jboss.org/browse/RF-13605 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.6 > Reporter: abhishek vijra > > Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. > Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 14 07:40:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 14 Apr 2014 07:40:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12961570#comment-12961570 ] Michal Petrov commented on RF-13605: ------------------------------------ Like [~avijra] said in the mail, I'm not sure this should be considered a bug. What happens is that the onblur triggers a rerender and so a part of DOM, button included, is replaced. The click on the original button either never happens to begin with, or is not executed since the button doesn't exist any more. Given that the ajax request may take a while to come back I assume the click might still register sometimes. {code}
{code} As far as I understand this should do essentially the same thing, albeit without ajax. The click doesn't trigger either. > a4j:ajax button click event gets lost > ------------------------------------- > > Key: RF-13605 > URL: https://issues.jboss.org/browse/RF-13605 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.6 > Reporter: abhishek vijra > > Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. > Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 14 08:02:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 14 Apr 2014 08:02:34 -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:comment-tabpanel&focusedCommentId=12961581#comment-12961581 ] Michal Petrov commented on RF-13514: ------------------------------------ [~jhuska], after my commits, are there any remaining issues on WildFly 8 Final? As far as AS 7.1.1 is concerned it seems there are issues with more components than just fileUpload. > 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 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 14 08:06:36 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Mon, 14 Apr 2014 08:06:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12961583#comment-12961583 ] Matej Novotny commented on RF-13603: ------------------------------------ Verified, I managed to reproduce this issue. I used kitchensink archetype (5.0.0.Alpha3) which I built with JDK 6 and deployed to JBoss AS 7.1 (again using Java 6). Even without changing the web.xml file I am getting very similar compatibility error (this one comes from Skinbean, but there are more such errors in log, all of them throwing UnsupportedClassVersionError). {code} 13:57:27,188 WARN [org.jboss.modules] (MSC service thread 1-7) Failed to define class org.richfaces.skin.SkinBean in Module "deployment.kitchensink-test.war:main" from Service Module Loader: java.lang.UnsupportedClassVersionError: org/richfaces/skin/SkinBean : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.6.0_24] at java.lang.ClassLoader.defineClass(ClassLoader.java:634) [rt.jar:1.6.0_24] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) [rt.jar:1.6.0_24] at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.Module.loadModuleClass(Module.java:517) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA] at org.jboss.as.web.deployment.jsf.JsfManagedBeanProcessor.deploy(JsfManagedBeanProcessor.java:107) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) [rt.jar:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.6.0_24] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] 13:57:27,221 ERROR [org.jboss.web] (MSC service thread 1-7) JBAS018211: Could not load JSF managed bean class: org.richfaces.skin.SkinBean {code} I will modify steps to reproduce accordingly to my findings. If there is anything else I can do, let me know. > unsupported classversion 51.0 while deploying ear > ------------------------------------------------- > > Key: RF-13603 > URL: https://issues.jboss.org/browse/RF-13603 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Environment: Windows 7, Weblogic 10.3.5, JDK 6 > Reporter: Nestor Armando Bohorquez > Assignee: Matej Novotny > Labels: ResourceServlet, classversion > > An exception is thrown when applicattion is been deployed: > {code} > java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) > at java.lang.ClassLoader.defineClass(ClassLoader.java:614) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) > at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) > at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) > at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) > at java.lang.ClassLoader.loadClass(ClassLoader.java:305) > at java.lang.ClassLoader.loadClass(ClassLoader.java:246) > at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) > at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) > at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) > at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) > at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) > at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) > at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) > at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) > at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) > at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) > at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) > at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) > at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) > at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) > at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) > at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) > at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) > {code} > I'm using this in the web.xml file. > {code} > > Resource Servlet > org.richfaces.servlet.ResourceServlet > 1 > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 14 08:10:33 2014 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Mon, 14 Apr 2014 08:10:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Novotny updated RF-13603: ------------------------------- Steps to Reproduce: # Get RF 5 kitchensink archetype and build it with JDK 6 # Start JBoss AS 7.1 with Java 6 and deploy kitchensink app # See console for errors _______________________________________ ORIGINAL STEPS TO REPRODUCE 1. Use this in web.xml: {code} Resource Servlet org.richfaces.servlet.ResourceServlet 1 {code} 2. Deploy was: 1. Use this in web.xml: {code} Resource Servlet org.richfaces.servlet.ResourceServlet 1 {code} 2. Deploy > unsupported classversion 51.0 while deploying ear > ------------------------------------------------- > > Key: RF-13603 > URL: https://issues.jboss.org/browse/RF-13603 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Environment: Windows 7, Weblogic 10.3.5, JDK 6 > Reporter: Nestor Armando Bohorquez > Assignee: Matej Novotny > Labels: ResourceServlet, classversion > > An exception is thrown when applicattion is been deployed: > {code} > java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) > at java.lang.ClassLoader.defineClass(ClassLoader.java:614) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) > at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) > at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) > at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) > at java.lang.ClassLoader.loadClass(ClassLoader.java:305) > at java.lang.ClassLoader.loadClass(ClassLoader.java:246) > at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) > at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) > at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) > at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) > at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) > at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) > at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) > at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) > at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) > at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) > at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) > at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) > at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) > at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) > at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) > at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) > at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) > {code} > I'm using this in the web.xml file. > {code} > > Resource Servlet > org.richfaces.servlet.ResourceServlet > 1 > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 14 10:58:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 14 Apr 2014 10:58:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov reassigned RF-11736: ---------------------------------- Assignee: Michal Petrov > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Assignee: Michal Petrov > Fix For: 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 15 02:46:34 2014 From: issues at jboss.org (Konstantin Morozov (JIRA)) Date: Tue, 15 Apr 2014 02:46:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13606) WebSphere/MyFaces in 4.3.6 In-Reply-To: References: Message-ID: Konstantin Morozov created RF-13606: --------------------------------------- Summary: 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: 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) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 15 04:32:37 2014 From: issues at jboss.org (abhishek vijra (JIRA)) Date: Tue, 15 Apr 2014 04:32:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] abhishek vijra updated RF-13605: -------------------------------- Attachment: queue.zip > a4j:ajax button click event gets lost > ------------------------------------- > > Key: RF-13605 > URL: https://issues.jboss.org/browse/RF-13605 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.6 > Reporter: abhishek vijra > Attachments: queue.zip > > > Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. > Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 15 06:50:33 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 15 Apr 2014 06:50:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12790) EDT/DT is broken after postback request with Mojarra 2.1.18 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12961956#comment-12961956 ] Pavol Pitonak commented on RF-12790: ------------------------------------ For the record: RichFaces 4.3.6-SNAPSHOT work fine in EAP 6.2.2 and WildFly 8.0.0. > EDT/DT is broken after postback request with Mojarra 2.1.18 > ----------------------------------------------------------- > > Key: RF-12790 > URL: https://issues.jboss.org/browse/RF-12790 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables, regression > Affects Versions: 4.2.3.Final, 4.3.0.Final > Environment: RichFaces 4.3.1-SNAPSHOT > Metamer 4.3.1-SNAPSHOT > Mojarra 2.1.18 > JBoss AS 7.2.0.Alpha1-SNAPSHOT, Tomcat 7.0.32 > OpenJDK Runtime Environment 1.7.0_09-icedtea-mockbuild_2013_02_07_23_07-b00 @ Linux > Chrome 24.0.1312.69 @ Linux x86_64 > Reporter: Pavol Pitonak > Priority: Critical > Attachments: brokenresources.zip, edt.png > > > # download JBoss AS 7.2.0.Alpha1-SNAPSHOT from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/artifact/build/target/jboss-as-7.x.zip > # deploy Metamer to the JBoss AS > # open http://localhost:8080/metamer/faces/components/richExtendedDataTable/frozenColumns.xhtml > # set parameter frozenColumns to 2 > result: > * EDT is totally broken, there are JS errors in browser console > * EDT and dataScroller resources (ecss and js) disappear from the page after postback request > * example works fine when I remove attribute binding from the xhtml > * worked fine with JBoss AS 7.1.1 (Mojarra 2.1.7) > * it's not a JBoss AS bug, I can reproduce also on Tomcat with Mojarra 2.1.18 > * works fine with Mojarra 2.1.17 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 15 09:44:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 15 Apr 2014 09:44:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-11736. -------------------------------- Resolution: Done I've made the panel show before the sizing is determined so the sizes are obtained from the now-visible header. This shouldn't affect other things. > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Assignee: Michal Petrov > Fix For: 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 15 11:32:34 2014 From: issues at jboss.org (Christoph W. (JIRA)) Date: Tue, 15 Apr 2014 11:32:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12962077#comment-12962077 ] Christoph W. commented on RF-11736: ----------------------------------- When will the fix be backported to 4.3.x? > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Assignee: Michal Petrov > Fix For: 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 03:14:34 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 16 Apr 2014 03:14:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12962184#comment-12962184 ] Pavol Pitonak commented on RF-11736: ------------------------------------ [~jstefek], please verify the fix. [~christoph_w], yes, we will verify it in 5.x and then it should be backported to 4.3. > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Assignee: Michal Petrov > Fix For: 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 03:44:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 16 Apr 2014 03:44:33 -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:all-tabpanel ] Michal Petrov reassigned RF-13582: ---------------------------------- Assignee: Michal Petrov > 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 > Fix For: 4.5.0.Alpha3 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 03:46:33 2014 From: issues at jboss.org (Michael Colin (JIRA)) Date: Wed, 16 Apr 2014 03:46:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13607) Tables/Menus logged warnings for invalid children In-Reply-To: References: Message-ID: Michael Colin created RF-13607: ---------------------------------- Summary: 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 09:02:35 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Wed, 16 Apr 2014 09:02:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12962270#comment-12962270 ] Ji?? ?tefek commented on RF-11736: ---------------------------------- Verified. It is working with RF 5.x. Ready to close. ---- Just one thing, what should be the behaviour of popupPanel when @top=auto and @left=auto (default attributes values)? Should not it be centered to view similarly like the `center` function here in the workaround? I have not found it in documentation (VDL, Component reference). > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Assignee: Michal Petrov > Fix For: 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 09:30:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 16 Apr 2014 09:30:34 -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=12962278#comment-12962278 ] Michal Petrov commented on RF-13582: ------------------------------------ I've compared the framework with richfaces4/core and put back the classes I could. There are a few classes missing - former {{org.richfaces.webapp}} package is missing entirely, {{org.richfaces.resource}} classes were renamed/refactored. Some classes that were deprecated in 4.3.x were removed in 5. > 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 > Fix For: 4.5.0.Alpha3 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 10:12:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 16 Apr 2014 10:12:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12962290#comment-12962290 ] Michal Petrov commented on RF-11736: ------------------------------------ It depends on @followByScroll - if set to true (default) it centers on view, otherwise it's centered from the top of the page. That attribute is undefined in the Metamer example. > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Assignee: Michal Petrov > Fix For: 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 10:14:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 16 Apr 2014 10:14:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov updated RF-11736: ------------------------------- Fix Version/s: 4.3.7 > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Assignee: Michal Petrov > Fix For: 4.3.7, 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 17:50:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 16 Apr 2014 17:50:34 -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: Brian Leathem created RF-13608: ---------------------------------- Summary: 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 The current package {{org.richfaces.compat}} is inappropriate for the RichFaces 4.5 release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 17:52:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 16 Apr 2014 17:52:33 -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 ] Brian Leathem updated RF-13608: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > 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 > Fix For: 4.5.0.Alpha3 > > > The current package {{org.richfaces.compat}} is inappropriate for the RichFaces 4.5 release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 17:52:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 16 Apr 2014 17:52:33 -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 ] Brian Leathem updated RF-13608: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 1 > 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 > Fix For: 4.5.0.Alpha3 > > > The current package {{org.richfaces.compat}} is inappropriate for the RichFaces 4.5 release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 18:04:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 16 Apr 2014 18:04:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13609) Showcase doesn't build In-Reply-To: References: Message-ID: Brian Leathem created RF-13609: ---------------------------------- Summary: Showcase doesn't build Key: RF-13609 URL: https://issues.jboss.org/browse/RF-13609 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.5.0.Alpha3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 18:10:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 16 Apr 2014 18:10:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13609) Showcase doesn't build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12962394#comment-12962394 ] Brian Leathem commented on RF-13609: ------------------------------------ Additionally there are deploy time errors: {code} java.lang.ClassNotFoundException: org.richfaces.skin.SkinningExternalContextFactory {code} > Showcase doesn't build > ---------------------- > > Key: RF-13609 > URL: https://issues.jboss.org/browse/RF-13609 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > There are compile time errors related to broken import statements -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 18:10:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 16 Apr 2014 18:10:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13609) Showcase doesn't build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13609: ------------------------------- Description: There are compile time errors related to broken import statements > Showcase doesn't build > ---------------------- > > Key: RF-13609 > URL: https://issues.jboss.org/browse/RF-13609 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > There are compile time errors related to broken import statements -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 18:46:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 16 Apr 2014 18:46:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13609) Showcase doesn't build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12962401#comment-12962401 ] Brian Leathem commented on RF-13609: ------------------------------------ After resolving the deploy time errors, there are runtime errors. eg: {code} 15:44:26,792 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-/0.0.0.0:8080-1) Error Rendering View[/index.xhtml]: java.lang.IllegalStateException: Failed to obtain service MappedResourceFactory at org.richfaces.application.ServiceTracker$1.invoke(ServiceTracker.java:151) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at com.sun.proxy.$Proxy96.createResource(Unknown Source) at org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:266) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at com.sun.faces.renderkit.html_basic.StylesheetRenderer.encodeEnd(StylesheetRenderer.java:97) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [classes:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:832) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:620) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:553) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:482) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:689) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:663) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.jsp.index_jsp._jspService(index_jsp.java:60) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:365) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:309) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:242) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] {code} > Showcase doesn't build > ---------------------- > > Key: RF-13609 > URL: https://issues.jboss.org/browse/RF-13609 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > There are compile time errors related to broken import statements -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 19:20:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 16 Apr 2014 19:20:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13610) Resource loading error in the showcase In-Reply-To: References: Message-ID: Brian Leathem created RF-13610: ---------------------------------- Summary: Resource loading error in the showcase Key: RF-13610 URL: https://issues.jboss.org/browse/RF-13610 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: resource handling, showcase Reporter: Brian Leathem Fix For: 4.5.0.Alpha3 Getting the runtime error: {code} 15:44:26,792 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-/0.0.0.0:8080-1) Error Rendering View[/index.xhtml]: java.lang.IllegalStateException: Failed to obtain service MappedResourceFactory at org.richfaces.application.ServiceTracker$1.invoke(ServiceTracker.java:151) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at com.sun.proxy.$Proxy96.createResource(Unknown Source) at org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:266) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] at com.sun.faces.renderkit.html_basic.StylesheetRenderer.encodeEnd(StylesheetRenderer.java:97) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [classes:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:832) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:620) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:553) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:482) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:689) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:663) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.jsp.index_jsp._jspService(index_jsp.java:60) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:365) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:309) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:242) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 19:20:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 16 Apr 2014 19:20:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13609) Showcase doesn't build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13609. -------------------------------- Resolution: Done > Showcase doesn't build > ---------------------- > > Key: RF-13609 > URL: https://issues.jboss.org/browse/RF-13609 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > There are compile time errors related to broken import statements -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 16 19:20:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 16 Apr 2014 19:20:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13609) Showcase doesn't build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12962406#comment-12962406 ] Brian Leathem commented on RF-13609: ------------------------------------ I believe the runtime error is caused by missing resources. I created RF-13610 to track the issue. > Showcase doesn't build > ---------------------- > > Key: RF-13609 > URL: https://issues.jboss.org/browse/RF-13609 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > There are compile time errors related to broken import statements -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 17 03:56:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Thu, 17 Apr 2014 03:56:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11359) using component control in rich:dataTable and rich:extendedDataTable doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-11359. ---------------------------- Labels: (was: ci_issue) Fix Version/s: (was: 5-Future) Resolution: Out of Date I can not reproduce the issue anymore with RF 4.5.0-SNAPSHOT or other versions. > using component control in rich:dataTable and rich:extendedDataTable doesn't work > --------------------------------------------------------------------------------- > > Key: RF-11359 > URL: https://issues.jboss.org/browse/RF-11359 > Project: RichFaces > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.0.M1 > Environment: RichFaces 4.3.0-SNAPSHOT > Metamer 4.3.0-SNAPSHOT > Mojarra 2.1.7-redhat-1 > JBoss AS 7.1.2.Final-redhat-1 > Java(TM) SE Runtime Environment 1.6.0_32-b05 @ Linux > Chrome 21.0.1180.81 @ Linux x86_64 > Reporter: Pavol Pitonak > > Problem with jQuery 1.6.2: sorting using component control in rich:dataTable and rich:extendedDataTable doesn't work, can be reproduced in Metamer on page http://localhost:8080/metamer/faces/components/richDataTable/sorting-using-component-control.xhtml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 17 04:34:34 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 17 Apr 2014 04:34:34 -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=12962458#comment-12962458 ] Ji?? ?tefek commented on RF-12132: ---------------------------------- I can confirm this bug. Used: last RF5 snapshots; GlassFish 3.1.2.2 , Tomcat 7.0.53 with Mojarra and MyFaces; FF 22, Chrome 34. Added reproducer to Metamer. I can also confirm that the problem is not intermittent. The queue behaves the same as in the description here = no further ajax requests after error in @oncomplete. > 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 > Environment: Myfaces 2.1.6 > Tomcat 6.0.35 > Reporter: Michael Heinen > Assignee: Ji?? ?tefek > Labels: needs-qe > Fix For: 5-Tracking > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 17 04:34:34 2014 From: issues at jboss.org (=?UTF-8?Q?Ji=C5=99=C3=AD_=C5=A0tefek_=28JIRA=29?=) Date: Thu, 17 Apr 2014 04:34:34 -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 updated RF-12132: ----------------------------- Labels: (was: needs-qe) > 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 > Environment: Myfaces 2.1.6 > Tomcat 6.0.35 > Reporter: Michael Heinen > Assignee: Ji?? ?tefek > Fix For: 5-Tracking > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 17 08:24:34 2014 From: issues at jboss.org (Juergen Zimmermann (JIRA)) Date: Thu, 17 Apr 2014 08:24:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13611) RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final In-Reply-To: References: Message-ID: Juergen Zimmermann created RF-13611: --------------------------------------- Summary: RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final Key: RF-13611 URL: https://issues.jboss.org/browse/RF-13611 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 5.0.0.Alpha3 Reporter: Juergen Zimmermann I'm using WildFly 8.0.0.CR1 and Weld 2.2.0.Final (via the WildFly patch mechanism). However, I'm getting the stacktrace below. When I patch WildFly 8.0.0.CR1 with the predecessor version Weld 2.2.0.CR2, then the issue is gone. {code} ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.deployment.unit."shop.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."shop.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:1142) [rt.jar:1.8.0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: Exception 0 : org.jboss.weld.exceptions.DefinitionException: WELD-000412: ObserverMethod.getReception() returned null for org.richfaces.push.cdi.PushCDIExtension$PushObserverMethod at 31e23242 at org.jboss.weld.util.Observers.validateObserverMethod(Observers.java:118) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:158) at org.richfaces.push.cdi.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:90) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:271) at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:258) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:237) at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:174) at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:133) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:107) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59) at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44) at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59) at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) 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} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 17 08:32:33 2014 From: issues at jboss.org (Jozef Hartinger (JIRA)) Date: Thu, 17 Apr 2014 08:32:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13611) RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12962518#comment-12962518 ] Jozef Hartinger commented on RF-13611: -------------------------------------- The method should not be returning null. > RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final > --------------------------------------------------------- > > Key: RF-13611 > URL: https://issues.jboss.org/browse/RF-13611 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > > I'm using WildFly 8.0.0.CR1 and Weld 2.2.0.Final (via the WildFly patch mechanism). However, I'm getting the stacktrace below. When I patch WildFly 8.0.0.CR1 with the predecessor version Weld 2.2.0.CR2, then the issue is gone. > {code} > ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.deployment.unit."shop.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."shop.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:1142) [rt.jar:1.8.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > org.jboss.weld.exceptions.DefinitionException: WELD-000412: ObserverMethod.getReception() returned null for org.richfaces.push.cdi.PushCDIExtension$PushObserverMethod at 31e23242 > at org.jboss.weld.util.Observers.validateObserverMethod(Observers.java:118) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:158) > at org.richfaces.push.cdi.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:90) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:271) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:258) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:237) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:174) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:133) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:107) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > 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:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > 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} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Apr 20 19:44:33 2014 From: issues at jboss.org (Walter Maidub (JIRA)) Date: Sun, 20 Apr 2014 19:44:33 -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:comment-tabpanel&focusedCommentId=12962836#comment-12962836 ] Walter Maidub commented on RF-13602: ------------------------------------ It doesn't work. We download richfaces 3.5.6 and the behavior its the same, the web application have problem with rendering ajax component. Do you need any logs? > 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 > Labels: ie11, waiting_on_user > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 06:52:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 22 Apr 2014 06:52:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13612) Document styling attributes for rich:dataTable In-Reply-To: References: Message-ID: Michal Petrov created RF-13612: ---------------------------------- Summary: Document styling attributes for rich:dataTable Key: RF-13612 URL: https://issues.jboss.org/browse/RF-13612 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 4.3.6 Reporter: Michal Petrov There are several attributes that can be assigned to a dataTable such as {{headerCellClass}} or {{firstColumnFooterClass}} (see [AbstractTableRenderer|https://github.com/richfaces4/components/blob/master/iteration/ui/src/main/java/org/richfaces/renderkit/AbstractTableRenderer.java#L325]). The renderer is set to process them but they are not documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:14:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:14:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963074#comment-12963074 ] Brian Leathem commented on RF-13592: ------------------------------------ Sounds like an issue with a stale node reference. > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Priority: Critical > Labels: gss > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:22:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:22:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent" In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963079#comment-12963079 ] Brian Leathem commented on RF-11736: ------------------------------------ Nice work [~michpetrov] and QE team! > rich:popupPanel x domElementAttachment="parent" > ----------------------------------------------- > > Key: RF-11736 > URL: https://issues.jboss.org/browse/RF-11736 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final > Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3 > Reporter: Edilmar Alves > Assignee: Michal Petrov > Fix For: 4.3.7, 5-Tracking > > > rich:popupPanel repositions after second click when we use domElementAttachment="parent" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:24:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:24:34 -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 ] Brian Leathem updated RF-12132: ------------------------------- Assignee: (was: Ji?? ?tefek) > 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 > Environment: Myfaces 2.1.6 > Tomcat 6.0.35 > Reporter: Michael Heinen > Fix For: 5-Tracking > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:28:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:28:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13568) IllegalArgumentException for PushResource.jsf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13568: ---------------------------------- Assignee: Pavol Pitonak QE please co-ordinate with [~juergen.zimmermann] to re-produce this issue, otherwise resolve it as out-of-date. > IllegalArgumentException for PushResource.jsf > --------------------------------------------- > > Key: RF-13568 > URL: https://issues.jboss.org/browse/RF-13568 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha3 > Environment: WildFly snapshot with Undertow 1.0.1 > Reporter: Juergen Zimmermann > Assignee: Pavol Pitonak > > Im using the latest WildFly snapshot containing Undertow 1.0.1. I'm getting tons of stacktraces like the following: > {code} > [io.undertow.request] UT005023: Exception handling request to /shop/rfRes/org.richfaces.ui.ajax.push.PushResource.jsf: java.lang.IllegalArgumentException: pushTopic request parameter must be present > at org.richfaces.ui.ajax.push.PushResource.encode(PushResource.java:87) [richfaces-5.0.0.Alpha3.jar:5.0.0.Alpha3] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-5.0.0.Alpha3.jar:5.0.0.Alpha3] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) [richfaces-5.0.0.Alpha3.jar:5.0.0.Alpha3] > 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.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.1.Final.jar:1.0.1.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.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.1.Final.jar:1.0.1.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.1.Final.jar:1.0.1.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:30:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:30:34 -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=12963083#comment-12963083 ] Brian Leathem commented on RF-13582: ------------------------------------ Thanks for making progress with this issue [~michpetrov]. To identify any further breakages we should: 1) Build/deploy/run an unmodified richfaces showcase from 4.3.x against RF 4.5 jars (with necessary pom changes) 2) Ask QE to do the same for metamer If both the above samples/tests run without error then we are in a good position w.r.t. backwards compatibility. > 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 > Fix For: 4.5.0.Alpha3 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:34:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:34:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13595) rich:validator doesn't work when loaded via ajax (re-render) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13595: ---------------------------------- Assignee: (was: Matej Novotny) Thanks [~manovotn]! > rich:validator doesn't work when loaded via ajax (re-render) > ------------------------------------------------------------ > > Key: RF-13595 > URL: https://issues.jboss.org/browse/RF-13595 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.5 > Environment: RF 4.3.5 > Mojarra 2.1.27 > Java 7 Update 51 x64 > Tomcat 7.0.52 > Firefox 28.0 + Firebug > Reporter: Michael B > Fix For: 4.5-Tracking > > Attachments: validationTest.zip > > > When loading input components with a rich:validator via ajax (re-render), client side validation bridge breaks due to a missing JS function av_xxxxxxxxx. > As already described in further detail in a comment to this JIRA here: > https://issues.jboss.org/browse/RF-12031 > I've created a very basic example project to reproduce the problem for a single input field which becomes visible (re-rendered) when you click on an a4j:commandButton. > Please note that this is a minimum example only. The problem is also reproducable for other input components besides h:inputText - like for example rich:calendar. > The workaround described in the referenced JIRA creates other problems in client JS when combined with other components like rich:focus and is also not applicable for other input components besides h:inputText. > We think the problem is located in the way JS functions are optimized for being re-used as well as in the way they are (not) being added on the client side when a component becomes visible on ajax response re-rendering. > Please use attached eclipse project to easily reproduce the problem => open Firefox => Firebug console to see the error about the missing JS function av_xxxxxxx ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:34:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:34:34 -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:comment-tabpanel&focusedCommentId=12963085#comment-12963085 ] Brian Leathem commented on RF-13602: ------------------------------------ {quote} We download richfaces 3.5.6 {quote} Can you clarify? > 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 > Labels: ie11, waiting_on_user > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:34:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:34:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13603: ------------------------------- Fix Version/s: 5-Tracking > unsupported classversion 51.0 while deploying ear > ------------------------------------------------- > > Key: RF-13603 > URL: https://issues.jboss.org/browse/RF-13603 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Environment: Windows 7, Weblogic 10.3.5, JDK 6 > Reporter: Nestor Armando Bohorquez > Assignee: Matej Novotny > Labels: ResourceServlet, classversion > Fix For: 5-Tracking > > > An exception is thrown when applicattion is been deployed: > {code} > java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) > at java.lang.ClassLoader.defineClass(ClassLoader.java:614) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) > at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) > at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) > at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) > at java.lang.ClassLoader.loadClass(ClassLoader.java:305) > at java.lang.ClassLoader.loadClass(ClassLoader.java:246) > at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) > at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) > at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) > at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) > at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) > at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) > at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) > at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) > at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) > at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) > at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) > at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) > at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) > at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) > at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) > at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) > at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) > {code} > I'm using this in the web.xml file. > {code} > > Resource Servlet > org.richfaces.servlet.ResourceServlet > 1 > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:36:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:36:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13603) unsupported classversion 51.0 while deploying ear In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13603: ------------------------------- Workaround Description: Build with JDK 7 > unsupported classversion 51.0 while deploying ear > ------------------------------------------------- > > Key: RF-13603 > URL: https://issues.jboss.org/browse/RF-13603 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha3 > Environment: Windows 7, Weblogic 10.3.5, JDK 6 > Reporter: Nestor Armando Bohorquez > Assignee: Matej Novotny > Labels: ResourceServlet, classversion > Fix For: 5-Tracking > > > An exception is thrown when applicattion is been deployed: > {code} > java.lang.UnsupportedClassVersionError: org/richfaces/servlet/ResourceServlet : unsupported classversion 51.0 > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClassCond(ClassLoader.java:630) > at java.lang.ClassLoader.defineClass(ClassLoader.java:614) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) > at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343) > at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302) > at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270) > at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64) > at java.lang.ClassLoader.loadClass(ClassLoader.java:305) > at java.lang.ClassLoader.loadClass(ClassLoader.java:246) > at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179) > at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:43) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:225) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:209) > at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:105) > at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1368) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:449) > at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:493) > at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418) > at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:972) > at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:382) > at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) > at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) > at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) > at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) > at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613) > at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) > at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184) > at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58) > at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) > at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207) > at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98) > at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) > at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) > at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) > at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) > at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) > at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) > at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) > {code} > I'm using this in the web.xml file. > {code} > > Resource Servlet > org.richfaces.servlet.ResourceServlet > 1 > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:36:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:36:34 -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: ------------------------------- Steps to Reproduce: 1. In Eclipse, create new Dynamic Web Project: select "GlassFish 4.0" as the target runtime, select 3.1 as Dynamic web module version, Default Configuration for GlassFish 4.0 as Configuration 2. Navigate to directory WebContent/WEB-INF/lib and put the following files there - cssparser-0.9.9.jar - guava-r09.jar - richfaces-components-api-4.3.5.Final.jav - richfaces-components-ui-4.3.5.Final.jar - richfaces-core-api-4.3.5.Final.jar - richfaces-core-impl-4.3.5.Final.jar - sac-1.3.jar 3. Right-click on the project in Eclipse, click Properties, then go to Project Facets and enable checkbox to the left of Java Server Faces (ensure that version is 2.2). Ensure that also the following checkboxes are enabled: - Dynamic Web Module, version 3.1 - Java, version 1.7 - JavaScript, version 1.0 Click "Apply" button, then click "OK" button. 4. Under WebContent directory, create new XHTML file called test.xhtml with the following content: {code} Output from Editor (Updating) {code} 5. Under Java Resources directory src, create file EditorBean.java with the following content: {code} import javax.faces.bean.ManagedBean; import javax.faces.bean.SessionScoped; @ManagedBean(name="editorBean") @SessionScoped() public class EditorBean { private String value = ""; public String getValue() { return value; } public void setValue(String value) { this.value = value; } } {code} 6. Right-click on test.xhtml, select "Debug As"->"Debug on Server", of the servers select GlassFish 4.0 and click button "Finish". 7. Navigate to the /faces/test.xhtml in Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659). 8. Hover the mouse over the toolbar of the editor. Note that the buttons of the editor start to move in unreasonable way (Internet Explorer) or tooltips of the buttons start to flicker (Chrome). was: 1. In Eclipse, create new Dynamic Web Project: select "GlassFish 4.0" as the target runtime, select 3.1 as Dynamic web module version, Default Configuration for GlassFish 4.0 as Configuration 2. Navigate to directory WebContent/WEB-INF/lib and put the following files there - cssparser-0.9.9.jar - guava-r09.jar - richfaces-components-api-4.3.5.Final.jav - richfaces-components-ui-4.3.5.Final.jar - richfaces-core-api-4.3.5.Final.jar - richfaces-core-impl-4.3.5.Final.jar - sac-1.3.jar 3. Right-click on the project in Eclipse, click Properties, then go to Project Facets and enable checkbox to the left of Java Server Faces (ensure that version is 2.2). Ensure that also the following checkboxes are enabled: - Dynamic Web Module, version 3.1 - Java, version 1.7 - JavaScript, version 1.0 Click "Apply" button, then click "OK" button. 4. Under WebContent directory, create new XHTML file called test.xhtml with the following content: Output from Editor (Updating) 5. Under Java Resources directory src, create file EditorBean.java with the following content: import javax.faces.bean.ManagedBean; import javax.faces.bean.SessionScoped; @ManagedBean(name="editorBean") @SessionScoped() public class EditorBean { private String value = ""; public String getValue() { return value; } public void setValue(String value) { this.value = value; } } 6. Right-click on test.xhtml, select "Debug As"->"Debug on Server", of the servers select GlassFish 4.0 and click button "Finish". 7. Navigate to the /faces/test.xhtml in Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659). 8. Hover the mouse over the toolbar of the editor. Note that the buttons of the editor start to move in unreasonable way (Internet Explorer) or tooltips of the buttons start to flicker (Chrome). > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:36:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:36:34 -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 reassigned RF-13604: ---------------------------------- Assignee: Pavol Pitonak QE, please verify > 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 > Assignee: Pavol Pitonak > Labels: editor, glassfish, jsf22 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:42:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:42:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13605: ------------------------------- Description: Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. {code} {code} was: Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. > a4j:ajax button click event gets lost > ------------------------------------- > > Key: RF-13605 > URL: https://issues.jboss.org/browse/RF-13605 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.6 > Reporter: abhishek vijra > Attachments: queue.zip > > > Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. > Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. > {code} > > rendered="#{not empty richBean.name}" style="font-size:2em" /> > > > > cellspacing="10"> > > > render="@form" /> > > > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:42:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:42:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13605: ------------------------------- Description: Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. {code} {code} was: Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. {code} {code} > a4j:ajax button click event gets lost > ------------------------------------- > > Key: RF-13605 > URL: https://issues.jboss.org/browse/RF-13605 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.6 > Reporter: abhishek vijra > Attachments: queue.zip > > > Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. > Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. > {code} > > > > > > > > > > > > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:42:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:42:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13605: ------------------------------- Description: Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. {code} {code} was: Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. {code} {code} > a4j:ajax button click event gets lost > ------------------------------------- > > Key: RF-13605 > URL: https://issues.jboss.org/browse/RF-13605 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.6 > Reporter: abhishek vijra > Attachments: queue.zip > > > Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. > Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. > {code} > > > > > > > > > > > > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:48:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:48:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963088#comment-12963088 ] Brian Leathem commented on RF-13605: ------------------------------------ Indeed, as [~michpetrov] pointed out the problem here is one of competing nearly-simultaneous ajax requests. The user should consider which even should trigger the ajax update, and should consider moving the ajax _change_ listener on the input text into a _valueChangeListener_ property of the inputText. This way the change listener would get executed when the ajax update initiated by the button was processed. See: https://javaserverfaces.java.net/nonav/docs/2.1/vdldocs/facelets/h/inputText.html > a4j:ajax button click event gets lost > ------------------------------------- > > Key: RF-13605 > URL: https://issues.jboss.org/browse/RF-13605 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.6 > Reporter: abhishek vijra > Attachments: queue.zip > > > Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. > Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. > {code} > > > > > > > > > > > > > > > > > > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:48:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:48:34 -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:all-tabpanel ] Brian Leathem updated RF-13606: ------------------------------- Description: 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} was: Application started successfully, but throws exception when launched: 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) > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:50:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:50:33 -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:all-tabpanel ] Brian Leathem resolved RF-13606. -------------------------------- Resolution: Incomplete Description Sorry, but a stacktrace on it's own does not constitute an issue report. Feel free to re-open the issue with a sample application attached that deploys fine in other containers, but fails in your preferred container. > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:52:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:52:33 -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:comment-tabpanel&focusedCommentId=12963091#comment-12963091 ] Brian Leathem commented on RF-13607: ------------------------------------ Please provide an example of sample code that you would expect to throw an error. > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:54:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:54:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13611) RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963092#comment-12963092 ] Brian Leathem commented on RF-13611: ------------------------------------ The method that returns null: https://github.com/richfaces/richfaces/blob/master/framework/src/main/java/org/richfaces/push/cdi/PushCDIExtension.java#L162 {code} public Reception getReception() { return null; } {code} > RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final > --------------------------------------------------------- > > Key: RF-13611 > URL: https://issues.jboss.org/browse/RF-13611 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > > I'm using WildFly 8.0.0.CR1 and Weld 2.2.0.Final (via the WildFly patch mechanism). However, I'm getting the stacktrace below. When I patch WildFly 8.0.0.CR1 with the predecessor version Weld 2.2.0.CR2, then the issue is gone. > {code} > ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.deployment.unit."shop.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."shop.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:1142) [rt.jar:1.8.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > org.jboss.weld.exceptions.DefinitionException: WELD-000412: ObserverMethod.getReception() returned null for org.richfaces.push.cdi.PushCDIExtension$PushObserverMethod at 31e23242 > at org.jboss.weld.util.Observers.validateObserverMethod(Observers.java:118) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:158) > at org.richfaces.push.cdi.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:90) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:271) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:258) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:237) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:174) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:133) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:107) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > 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:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > 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} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:54:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:54:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13611) RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13611: ------------------------------- Fix Version/s: 4.3.7 > RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final > --------------------------------------------------------- > > Key: RF-13611 > URL: https://issues.jboss.org/browse/RF-13611 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > Fix For: 4.3.7 > > > I'm using WildFly 8.0.0.CR1 and Weld 2.2.0.Final (via the WildFly patch mechanism). However, I'm getting the stacktrace below. When I patch WildFly 8.0.0.CR1 with the predecessor version Weld 2.2.0.CR2, then the issue is gone. > {code} > ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.deployment.unit."shop.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."shop.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:1142) [rt.jar:1.8.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > org.jboss.weld.exceptions.DefinitionException: WELD-000412: ObserverMethod.getReception() returned null for org.richfaces.push.cdi.PushCDIExtension$PushObserverMethod at 31e23242 > at org.jboss.weld.util.Observers.validateObserverMethod(Observers.java:118) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:158) > at org.richfaces.push.cdi.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:90) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:271) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:258) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:237) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:174) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:133) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:107) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > 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:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > 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} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:54:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:54:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13612) Document styling attributes for rich:dataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13612: ------------------------------- Component/s: doc > Document styling attributes for rich:dataTable > ---------------------------------------------- > > Key: RF-13612 > URL: https://issues.jboss.org/browse/RF-13612 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.6 > Reporter: Michal Petrov > > There are several attributes that can be assigned to a dataTable such as {{headerCellClass}} or {{firstColumnFooterClass}} (see [AbstractTableRenderer|https://github.com/richfaces4/components/blob/master/iteration/ui/src/main/java/org/richfaces/renderkit/AbstractTableRenderer.java#L325]). The renderer is set to process them but they are not documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:54:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:54:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13612) Document styling attributes for rich:dataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13612: ------------------------------- Component/s: component-tables > Document styling attributes for rich:dataTable > ---------------------------------------------- > > Key: RF-13612 > URL: https://issues.jboss.org/browse/RF-13612 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables, doc > Affects Versions: 4.3.6 > Reporter: Michal Petrov > > There are several attributes that can be assigned to a dataTable such as {{headerCellClass}} or {{firstColumnFooterClass}} (see [AbstractTableRenderer|https://github.com/richfaces4/components/blob/master/iteration/ui/src/main/java/org/richfaces/renderkit/AbstractTableRenderer.java#L325]). The renderer is set to process them but they are not documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:56:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:56:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13612) Document styling attributes for rich:dataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13612: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Document styling attributes for rich:dataTable > ---------------------------------------------- > > Key: RF-13612 > URL: https://issues.jboss.org/browse/RF-13612 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables, doc > Affects Versions: 4.3.6 > Reporter: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > There are several attributes that can be assigned to a dataTable such as {{headerCellClass}} or {{firstColumnFooterClass}} (see [AbstractTableRenderer|https://github.com/richfaces4/components/blob/master/iteration/ui/src/main/java/org/richfaces/renderkit/AbstractTableRenderer.java#L325]). The renderer is set to process them but they are not documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 12:58:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 12:58:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11417) Tab: investigate why @action does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963094#comment-12963094 ] Brian Leathem commented on RF-11417: ------------------------------------ My apologies [~Trims] for the delayed follow-up, I was busy preparing-for/attending the DevNation conference recently. [~ppitonak] please verify the update Pull request. > Tab: investigate why @action does not work > ------------------------------------------ > > Key: RF-11417 > URL: https://issues.jboss.org/browse/RF-11417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Fix For: 5-Tracking > > > Determine why rich:tab @action has not been implemented. > Verify that its implementation can't affect current applications (and try to find possible workaround). > Implement @action and @actionListener. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 17:20:33 2014 From: issues at jboss.org (Walter Maidub (JIRA)) Date: Tue, 22 Apr 2014 17:20:33 -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:comment-tabpanel&focusedCommentId=12963135#comment-12963135 ] Walter Maidub commented on RF-13602: ------------------------------------ Sorry, We download Richfaces 4.3.6.Final.zip Regards > 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 > Labels: ie11, waiting_on_user > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 17:42:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 17:42:33 -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 reassigned RF-13602: ---------------------------------- Assignee: Pavol Pitonak QE, please verify > 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: Pavol Pitonak > Labels: ie11, waiting_on_user > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 22 17:42:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 22 Apr 2014 17:42:33 -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 updated RF-13602: ------------------------------- Labels: ie11 (was: ie11 waiting_on_user) > 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: Pavol Pitonak > Labels: ie11 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 23 14:09:33 2014 From: issues at jboss.org (Edilmar Alves (JIRA)) Date: Wed, 23 Apr 2014 14:09:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13369) autocomplete problem in glassfish 4 with jsf 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963365#comment-12963365 ] Edilmar Alves commented on RF-13369: ------------------------------------ I have the same problem with rich:autocomplete in GF4 + JSF2.2 + RF4.3.5. > autocomplete problem in glassfish 4 with jsf 2.2 > ------------------------------------------------ > > Key: RF-13369 > URL: https://issues.jboss.org/browse/RF-13369 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: glassfish4 with JSF2.2, ubunto 12.04 > Reporter: Joao Granado > Assignee: Luk?? Fry? > Labels: jsf22 > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > autocomplete: the pop-up list always appears empty -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 23 14:31:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 23 Apr 2014 14:31:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13369) autocomplete problem in glassfish 4 with jsf 2.2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963369#comment-12963369 ] Brian Leathem commented on RF-13369: ------------------------------------ This issue has been resolved in RF 5. It is expected to be resolved in RF 4.3 with the backport of the fix tracked by RF-13507. > autocomplete problem in glassfish 4 with jsf 2.2 > ------------------------------------------------ > > Key: RF-13369 > URL: https://issues.jboss.org/browse/RF-13369 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4 > Environment: glassfish4 with JSF2.2, ubunto 12.04 > Reporter: Joao Granado > Assignee: Luk?? Fry? > Labels: jsf22 > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > autocomplete: the pop-up list always appears empty -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 23 22:41:33 2014 From: issues at jboss.org (Walter Maidub (JIRA)) Date: Wed, 23 Apr 2014 22:41:33 -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:comment-tabpanel&focusedCommentId=12963419#comment-12963419 ] Walter Maidub commented on RF-13602: ------------------------------------ sorry, QE? > 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: Pavol Pitonak > Labels: ie11 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:29:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:29:34 -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 ] Brian Leathem updated RF-13514: ------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:29:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:29:34 -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:all-tabpanel ] Brian Leathem updated RF-13582: ------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > 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 > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:29:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:29:34 -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: ------------------------------- Original Estimate: 4 days Remaining Estimate: 4 days > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:29:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:29:34 -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:all-tabpanel ] Brian Leathem updated RF-13582: ------------------------------- Original Estimate: 3 hours (was: 1 day) Remaining Estimate: 3 hours (was: 1 day) > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:29:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:29:34 -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 ] Brian Leathem updated RF-13591: ------------------------------- Summary: RichFaces 4.5 integration tests are failing (was: RichFaces 4.5 not compilable because of integration tests) > 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 > Priority: Blocker > Fix For: 4.5.0.Alpha3 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:29:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:29:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13584) Backport the RF 5 component fixes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13584: ------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > Backport the RF 5 component fixes > --------------------------------- > > Key: RF-13584 > URL: https://issues.jboss.org/browse/RF-13584 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Some fixes were applied to the RichFaces 5 components that should be backported to RF 4.5. These include (but are not limited to) the fixes labelled "45x": > https://issues.jboss.org/browse/RF-13520?jql=project%3DRF%20and%20labels%20%3D%2045x -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:31:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:31:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13406) Create a new showcase for RichFaces 5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13406: ------------------------------- Original Estimate: 2 days (was: 1 day) Remaining Estimate: 2 days (was: 1 day) > Create a new showcase for RichFaces 5 > ------------------------------------- > > Key: RF-13406 > URL: https://issues.jboss.org/browse/RF-13406 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Fix For: 5.0.0.Alpha4 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The new showcase should: > # Include the examples from the existing RichFaces4 showcase > #* Simplications should be made as appropriate to reduce complexity (eg. no JMS, no JPA - these can be addressed in standalone examples) > # Be based on the RichFaces Sandbox Bootstrap demo > #* The layout will have to be changed to use generic bootstrap CSS as required > # Drop (as much as possible) the container specific configuration found in the RichFaces4 showcase > #* consider any sample simplifications required to achieve this goal -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:31:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:31:33 -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 ] Brian Leathem updated RF-13608: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:31:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:31:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13586) Port the page fragments to RF 4.5 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13586: ------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > Port the page fragments to RF 4.5 > --------------------------------- > > Key: RF-13586 > URL: https://issues.jboss.org/browse/RF-13586 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:31:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:31:33 -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 ] Brian Leathem updated RF-13591: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:31:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:31:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13587) rich:autocomplete - suggestion box doesn't show up at all In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13587: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > rich:autocomplete - suggestion box doesn't show up at all > --------------------------------------------------------- > > Key: RF-13587 > URL: https://issues.jboss.org/browse/RF-13587 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Implementation: JSF-2.2.6 mojarra, Mojarra 2.2.5 > Server: WebLogic 12.1.2.1, WildFly 8.0.0.Final > Browser: Chrome 33, Firefox 27 > Java: 1.7 > Reporter: Amit Tikoo > Labels: richfaces > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I am using a component but the suggestion box just doesn't show up. Here is a simple case I'm trying: > XHTML: > {code} > > > > #{station} > > > > {code} > JAVA: > {code} > public List autocomplete1(String request){ > List suggestions = new ArrayList(); > suggestions.add("test 1"); > suggestions.add("test 2"); > suggestions.add("test 3"); > suggestions.add("test 4"); > return suggestions; > } > {code} > This shows up in logging (using ) > {code} > error[14:47:03.644]: Received 'error at malformedXML' event from > error[14:47:03.644]: [status=200] During update: javax.faces.ViewState not found > {code} > Also i can see the suggestion if i switch the mode to "Client" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:33:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:33:33 -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 ] Brian Leathem updated RF-13160: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 1, 4.5.0.Alpha3 - Sprint 1 (was: 5.0.0.Alpha2 - Sprint 1) > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:33:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:33:33 -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 1 > 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 > > > Drag/Drop support should be added to file upload component . > Like the primefaces fileUploadDnd : http://www.primefaces.org/showcase/ui/fileUploadDnd.jsf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:33:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:33:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13610) Resource loading error in the showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13610: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 2 > Resource loading error in the showcase > -------------------------------------- > > Key: RF-13610 > URL: https://issues.jboss.org/browse/RF-13610 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling, showcase > Reporter: Brian Leathem > Fix For: 4.5.0.Alpha3 > > > Getting the runtime error: > {code} > 15:44:26,792 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-/0.0.0.0:8080-1) Error Rendering View[/index.xhtml]: java.lang.IllegalStateException: Failed to obtain service MappedResourceFactory > at org.richfaces.application.ServiceTracker$1.invoke(ServiceTracker.java:151) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at com.sun.proxy.$Proxy96.createResource(Unknown Source) > at org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:266) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at com.sun.faces.renderkit.html_basic.StylesheetRenderer.encodeEnd(StylesheetRenderer.java:97) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:832) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:620) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:553) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:482) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:689) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:663) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jsp.index_jsp._jspService(index_jsp.java:60) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:365) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:309) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:242) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:33:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:33:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13612) Document styling attributes for rich:dataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13612: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 2 > Document styling attributes for rich:dataTable > ---------------------------------------------- > > Key: RF-13612 > URL: https://issues.jboss.org/browse/RF-13612 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables, doc > Affects Versions: 4.3.6 > Reporter: Michal Petrov > Fix For: 4.5.0.Alpha3 > > > There are several attributes that can be assigned to a dataTable such as {{headerCellClass}} or {{firstColumnFooterClass}} (see [AbstractTableRenderer|https://github.com/richfaces4/components/blob/master/iteration/ui/src/main/java/org/richfaces/renderkit/AbstractTableRenderer.java#L325]). The renderer is set to process them but they are not documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:33:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:33:34 -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 (was: 4.5.0.Alpha3 - Sprint 1) > 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 > > > Drag/Drop support should be added to file upload component . > Like the primefaces fileUploadDnd : http://www.primefaces.org/showcase/ui/fileUploadDnd.jsf -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:35:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:35:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13610) Resource loading error in the showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13610: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Resource loading error in the showcase > -------------------------------------- > > Key: RF-13610 > URL: https://issues.jboss.org/browse/RF-13610 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling, showcase > Reporter: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Getting the runtime error: > {code} > 15:44:26,792 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-/0.0.0.0:8080-1) Error Rendering View[/index.xhtml]: java.lang.IllegalStateException: Failed to obtain service MappedResourceFactory > at org.richfaces.application.ServiceTracker$1.invoke(ServiceTracker.java:151) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at com.sun.proxy.$Proxy96.createResource(Unknown Source) > at org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:266) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at com.sun.faces.renderkit.html_basic.StylesheetRenderer.encodeEnd(StylesheetRenderer.java:97) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:832) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:620) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:553) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:482) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:689) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:663) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jsp.index_jsp._jspService(index_jsp.java:60) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:365) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:309) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:242) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:35:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:35:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13610) Resource loading error in the showcase In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13610. -------------------------------- Assignee: Brian Leathem Resolution: Done > Resource loading error in the showcase > -------------------------------------- > > Key: RF-13610 > URL: https://issues.jboss.org/browse/RF-13610 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling, showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Getting the runtime error: > {code} > 15:44:26,792 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http-/0.0.0.0:8080-1) Error Rendering View[/index.xhtml]: java.lang.IllegalStateException: Failed to obtain service MappedResourceFactory > at org.richfaces.application.ServiceTracker$1.invoke(ServiceTracker.java:151) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at com.sun.proxy.$Proxy96.createResource(Unknown Source) > at org.richfaces.resource.ResourceFactoryImpl.resolveMappedResource(ResourceFactoryImpl.java:393) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceFactoryImpl.createMappedResource(ResourceFactoryImpl.java:360) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:266) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280) [richfaces-4.5.0-SNAPSHOT.jar:4.5.0-SNAPSHOT] > at com.sun.faces.renderkit.html_basic.StylesheetRenderer.encodeEnd(StylesheetRenderer.java:97) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:881) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:439) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.19-redhat-1.jar:2.1.19-redhat-1] > at org.richfaces.demo.arrangeablemodel.PersistenceLifecycle.render(PersistenceLifecycle.java:66) [classes:] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:832) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:620) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:553) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:482) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:689) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:663) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jsp.index_jsp._jspService(index_jsp.java:60) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:365) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:309) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:242) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:35:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:35:33 -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: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:37:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:37:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13571) Upgrade Arquillian components: Core, Drone, Warp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13571: ------------------------------- Fix Version/s: 4.5.0.Alpha3 (was: 5.0.0.Alpha4) > Upgrade Arquillian components: Core, Drone, Warp > ------------------------------------------------ > > Key: RF-13571 > URL: https://issues.jboss.org/browse/RF-13571 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha4 > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:37:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:37:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13571) Upgrade Arquillian components: Core, Drone, Warp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13571: ------------------------------- Affects Version/s: (was: 5.0.0.Alpha4) > Upgrade Arquillian components: Core, Drone, Warp > ------------------------------------------------ > > Key: RF-13571 > URL: https://issues.jboss.org/browse/RF-13571 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:37:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:37:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13571) Upgrade Arquillian components: Core, Drone, Warp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13571: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 2 > Upgrade Arquillian components: Core, Drone, Warp > ------------------------------------------------ > > Key: RF-13571 > URL: https://issues.jboss.org/browse/RF-13571 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:39:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:39:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13612) Document styling attributes for rich:dataTable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13612: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Document styling attributes for rich:dataTable > ---------------------------------------------- > > Key: RF-13612 > URL: https://issues.jboss.org/browse/RF-13612 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables, doc > Affects Versions: 4.3.6 > Reporter: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > There are several attributes that can be assigned to a dataTable such as {{headerCellClass}} or {{firstColumnFooterClass}} (see [AbstractTableRenderer|https://github.com/richfaces4/components/blob/master/iteration/ui/src/main/java/org/richfaces/renderkit/AbstractTableRenderer.java#L325]). The renderer is set to process them but they are not documented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:43:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:43:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13571) Upgrade Arquillian components: Core, Drone, Warp In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13571: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Upgrade Arquillian components: Core, Drone, Warp > ------------------------------------------------ > > Key: RF-13571 > URL: https://issues.jboss.org/browse/RF-13571 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Luk?? Fry? > Assignee: Luk?? Fry? > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:43:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:43:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13426) Showcase - version info in footer shows 5.0.0.Alpha2 instead of 4.5.0.Alpha1 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13426. -------------------------------- Fix Version/s: (was: 4.5.0.Alpha3) Resolution: Out of Date > Showcase - version info in footer shows 5.0.0.Alpha2 instead of 4.5.0.Alpha1 > ---------------------------------------------------------------------------- > > Key: RF-13426 > URL: https://issues.jboss.org/browse/RF-13426 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.5.0.Alpha1 > Reporter: Juraj H?ska > Priority: Minor > > In showcase footer page section, there is _RichFaces Framework by JBoss by Red Hat, version 5.0.0.Alpha2_. > It should be with 4.5.0.Alpha1. > The version is so because it is retrieved from {{VersionBean}}, which is from the 5.0.0.Alpha2 framework. > IMHO it can cause some misunderstanding, or do we want to stress that the core is from RF 5 ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 01:45:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 01:45:34 -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:comment-tabpanel&focusedCommentId=12963421#comment-12963421 ] Brian Leathem commented on RF-13505: ------------------------------------ [~lfryc] what's the status of this issue? Is the new EPVCI merged now? > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 02:23:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 02:23:33 -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:comment-tabpanel&focusedCommentId=12963423#comment-12963423 ] Brian Leathem commented on RF-13602: ------------------------------------ QE = [Quality Engineering|http://en.wikipedia.org/wiki/Quality_engineering] > 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: Pavol Pitonak > Labels: ie11 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 04:17:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 24 Apr 2014 04:17:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13613) ContextMenu doesn't show on mouseover In-Reply-To: References: Message-ID: Michal Petrov created RF-13613: ---------------------------------- Summary: ContextMenu doesn't show on mouseover Key: RF-13613 URL: https://issues.jboss.org/browse/RF-13613 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.3.6 Reporter: Michal Petrov Assignee: Michal Petrov Setting @showEvent="mouseover" doesn't work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 04:27:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 24 Apr 2014 04:27:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13613) ContextMenu doesn't show on mouseover In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13613. -------------------------------- Fix Version/s: 4.3.7 Resolution: Done The default showEvent in ContextMenuRendererBase was "mouseover" and so the renderer was skipping it if it was set manually, the default event on the JS side is however "contextmenu". > ContextMenu doesn't show on mouseover > ------------------------------------- > > Key: RF-13613 > URL: https://issues.jboss.org/browse/RF-13613 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.6 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.7 > > > Setting @showEvent="mouseover" doesn't work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 06:59:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 24 Apr 2014 06:59:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 tests are failing In-Reply-To: References: Message-ID: Michal Petrov created RF-13614: ---------------------------------- Summary: RichFaces 4.5 tests are failing Key: RF-13614 URL: https://issues.jboss.org/browse/RF-13614 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Michal Petrov -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 07:09:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 24 Apr 2014 07:09:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov reassigned RF-13614: ---------------------------------- Assignee: Michal Petrov > RichFaces 4.5 tests are failing > ------------------------------- > > Key: RF-13614 > URL: https://issues.jboss.org/browse/RF-13614 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > Assignee: Michal Petrov > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 07:09:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 24 Apr 2014 07:09:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963468#comment-12963468 ] Michal Petrov commented on RF-13614: ------------------------------------ Most if not all of those are resource related and were caused by refactoring of the core (RF-13582). Those I'm fixing. There are some I'm not sure about: resources from {{org.richfaces/common}} in core, such as {{richfaces-base-component.js}} were copied over to components to avoid collision with RF 5. Currently those resources are not in core and several tests fail because of that, do we put them back into core, or leave them in components and update the tests? {{ResourceLibraryTest}} fails on incorrectly rendered page (the test page should contain links to JS files but the head is empty). Don't know what's causing it. > RichFaces 4.5 tests are failing > ------------------------------- > > Key: RF-13614 > URL: https://issues.jboss.org/browse/RF-13614 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 10:18:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 10:18:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13614: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > RichFaces 4.5 tests are failing > ------------------------------- > > Key: RF-13614 > URL: https://issues.jboss.org/browse/RF-13614 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 10:18:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 10:18:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 unit tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13614: ------------------------------- Summary: RichFaces 4.5 unit tests are failing (was: RichFaces 4.5 tests are failing) > RichFaces 4.5 unit tests are failing > ------------------------------------ > > Key: RF-13614 > URL: https://issues.jboss.org/browse/RF-13614 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 10:24:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 10:24:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 unit tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13614: ------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > RichFaces 4.5 unit tests are failing > ------------------------------------ > > Key: RF-13614 > URL: https://issues.jboss.org/browse/RF-13614 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 10:24:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 10:24:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 unit tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13614: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 1 > RichFaces 4.5 unit tests are failing > ------------------------------------ > > Key: RF-13614 > URL: https://issues.jboss.org/browse/RF-13614 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 10:30:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 10:30:35 -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 ] Brian Leathem updated RF-13514: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 2 (was: 4.5.0.Alpha3 - Sprint 1) > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 10:32:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Thu, 24 Apr 2014 10:32:34 -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 ] Michal Petrov resolved RF-13160. -------------------------------- Resolution: Done > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 10:42:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 10:42:37 -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 ] Brian Leathem updated RF-13505: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 1 > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 10:42:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 10:42:37 -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 ] Brian Leathem updated RF-13505: ------------------------------- Original Estimate: 2 days Remaining Estimate: 2 days > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 10:42:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Thu, 24 Apr 2014 10:42:38 -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 ] Brian Leathem updated RF-13505: ------------------------------- Original Estimate: 1 day (was: 2 days) Remaining Estimate: 1 day (was: 2 days) > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 14:00:34 2014 From: issues at jboss.org (H G (JIRA)) Date: Thu, 24 Apr 2014 14:00:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13469) RF 5 pickList NPE ResourceServletMapping - resource.getLibraryName() In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] H G updated RF-13469: --------------------- Affects Version/s: 5.0.0.Alpha3 > RF 5 pickList NPE ResourceServletMapping - resource.getLibraryName() > -------------------------------------------------------------------- > > Key: RF-13469 > URL: https://issues.jboss.org/browse/RF-13469 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2, 5.0.0.Alpha3 > Environment: WildFly CR1, RF 5 Alpha2, jboss-jsf-api_2.2_spec-2.2.4 > WildFly B1, RF 5 Alpha2, jboss-jsf-api_2.2_spec-2.2.3 > Firefox 26.0 > Reporter: H G > Labels: libraryName, npe, pickList, resource > Fix For: 5.0.0.Alpha4 > > > An exception is handled. The exception is related to the source code "resource.getLibraryName()" from ResourceServletMapping > Link to exception - https://community.jboss.org/message/852156 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 15:18:33 2014 From: issues at jboss.org (Holger Walter (JIRA)) Date: Thu, 24 Apr 2014 15:18:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling In-Reply-To: References: Message-ID: Holger Walter created RF-13615: ---------------------------------- Summary: 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.5 Environment: Problem can be tested in richfaces showcase. http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extendedDataTable&skin=blueSky Reporter: Holger Walter Affects version 4.3.6 - but issue tracker complained, that 4.3.6 does not exist 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 15:18:33 2014 From: issues at jboss.org (Holger Walter (JIRA)) Date: Thu, 24 Apr 2014 15:18:33 -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 ] Holger Walter updated RF-13615: ------------------------------- Affects Version/s: 4.3.6 (was: 4.3.5) > 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 > > Affects version 4.3.6 - but issue tracker complained, that 4.3.6 does not exist > 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Thu Apr 24 15:18:33 2014 From: issues at jboss.org (Holger Walter (JIRA)) Date: Thu, 24 Apr 2014 15:18:33 -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 ] Holger Walter updated RF-13615: ------------------------------- Description: 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 was: Affects version 4.3.6 - but issue tracker complained, that 4.3.6 does not exist 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 > 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 > > 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 00:38:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 00:38:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13613) ContextMenu doesn't show on mouseover In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963694#comment-12963694 ] Brian Leathem commented on RF-13613: ------------------------------------ Nice catch [~michpetrov]! > ContextMenu doesn't show on mouseover > ------------------------------------- > > Key: RF-13613 > URL: https://issues.jboss.org/browse/RF-13613 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.6 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.3.7 > > > Setting @showEvent="mouseover" doesn't work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 00:42:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 00:42:33 -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=12963695#comment-12963695 ] Brian Leathem commented on RF-13615: ------------------------------------ Interesting find [~wlh]. If you are interested in doing more debugging to help us narrow down the problem, refer to this client-side debugging howto: https://github.com/richfaces/richfaces/wiki/Debugging-RichFaces > 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 > > 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 01:46:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 01:46:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13564) rich:pickList shows an outline when clicked In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13564: ------------------------------- Priority: Trivial (was: Major) > rich:pickList shows an outline when clicked > ------------------------------------------- > > Key: RF-13564 > URL: https://issues.jboss.org/browse/RF-13564 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Priority: Trivial > Fix For: 4.3.7 > > > Hi all, i use rich:pickList and i was amazing. If we press left button on a mouse(don't release left button) on rich:pickList we'll see rectangle. You can check it [here|http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=pickList&skin=blueSky]. > I found a solution: > in file template "picklist.template.xml" > {code} > ... >
cdk:passThrough="onclick:onclick ondblclick:ondblclick onmousedown:onmousedown onmouseup:onmouseup onmouseover:onmouseover > onmousemove:onmousemove onmouseout:onmouseout onkeypress:onkeypress onkeydown:onkeydown onkeyup:onkeyup"> > ... > {code} > used tabindex attribue for DIV. > Why? > DIV elements are not compatible with tabindex ([see the HTML 4.01 spec|http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex]). > I can create pull request :). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 01:46:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 01:46:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13537) Autocomplete: onbegin attribute ignored In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13537: ------------------------------- Fix Version/s: 4.5-Tracking (was: 4.3.7) > Autocomplete: onbegin attribute ignored > --------------------------------------- > > Key: RF-13537 > URL: https://issues.jboss.org/browse/RF-13537 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Fix For: 4.5-Tracking > > > "onbegin" attribute of rich:autocomplete is always ignored! > I suggest next fix: > In file Autocomplete.js: > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > rf.ajax(this.id, event, {parameters: params, error: ajaxError, complete:ajaxSuccess}); > } > {code} > for fixing, we must replace on > {code} > var callAjax = function(event, callback) { > ... > this.isFirstAjax = false; > //caution: JSF submits inputs with empty names causing "WARNING: Parameters: Invalid chunk ignored." in Tomcat log > var params = {}; > params[this.id + ".ajax"] = "1"; > var parameters_extended = {parameters: params, error: ajaxError, complete:ajaxSuccess}; > if (this.options.onbegin != undefined) { > parameters_extended.begin = this.options.onbegin; > } > rf.ajax(this.id, event, parameters_extended); > } > {code} > I can create pull request if everything ok. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 01:48:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 01:48:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13507) Backport RF-13317 (EPVCI should specify correct ViewState) to 4.3 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13507: ------------------------------- Fix Version/s: 4.5.0.Alpha3 (was: 4.3.7) > Backport RF-13317 (EPVCI should specify correct ViewState) to 4.3 > ----------------------------------------------------------------- > > 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? > Fix For: 4.5.0.Alpha3 > > > Let's let RF-13317 stabilize in 5.x first. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 01:48:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 01:48:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13611) RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13611: ------------------------------- Fix Version/s: 4.5-Tracking (was: 4.3.7) > RichFaces 5.0.0.Alpha3 doesn't work with Weld 2.2.0.Final > --------------------------------------------------------- > > Key: RF-13611 > URL: https://issues.jboss.org/browse/RF-13611 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha3 > Reporter: Juergen Zimmermann > Fix For: 4.5-Tracking > > > I'm using WildFly 8.0.0.CR1 and Weld 2.2.0.Final (via the WildFly patch mechanism). However, I'm getting the stacktrace below. When I patch WildFly 8.0.0.CR1 with the predecessor version Weld 2.2.0.CR2, then the issue is gone. > {code} > ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.deployment.unit."shop.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."shop.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:1142) [rt.jar:1.8.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > org.jboss.weld.exceptions.DefinitionException: WELD-000412: ObserverMethod.getReception() returned null for org.richfaces.push.cdi.PushCDIExtension$PushObserverMethod at 31e23242 > at org.jboss.weld.util.Observers.validateObserverMethod(Observers.java:118) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.addObserverMethod(AfterBeanDiscoveryImpl.java:158) > at org.richfaces.push.cdi.PushCDIExtension.afterBeanDiscovery(PushCDIExtension.java:99) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:90) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:271) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:258) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:237) > at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:174) > at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:133) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:107) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > 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:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44) > at org.jboss.weld.bootstrap.events.AfterBeanDiscoveryImpl.fire(AfterBeanDiscoveryImpl.java:59) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:393) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > 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} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 05:48:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 25 Apr 2014 05:48:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 unit tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963765#comment-12963765 ] Michal Petrov commented on RF-13614: ------------------------------------ The tests that were missing resources were duplicates to component tests, I've removed them. The other failures were caused by mismatches between renderer types defined in classes and in *.faces-config.xml. Framework tests are fixed but I'm still getting some errors in component tests. > RichFaces 4.5 unit tests are failing > ------------------------------------ > > Key: RF-13614 > URL: https://issues.jboss.org/browse/RF-13614 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 06:02:34 2014 From: issues at jboss.org (abhishek vijra (JIRA)) Date: Fri, 25 Apr 2014 06:02:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: abhishek vijra created RF-13616: ----------------------------------- Summary: PopupPanel autosize with togglePanel doesn't resize Key: RF-13616 URL: https://issues.jboss.org/browse/RF-13616 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.2.3.Final Reporter: abhishek vijra PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 06:02:34 2014 From: issues at jboss.org (abhishek vijra (JIRA)) Date: Fri, 25 Apr 2014 06:02:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] abhishek vijra updated RF-13616: -------------------------------- Steps to Reproduce: 1. Without moving the PopupPanel directly switch to Panel Item 2. 2. The PopupPanel is autosized as expected, correctly adjusting to the size difference between its previous and its current content. Now switch back to Panel Item 1. 3. Move the PopupPanel around and then switch back to Panel Item 2. 4. Notice that the PopupPanel isn't properly autosized anymore but is now stuck to the smaller width of Panel Item 1. Switching to Panel Item 2 will autosize the PopupPanel properly if and only if it hasn't been moved yet. Looking into the PopupPanel source code we found that while initially moving the PopupPanel, the width of the currently active Panel Item is hard-set on said divs in the PopupPanel RichFaces.ui.PopupPanel.prototype.doResizeOrMove method which prevents all further autosizing on move. A possible workaround:- which overrides the original doResizeOrMove method on the RichFaces.ui.PopupPanel prototype and simply undoes the modifications of the previously undefined CSS widths properties on the relevant divs if the PopupPanel autosized attribute is enabled--can be activated by uncommenting the following code in /main/webapp/resources/js/patch-popup-panel.js: /* (function() { var richfacesUiPopupPanelDoResizeOrMove = RichFaces.ui.PopupPanel.prototype.doResizeOrMove; RichFaces.ui.PopupPanel.prototype.doResizeOrMove = function(diff) { var ret = richfacesUiPopupPanelDoResizeOrMove.call(this, diff); if (this.options.autosized) { this.cdiv.css("width", ""); this.contentDiv.css("width", ""); this.scrollerDiv.css("width", ""); this.shadowDiv.css("width", ""); } return ret; }; }()); */ was: 1. Without moving the PopupPanel directly switch to Panel Item 2. 2. The PopupPanel is autosized as expected, correctly adjusting to the size difference between its previous and its current content. Now switch back to Panel Item 1. 3. Move the PopupPanel around and then switch back to Panel Item 2. 4. Notice that the PopupPanel isn't properly autosized anymore but is now stuck to the smaller width of Panel Item 1. Switching to Panel Item 2 will autosize the PopupPanel properly if and only if it hasn't been moved yet. Looking into the PopupPanel source code we found that while initially moving the PopupPanel, the width of the currently active Panel Item is hard-set on said divs in the PopupPanel RichFaces.ui.PopupPanel.prototype.doResizeOrMove method which prevents all further autosizing on move. A possible workaround----which overrides the original doResizeOrMove method on the RichFaces.ui.PopupPanel prototype and simply undoes the modifications of the previously undefined CSS widths properties on the relevant divs if the PopupPanel autosized attribute is enabled--can be activated by uncommenting the following code in /main/webapp/resources/js/patch-popup-panel.js: /* (function() { var richfacesUiPopupPanelDoResizeOrMove = RichFaces.ui.PopupPanel.prototype.doResizeOrMove; RichFaces.ui.PopupPanel.prototype.doResizeOrMove = function(diff) { var ret = richfacesUiPopupPanelDoResizeOrMove.call(this, diff); if (this.options.autosized) { this.cdiv.css("width", ""); this.contentDiv.css("width", ""); this.scrollerDiv.css("width", ""); this.shadowDiv.css("width", ""); } return ret; }; }()); */ > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final > Reporter: abhishek vijra > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 06:02:34 2014 From: issues at jboss.org (abhishek vijra (JIRA)) Date: Fri, 25 Apr 2014 06:02:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] abhishek vijra updated RF-13616: -------------------------------- Steps to Reproduce: 1. Without moving the PopupPanel directly switch to Panel Item 2. 2. The PopupPanel is autosized as expected, correctly adjusting to the size difference between its previous and its current content. Now switch back to Panel Item 1. 3. Move the PopupPanel around and then switch back to Panel Item 2. 4. Notice that the PopupPanel isn't properly autosized anymore but is now stuck to the smaller width of Panel Item 1. Switching to Panel Item 2 will autosize the PopupPanel properly if and only if it hasn't been moved yet. Looking into the PopupPanel source code we found that while initially moving the PopupPanel, the width of the currently active Panel Item is hard-set on said divs in the PopupPanel RichFaces.ui.PopupPanel.prototype.doResizeOrMove method which prevents all further autosizing on move. A possible workaround----which overrides the original doResizeOrMove method on the RichFaces.ui.PopupPanel prototype and simply undoes the modifications of the previously undefined CSS widths properties on the relevant divs if the PopupPanel autosized attribute is enabled--can be activated by uncommenting the following code in /main/webapp/resources/js/patch-popup-panel.js: /* (function() { var richfacesUiPopupPanelDoResizeOrMove = RichFaces.ui.PopupPanel.prototype.doResizeOrMove; RichFaces.ui.PopupPanel.prototype.doResizeOrMove = function(diff) { var ret = richfacesUiPopupPanelDoResizeOrMove.call(this, diff); if (this.options.autosized) { this.cdiv.css("width", ""); this.contentDiv.css("width", ""); this.scrollerDiv.css("width", ""); this.shadowDiv.css("width", ""); } return ret; }; }()); */ was: 1. Without moving the PopupPanel directly switch to Panel Item 2. 2. The PopupPanel is autosized as expected, correctly adjusting to the size difference between its previous and its current content. Now switch back to Panel Item 1. 3. Move the PopupPanel around and then switch back to Panel Item 2. 4. Notice that the PopupPanel isn't properly autosized anymore but is now stuck to the smaller width of Panel Item 1. Switching to Panel Item 2 will autosize the PopupPanel properly if and only if it hasn't been moved yet. Looking into the PopupPanel source code we found that while initially moving the PopupPanel, the width of the currently active Panel Item is hard-set on said divs in the PopupPanel RichFaces.ui.PopupPanel.prototype.doResizeOrMove method which prevents all further autosizing on move. A possible workaround--which overrides the original doResizeOrMove method on the RichFaces.ui.PopupPanel prototype and simply undoes the modifications of the previously undefined CSS widths properties on the relevant divs if the PopupPanel autosized attribute is enabled--can be activated by uncommenting the following code in /main/webapp/resources/js/patch-popup-panel.js: /* (function() { var richfacesUiPopupPanelDoResizeOrMove = RichFaces.ui.PopupPanel.prototype.doResizeOrMove; RichFaces.ui.PopupPanel.prototype.doResizeOrMove = function(diff) { var ret = richfacesUiPopupPanelDoResizeOrMove.call(this, diff); if (this.options.autosized) { this.cdiv.css("width", ""); this.contentDiv.css("width", ""); this.scrollerDiv.css("width", ""); this.shadowDiv.css("width", ""); } return ret; }; }()); */ > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final > Reporter: abhishek vijra > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 06:06:33 2014 From: issues at jboss.org (abhishek vijra (JIRA)) Date: Fri, 25 Apr 2014 06:06:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] abhishek vijra updated RF-13616: -------------------------------- Attachment: popupPanel.zip > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final > Reporter: abhishek vijra > Attachments: popupPanel.zip > > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 07:40:34 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 25 Apr 2014 07:40:34 -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 ] Pavol Pitonak reassigned RF-13602: ---------------------------------- Assignee: Juraj H?ska (was: Pavol Pitonak) > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 07:42:34 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 25 Apr 2014 07:42:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11417) Tab: investigate why @action does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963799#comment-12963799 ] Pavol Pitonak commented on RF-11417: ------------------------------------ Brian, the pull request has already been verified, see my comment in RF-11427 https://issues.jboss.org/browse/RF-11427?focusedCommentId=12959188&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12959188 {quote} Thanks Valiantsin Shukaila, it works fine now. Brian Leathem, the is a checkstyle violation on line 580 and it needs to be rebased to lastest master. IMHO we can handle these minor issues, WDYT? {quote} > Tab: investigate why @action does not work > ------------------------------------------ > > Key: RF-11417 > URL: https://issues.jboss.org/browse/RF-11417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Fix For: 5-Tracking > > > Determine why rich:tab @action has not been implemented. > Verify that its implementation can't affect current applications (and try to find possible workaround). > Implement @action and @actionListener. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 07:42:34 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 25 Apr 2014 07:42:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13568) IllegalArgumentException for PushResource.jsf In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak reassigned RF-13568: ---------------------------------- Assignee: Ji?? ?tefek (was: Pavol Pitonak) > IllegalArgumentException for PushResource.jsf > --------------------------------------------- > > Key: RF-13568 > URL: https://issues.jboss.org/browse/RF-13568 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha3 > Environment: WildFly snapshot with Undertow 1.0.1 > Reporter: Juergen Zimmermann > Assignee: Ji?? ?tefek > > Im using the latest WildFly snapshot containing Undertow 1.0.1. I'm getting tons of stacktraces like the following: > {code} > [io.undertow.request] UT005023: Exception handling request to /shop/rfRes/org.richfaces.ui.ajax.push.PushResource.jsf: java.lang.IllegalArgumentException: pushTopic request parameter must be present > at org.richfaces.ui.ajax.push.PushResource.encode(PushResource.java:87) [richfaces-5.0.0.Alpha3.jar:5.0.0.Alpha3] > at org.richfaces.resource.UserResourceWrapperImpl.encode(UserResourceWrapperImpl.java:187) [richfaces-5.0.0.Alpha3.jar:5.0.0.Alpha3] > at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:229) [richfaces-5.0.0.Alpha3.jar:5.0.0.Alpha3] > 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.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.1.Final.jar:1.0.1.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.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.1.Final.jar:1.0.1.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.1.Final.jar:1.0.1.Final] > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) [undertow-core-1.0.1.Final.jar:1.0.1.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 07:44:33 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Fri, 25 Apr 2014 07:44:33 -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 ] Pavol Pitonak reassigned RF-13604: ---------------------------------- Assignee: Matej Novotny (was: Pavol Pitonak) > 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 > Assignee: Matej Novotny > Labels: editor, glassfish, jsf22 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 09:06:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 25 Apr 2014 09:06:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 unit tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13614. -------------------------------- Resolution: Done And the last error is gone (was missing another faces-config). > RichFaces 4.5 unit tests are failing > ------------------------------------ > > Key: RF-13614 > URL: https://issues.jboss.org/browse/RF-13614 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 11:06:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Fri, 25 Apr 2014 11:06:33 -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=12963876#comment-12963876 ] Michal Petrov commented on RF-13591: ------------------------------------ The reported failures shouldn't be an issue, those were component tests and were removed/merged into components. There remain some other tests in framework that use ajax and those will need to be moved to components. > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 11:58:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 11:58:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11417) Tab: investigate why @action does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11417: ------------------------------- Fix Version/s: (was: 5-Tracking) > Tab: investigate why @action does not work > ------------------------------------------ > > Key: RF-11417 > URL: https://issues.jboss.org/browse/RF-11417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > > Determine why rich:tab @action has not been implemented. > Verify that its implementation can't affect current applications (and try to find possible workaround). > Implement @action and @actionListener. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 11:58:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 11:58:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11417) Tab: investigate why @action does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11417: ------------------------------- Fix Version/s: 4.3.7 > Tab: investigate why @action does not work > ------------------------------------------ > > Key: RF-11417 > URL: https://issues.jboss.org/browse/RF-11417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Fix For: 4.3.7 > > > Determine why rich:tab @action has not been implemented. > Verify that its implementation can't affect current applications (and try to find possible workaround). > Implement @action and @actionListener. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 12:00:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 12:00:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 unit tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963892#comment-12963892 ] Brian Leathem commented on RF-13614: ------------------------------------ Nice work [~michpetrov]. It's good to see that our unit tests are catching errors in the faces-config files. > RichFaces 4.5 unit tests are failing > ------------------------------------ > > Key: RF-13614 > URL: https://issues.jboss.org/browse/RF-13614 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 12:02:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 12:02:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13616: ---------------------------------- Assignee: Pavol Pitonak QE, please verify > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final > Reporter: abhishek vijra > Assignee: Pavol Pitonak > Attachments: popupPanel.zip > > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 12:42:33 2014 From: issues at jboss.org (Holger Walter (JIRA)) Date: Fri, 25 Apr 2014 12:42:33 -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=12963903#comment-12963903 ] Holger Walter commented on RF-13615: ------------------------------------ Hi Brian, thanks for the feedback. Just tried to debug the client as described in your link. Unfortunately (RF 4.3.6) does not work in Firefox 28. Get the message 'Richfaces.HtmlLog()' is not a constructor'. In IE10 works. I did some debugging regarding the 2nd ajax request. I'm not really sure, but I think the function 'setColumnWidth' in extendedDataTable.js is the problem. It always sends ajax requests in case it is called (last line in function) - and it will always ( on each other request) be called after the width of a col has changed. Hope you can check this. Regards wlh > 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 > > 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 16:22:34 2014 From: issues at jboss.org (Holger Walter (JIRA)) Date: Fri, 25 Apr 2014 16:22:34 -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=12963922#comment-12963922 ] Holger Walter commented on RF-13615: ------------------------------------ Update: I tried to adapt the 'setColumnWidth' function in extendedDataTable.js, by applying a small change: the ajax request at the end of the function is now only triggered in case the respective column is not already available in the array 'newWidths', with the given width. This workaround works - the columns are sized correctly, and the second ajax request is not sent. However, your approach of correcting the column width on client side on each request, after it had been resized once is not really the most performant one, especially when you take IE8 into account. As far as I remember you added a fix in 4.3.5 which fixed incorrect column sizes after scrolling. I have the feeling, that the current problem was introduced with this fix - but I'm not sure. Best reagrds wlh > 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 > > 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Fri Apr 25 18:32:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Fri, 25 Apr 2014 18:32:34 -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 reassigned RF-13615: ---------------------------------- Assignee: Pavol Pitonak QE would you please verify this issue? If we could also ascertain if/whether it is a regression that would be great. > 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: Pavol Pitonak > > 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sat Apr 26 01:42:33 2014 From: issues at jboss.org (abhishek vijra (JIRA)) Date: Sat, 26 Apr 2014 01:42:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963944#comment-12963944 ] abhishek vijra commented on RF-13616: ------------------------------------- The issue exists in FF , Chrome and IE . > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final > Reporter: abhishek vijra > Assignee: Pavol Pitonak > Attachments: popupPanel.zip > > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Apr 27 23:12:33 2014 From: issues at jboss.org (Gurinder Randhawa (JIRA)) Date: Sun, 27 Apr 2014 23:12:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12554) inside doesn't work without a dummy usage outside In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963980#comment-12963980 ] Gurinder Randhawa commented on RF-12554: ---------------------------------------- WE are using tooltipster javascript plugin in our xhtml (richfaces 4,3,5) We use
A. QUESTION TOOL TIP INSIDE REPEAT
which doesn't work inside a ui:repeat or a4j:repeat tag. The javascript is loaded in our template and is firing, but results are not rendered in styled format. The tooltip works everywhere else. > inside doesn't work without a dummy usage outside > ---------------------------------------------------------------------------- > > 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 > Priority: Minor > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Sun Apr 27 23:54:33 2014 From: issues at jboss.org (Gurinder Randhawa (JIRA)) Date: Sun, 27 Apr 2014 23:54:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12554) inside doesn't work without a dummy usage outside In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963981#comment-12963981 ] Gurinder Randhawa commented on RF-12554: ---------------------------------------- More details on this issue, we are experiencing this issue inside a composite component having a repeat tag. The tip shows fine in a4j:repeat tag outside a composite component. > inside doesn't work without a dummy usage outside > ---------------------------------------------------------------------------- > > 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 > Priority: Minor > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 28 05:20:34 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 28 Apr 2014 05:20:34 -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:comment-tabpanel&focusedCommentId=12964021#comment-12964021 ] Juraj H?ska commented on RF-13602: ---------------------------------- I have not reproduce the issue. The above mentioned functionality works for me on all browsers. I have reproduced it on this code: # clone from this branch: https://github.com/jhuska/richfaces-sanbox/tree/RF-13602 # build it with {{mvn clean package}} # deploy it on JBoss AS 7.1.1.Final # load http://localhost:8080/richfaces-sanbox # select in the {{r:select}} second option # see that the {{fileUpload}} is enabled [~wdmmza] can you confirm this ? Is my example somehow different from yours (I have trimmed all unnecessary code) ? Or can you add there a code which makes it non working ? > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 28 05:22:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 28 Apr 2014 05:22:33 -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 ] Juraj H?ska updated RF-13602: ----------------------------- Labels: ie11 waiting_on_user (was: ie11) > 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, waiting_on_user > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 28 05:22:34 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Mon, 28 Apr 2014 05:22:34 -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:comment-tabpanel&focusedCommentId=12964021#comment-12964021 ] Juraj H?ska edited comment on RF-13602 at 4/28/14 5:21 AM: ----------------------------------------------------------- I have not reproduce the issue. The above mentioned functionality works for me on all browsers. I have tried it on this code: # clone from this branch: https://github.com/jhuska/richfaces-sanbox/tree/RF-13602 # build it with {{mvn clean package}} # deploy it on JBoss AS 7.1.1.Final # load http://localhost:8080/richfaces-sanbox # select in the {{r:select}} second option # see that the {{fileUpload}} is enabled [~wdmmza] can you confirm this ? Is my example somehow different from yours (I have trimmed all unnecessary code) ? Or can you add there a code which makes it non working ? was (Author: jhuska): I have not reproduce the issue. The above mentioned functionality works for me on all browsers. I have reproduced it on this code: # clone from this branch: https://github.com/jhuska/richfaces-sanbox/tree/RF-13602 # build it with {{mvn clean package}} # deploy it on JBoss AS 7.1.1.Final # load http://localhost:8080/richfaces-sanbox # select in the {{r:select}} second option # see that the {{fileUpload}} is enabled [~wdmmza] can you confirm this ? Is my example somehow different from yours (I have trimmed all unnecessary code) ? Or can you add there a code which makes it non working ? > 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, waiting_on_user > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 28 06:10:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Mon, 28 Apr 2014 06:10:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13614) RichFaces 4.5 unit tests are failing In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964031#comment-12964031 ] Michal Petrov commented on RF-13614: ------------------------------------ They are not exactly catching the error, they fail because the components don't work properly. > RichFaces 4.5 unit tests are failing > ------------------------------------ > > Key: RF-13614 > URL: https://issues.jboss.org/browse/RF-13614 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 28 12:24:33 2014 From: issues at jboss.org (Walter Maidub (JIRA)) Date: Mon, 28 Apr 2014 12:24:33 -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 ] Walter Maidub updated RF-13602: ------------------------------- Attachment: Dear Juraj H?ska.docx Documents that describes the issues > 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, waiting_on_user > Attachments: Dear Juraj H?ska.docx > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 28 12:28:33 2014 From: issues at jboss.org (Walter Maidub (JIRA)) Date: Mon, 28 Apr 2014 12:28:33 -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:comment-tabpanel&focusedCommentId=12964169#comment-12964169 ] Walter Maidub edited comment on RF-13602 at 4/28/14 12:27 PM: -------------------------------------------------------------- Juraj H?ska, we downloaded your code and the problem persist. In this comments, I attach the documents that describes the issues was (Author: wdmmza): Documents that describes the issues > 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, waiting_on_user > Attachments: Dear Juraj H?ska.docx > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 28 17:20:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Macko_=28JIRA=29?=) Date: Mon, 28 Apr 2014 17:20:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13617) CDK - NPE getOutputFileName In-Reply-To: References: Message-ID: Luk?? Macko created RF-13617: -------------------------------- Summary: CDK - NPE getOutputFileName Key: RF-13617 URL: https://issues.jboss.org/browse/RF-13617 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Reporter: Luk?? Macko Priority: Blocker During backporting chart to 4.5.X I come across this exception. In RF5 CDK works ok. {{[ERROR] Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException: NullPointerException -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at com.sun.tools.javac.main.Main.compile(Main.java:469) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:132) at org.richfaces.cdk.apt.AptBuilder.build(AptBuilder.java:47) at org.richfaces.cdk.Generator.execute(Generator.java:155) at org.richfaces.builder.mojo.GenerateMojo.execute(GenerateMojo.java:254) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) ... 20 more Caused by: java.lang.reflect.InvocationTargetException 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.richfaces.cdk.apt.LibraryProxyInterceptor.invoke(LibraryProxyInterceptor.java:18) at org.richfaces.cdk.generate.java.taghandler.TagHandlerWriter.render(TagHandlerWriter.java:48) at org.richfaces.cdk.apt.DefaultLibraryGenerator.generate(DefaultLibraryGenerator.java:28) at org.richfaces.cdk.apt.CdkProcessorImpl.generate(CdkProcessorImpl.java:157) at org.richfaces.cdk.apt.CdkProcessorImpl.continueAfterJavaSourceProcessing(CdkProcessorImpl.java:133) at org.richfaces.cdk.apt.CdkProcessorImpl.process(CdkProcessorImpl.java:106) at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793) at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$200(JavacProcessingEnvironment.java:97) at com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.runContributingProcs(JavacProcessingEnvironment.java:644) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1027) at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1185) at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1108) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824) at com.sun.tools.javac.main.Main.compile(Main.java:439) ... 25 more Caused by: java.lang.NullPointerException at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutputFileName(TagHandlerClassGenerator.java:87) at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutput(TagHandlerClassGenerator.java:80) at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.process(TagHandlerClassGenerator.java:60) at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.generateTagHandler(TagHandlerGeneratorVisitor.java:74) at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:49) at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:39) at org.richfaces.cdk.model.ComponentModel.accept(ComponentModel.java:45) at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:211) at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:206) at org.richfaces.cdk.model.ComponentLibrary.accept(ComponentLibrary.java:95) ... 43 more [ERROR]}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Mon Apr 28 17:36:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Mon, 28 Apr 2014 17:36:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13618) Create a Bootstrap skin for the RichFaces 4.x set of components In-Reply-To: References: Message-ID: Brian Leathem created RF-13618: ---------------------------------- Summary: Create a Bootstrap skin for the RichFaces 4.x set of components Key: RF-13618 URL: https://issues.jboss.org/browse/RF-13618 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 03:12:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 29 Apr 2014 03:12:33 -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 ] Juraj H?ska updated RF-13602: ----------------------------- Labels: ie11 (was: ie11 waiting_on_user) > 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 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 03:38:34 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 29 Apr 2014 03:38:34 -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 ] Juraj H?ska updated RF-13602: ----------------------------- Attachment: ie11-1.png ie11-2.png ie11-3.png I have give it a second spin and I can not still reproduce it. In the attachments you can find screenshots from my endeavor. Particularly on {{ie11-2.png}} the {{rich:fileUpload}} is enabled for me. [~wdmmza] Have you please cleared the browser cache before testing this ? > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 03:38:34 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 29 Apr 2014 03:38:34 -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:comment-tabpanel&focusedCommentId=12964274#comment-12964274 ] Juraj H?ska edited comment on RF-13602 at 4/29/14 3:37 AM: ----------------------------------------------------------- I have gave it a second spin and I can not still reproduce it. In the attachments you can find screenshots from my endeavor. Particularly on {{ie11-2.png}} the {{rich:fileUpload}} is enabled for me. [~wdmmza] Have you please cleared the browser cache before testing this ? was (Author: jhuska): I have give it a second spin and I can not still reproduce it. In the attachments you can find screenshots from my endeavor. Particularly on {{ie11-2.png}} the {{rich:fileUpload}} is enabled for me. [~wdmmza] Have you please cleared the browser cache before testing this ? > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 03:44:33 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 29 Apr 2014 03:44:33 -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:comment-tabpanel&focusedCommentId=12964274#comment-12964274 ] Juraj H?ska edited comment on RF-13602 at 4/29/14 3:43 AM: ----------------------------------------------------------- I have gave it a second spin, and I can not still reproduce it. In the attachments you can find screenshots from my endeavor. Particularly in {{ie11-2.png}}, the {{rich:fileUpload}} is enabled for me. [~wdmmza] Have you please cleared the browser cache before testing this ? Because otherwise it would be environment specific. My server is running on: java version "1.7.0_55" OpenJDK Runtime Environment (fedora-2.4.7.0.fc20-x86_64 u55-b13) OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) Client: Win 7 + IE11 with a slightly higher maintenance version. was (Author: jhuska): I have gave it a second spin and I can not still reproduce it. In the attachments you can find screenshots from my endeavor. Particularly on {{ie11-2.png}} the {{rich:fileUpload}} is enabled for me. [~wdmmza] Have you please cleared the browser cache before testing this ? > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 03:44:34 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 29 Apr 2014 03:44:34 -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:comment-tabpanel&focusedCommentId=12964274#comment-12964274 ] Juraj H?ska edited comment on RF-13602 at 4/29/14 3:44 AM: ----------------------------------------------------------- I have gave it a second spin, and I can not still reproduce it. In the attachments you can find screenshots from my endeavor. Particularly in {{ie11-2.png}}, the {{rich:fileUpload}} is enabled for me. [~wdmmza] Have you please cleared the browser cache before testing this ? Because otherwise it would be environment specific. My *server* is running on: java version "1.7.0_55" OpenJDK Runtime Environment (fedora-2.4.7.0.fc20-x86_64 u55-b13) OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) *Client*: Win 7 + IE11 with a slightly higher maintenance version. was (Author: jhuska): I have gave it a second spin, and I can not still reproduce it. In the attachments you can find screenshots from my endeavor. Particularly in {{ie11-2.png}}, the {{rich:fileUpload}} is enabled for me. [~wdmmza] Have you please cleared the browser cache before testing this ? Because otherwise it would be environment specific. My server is running on: java version "1.7.0_55" OpenJDK Runtime Environment (fedora-2.4.7.0.fc20-x86_64 u55-b13) OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) Client: Win 7 + IE11 with a slightly higher maintenance version. > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 03:46:34 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Tue, 29 Apr 2014 03:46:34 -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 ] Juraj H?ska updated RF-13602: ----------------------------- Labels: ie11 waiting_on_user (was: ie11) > 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, waiting_on_user > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 04:56:33 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 29 Apr 2014 04:56:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-13616: ------------------------------- Affects Version/s: 4.3.6 > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final, 4.3.6 > Reporter: abhishek vijra > Assignee: Pavol Pitonak > Attachments: popupPanel.zip > > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 05:04:33 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 29 Apr 2014 05:04:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964291#comment-12964291 ] Pavol Pitonak commented on RF-13616: ------------------------------------ Reproduced in 4.3.6. > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final, 4.3.6 > Reporter: abhishek vijra > Assignee: Pavol Pitonak > Attachments: popupPanel.zip > > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 05:04:33 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 29 Apr 2014 05:04:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavol Pitonak updated RF-13616: ------------------------------- Assignee: (was: Pavol Pitonak) > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final, 4.3.6 > Reporter: abhishek vijra > Attachments: popupPanel.zip > > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 05:24:33 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 29 Apr 2014 05:24:33 -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 ] Pavol Pitonak updated RF-13615: ------------------------------- Attachment: edt.png > 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: Pavol Pitonak > Attachments: edt.png > > > 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 05:26:33 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 29 Apr 2014 05:26:33 -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=12964293#comment-12964293 ] Pavol Pitonak commented on RF-13615: ------------------------------------ [~wlh], a4j:log works fine in Firefox 28 for me. [~bleathem], I could reproduce this behavior in 4.3.5 and 4.3.6. [~wlh] is right that the behavior changed in 4.3.5. In 4.3.4 only one request is sent but the last column in extended data table is rendered wrong. !edt.png|thumbnail! > 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: Pavol Pitonak > Attachments: edt.png > > > 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 05:26:34 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Tue, 29 Apr 2014 05:26:34 -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 ] Pavol Pitonak updated RF-13615: ------------------------------- Assignee: (was: Pavol Pitonak) > 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 > Attachments: edt.png > > > 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 07:46:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 29 Apr 2014 07:46:34 -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=12964375#comment-12964375 ] Michal Petrov commented on RF-13615: ------------------------------------ The column-resizing issue was RF-13287, my solution does indeed use {{setColumnWidth}}, causing the second request. > 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 > Attachments: edt.png > > > 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 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 09:48:33 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Tue, 29 Apr 2014 09:48:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13617) CDK - NPE getOutputFileName In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964429#comment-12964429 ] Michal Petrov commented on RF-13617: ------------------------------------ [~lukindo], the issue is in AbstractChart, you've got: bq. tag = @Tag(type = TagType.Facelets, *generate = true*) this causes the CDK to try generating a handler class but since no handler is defined it throws the NPE. It builds fine without it (there's one checkstyle error in ChartRendererBase) but I don't know if there's supposed to be a handler or not. > CDK - NPE getOutputFileName > --------------------------- > > Key: RF-13617 > URL: https://issues.jboss.org/browse/RF-13617 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Macko > Priority: Blocker > > During backporting chart to 4.5.X I come across this exception. In RF5 CDK works ok. > {{[ERROR] Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException: NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at com.sun.tools.javac.main.Main.compile(Main.java:469) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:132) > at org.richfaces.cdk.apt.AptBuilder.build(AptBuilder.java:47) > at org.richfaces.cdk.Generator.execute(Generator.java:155) > at org.richfaces.builder.mojo.GenerateMojo.execute(GenerateMojo.java:254) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > ... 20 more > Caused by: java.lang.reflect.InvocationTargetException > 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.richfaces.cdk.apt.LibraryProxyInterceptor.invoke(LibraryProxyInterceptor.java:18) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerWriter.render(TagHandlerWriter.java:48) > at org.richfaces.cdk.apt.DefaultLibraryGenerator.generate(DefaultLibraryGenerator.java:28) > at org.richfaces.cdk.apt.CdkProcessorImpl.generate(CdkProcessorImpl.java:157) > at org.richfaces.cdk.apt.CdkProcessorImpl.continueAfterJavaSourceProcessing(CdkProcessorImpl.java:133) > at org.richfaces.cdk.apt.CdkProcessorImpl.process(CdkProcessorImpl.java:106) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$200(JavacProcessingEnvironment.java:97) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.runContributingProcs(JavacProcessingEnvironment.java:644) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1027) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1185) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1108) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824) > at com.sun.tools.javac.main.Main.compile(Main.java:439) > ... 25 more > Caused by: java.lang.NullPointerException > at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutputFileName(TagHandlerClassGenerator.java:87) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutput(TagHandlerClassGenerator.java:80) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.process(TagHandlerClassGenerator.java:60) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.generateTagHandler(TagHandlerGeneratorVisitor.java:74) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:49) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:39) > at org.richfaces.cdk.model.ComponentModel.accept(ComponentModel.java:45) > at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:211) > at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:206) > at org.richfaces.cdk.model.ComponentLibrary.accept(ComponentLibrary.java:95) > ... 43 more > [ERROR]}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 10:14:34 2014 From: issues at jboss.org (Wang Liyu (JIRA)) Date: Tue, 29 Apr 2014 10:14:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13619) RichFaces.javascriptServiceComplete(); is not called on normal GET/POST request In-Reply-To: References: Message-ID: Wang Liyu created RF-13619: ------------------------------ Summary: RichFaces.javascriptServiceComplete(); is not called on normal GET/POST request Key: RF-13619 URL: https://issues.jboss.org/browse/RF-13619 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: base functionality Affects Versions: 4.3.6 Environment: Richfaces 4.3.6.Final, Tomcat 7.0.53, JSF 2.1.27, Java7u55 Reporter: Wang Liyu In AJAX Response Richfaces added RichFaces.javascriptServiceComplete(); at the end of the response, the default implementation is fire a event, so if I have $.ready() want to do something on delay-constructed Richfaces Objects, this would be the place, I can call $.one('javascriptServiceComplete', functionname); But if the same page is called with GET/POST method (normal requestion), it won't call this method, is there any reason why is that? Here is the discussion on the forum: https://community.jboss.org/thread/240501 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:52:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:52:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11417) Tab: investigate why @action does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11417: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Tab: investigate why @action does not work > ------------------------------------------ > > Key: RF-11417 > URL: https://issues.jboss.org/browse/RF-11417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Fix For: 4.3.7 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Determine why rich:tab @action has not been implemented. > Verify that its implementation can't affect current applications (and try to find possible workaround). > Implement @action and @actionListener. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:52:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:52:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11427) rich:tab - actionListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11427: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > rich:tab - actionListener > ------------------------- > > Key: RF-11427 > URL: https://issues.jboss.org/browse/RF-11427 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1 > Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d > Metamer 4.1.0-SNAPSHOT r.22728 > Mojarra 2.1.2-FCS > Apache Tomcat 7.0.16 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 18.0.1025.168 @ Linux i686 > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: ci_issue, patch_proposed > Fix For: 4.3.7 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > It seems that the actionListener attribute doesn't work. > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # open tab2 > # open tab1 (action and action listener are invoked) > # open tab2 > # open tab1 (action and action listener are *NOT* invoked) > # open tab1 (action and action listener are invoked) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:52:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:52:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13506) Incorrect information on showcase fileUpload sample page (maxRequestSize description) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13506: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Incorrect information on showcase fileUpload sample page (maxRequestSize description) > ------------------------------------------------------------------------------------- > > Key: RF-13506 > URL: https://issues.jboss.org/browse/RF-13506 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input, examples, showcase > Affects Versions: 4.3.4 > Reporter: Vasil Lukach > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload page contains incorrect information: > "maxRequestSize attribute defines max size in bytes of the uploaded files (1000000 for this example)". > But based on "This example allows you to upload up to 5 files. The file extension is limited to GIF, JPG, BMP, PNG and the maximum size of each file must not exceed 100kB" number 1000000 should be changed to 102400. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:52:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:52:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13478) VDL documentation typos In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13478: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > VDL documentation typos > ----------------------- > > Key: RF-13478 > URL: https://issues.jboss.org/browse/RF-13478 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.3, 4.3.4 > Reporter: Vasil Lukach > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces VDL documentation typos: > 1) rich:fileUpload > - uploadLabel attribute : Add -> Upload > - execute attribute (proposal): remove "Some components make use of additional keywords" > 2) a4j:mediaOutput > element attribute: imj -> img > 3) accordion: epand -> expand -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:52:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:52:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13512) Photoalbum: port fix from RF-13498 to RF4 photoalbum In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13512: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Photoalbum: port fix from RF-13498 to RF4 photoalbum > ---------------------------------------------------- > > Key: RF-13512 > URL: https://issues.jboss.org/browse/RF-13512 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Ji?? ?tefek > Labels: photoalbum > Fix For: 4.3.7 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:52:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:52:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13564) rich:pickList shows an outline when clicked In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13564: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > rich:pickList shows an outline when clicked > ------------------------------------------- > > Key: RF-13564 > URL: https://issues.jboss.org/browse/RF-13564 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Hi all, i use rich:pickList and i was amazing. If we press left button on a mouse(don't release left button) on rich:pickList we'll see rectangle. You can check it [here|http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=pickList&skin=blueSky]. > I found a solution: > in file template "picklist.template.xml" > {code} > ... >
cdk:passThrough="onclick:onclick ondblclick:ondblclick onmousedown:onmousedown onmouseup:onmouseup onmouseover:onmouseover > onmousemove:onmousemove onmouseout:onmouseout onkeypress:onkeypress onkeydown:onkeydown onkeyup:onkeyup"> > ... > {code} > used tabindex attribue for DIV. > Why? > DIV elements are not compatible with tabindex ([see the HTML 4.01 spec|http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex]). > I can create pull request :). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13569) Photoalbum: the change of users avatar doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13569: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Photoalbum: the change of users avatar doesn't work > --------------------------------------------------- > > Key: RF-13569 > URL: https://issues.jboss.org/browse/RF-13569 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.7 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # After the user's avatar is changed, the avatar is not updated in comments or search results (already resolved by https://github.com/richfaces4/dev-examples/commit/942575579f4e80c2d8dac5c3e1e57f8e706ee0cc) > # the avatar is not updated in the users profile after a second change of the avatar (but is updated in search result and in comments) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:36 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13592: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Priority: Critical > Labels: gss > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:36 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13598: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.7 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > See the https://community.jboss.org/thread/239391 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:37 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:37 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11417) Tab: investigate why @action does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11417: ------------------------------- Sprint: 4.3.7 Sprint 1 > Tab: investigate why @action does not work > ------------------------------------------ > > Key: RF-11417 > URL: https://issues.jboss.org/browse/RF-11417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Fix For: 4.3.7 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Determine why rich:tab @action has not been implemented. > Verify that its implementation can't affect current applications (and try to find possible workaround). > Implement @action and @actionListener. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11427) rich:tab - actionListener In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-11427: ------------------------------- Sprint: 4.3.7 Sprint 1 > rich:tab - actionListener > ------------------------- > > Key: RF-11427 > URL: https://issues.jboss.org/browse/RF-11427 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.Final, 4.1.0.Milestone2, 4.2.3.CR1 > Environment: RichFaces 4.1.0-SNAPSHOT r.5debbf8981de1839984bdaa38b31f58ed028239d > Metamer 4.1.0-SNAPSHOT r.22728 > Mojarra 2.1.2-FCS > Apache Tomcat 7.0.16 > OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux > Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 > RichFaces 4.2.1-SNAPSHOT > Metamer 4.2.1-SNAPSHOT > Mojarra 2.1.7-jbossorg-1 > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 18.0.1025.168 @ Linux i686 > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: ci_issue, patch_proposed > Fix For: 4.3.7 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > It seems that the actionListener attribute doesn't work. > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # open tab2 > # open tab1 (action and action listener are invoked) > # open tab2 > # open tab1 (action and action listener are *NOT* invoked) > # open tab1 (action and action listener are invoked) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.26 in RichFaces 4 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13364: ------------------------------- Sprint: 4.3.5 Sprint 1, 4.3.7 Sprint 1 (was: 4.3.5 Sprint 1) > Upgrade Mojarra to 2.1.26 in RichFaces 4 > ---------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13506) Incorrect information on showcase fileUpload sample page (maxRequestSize description) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13506: ------------------------------- Sprint: 4.3.7 Sprint 1 > Incorrect information on showcase fileUpload sample page (maxRequestSize description) > ------------------------------------------------------------------------------------- > > Key: RF-13506 > URL: https://issues.jboss.org/browse/RF-13506 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input, examples, showcase > Affects Versions: 4.3.4 > Reporter: Vasil Lukach > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload page contains incorrect information: > "maxRequestSize attribute defines max size in bytes of the uploaded files (1000000 for this example)". > But based on "This example allows you to upload up to 5 files. The file extension is limited to GIF, JPG, BMP, PNG and the maximum size of each file must not exceed 100kB" number 1000000 should be changed to 102400. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:38 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:38 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13478) VDL documentation typos In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13478: ------------------------------- Sprint: 4.3.7 Sprint 1 > VDL documentation typos > ----------------------- > > Key: RF-13478 > URL: https://issues.jboss.org/browse/RF-13478 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.3, 4.3.4 > Reporter: Vasil Lukach > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces VDL documentation typos: > 1) rich:fileUpload > - uploadLabel attribute : Add -> Upload > - execute attribute (proposal): remove "Some components make use of additional keywords" > 2) a4j:mediaOutput > element attribute: imj -> img > 3) accordion: epand -> expand -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13512) Photoalbum: port fix from RF-13498 to RF4 photoalbum In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13512: ------------------------------- Sprint: 4.3.7 Sprint 1 > Photoalbum: port fix from RF-13498 to RF4 photoalbum > ---------------------------------------------------- > > Key: RF-13512 > URL: https://issues.jboss.org/browse/RF-13512 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Ji?? ?tefek > Labels: photoalbum > Fix For: 4.3.7 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13564) rich:pickList shows an outline when clicked In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13564: ------------------------------- Sprint: 4.3.7 Sprint 1 > rich:pickList shows an outline when clicked > ------------------------------------------- > > Key: RF-13564 > URL: https://issues.jboss.org/browse/RF-13564 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Hi all, i use rich:pickList and i was amazing. If we press left button on a mouse(don't release left button) on rich:pickList we'll see rectangle. You can check it [here|http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=pickList&skin=blueSky]. > I found a solution: > in file template "picklist.template.xml" > {code} > ... >
cdk:passThrough="onclick:onclick ondblclick:ondblclick onmousedown:onmousedown onmouseup:onmouseup onmouseover:onmouseover > onmousemove:onmousemove onmouseout:onmouseout onkeypress:onkeypress onkeydown:onkeydown onkeyup:onkeyup"> > ... > {code} > used tabindex attribue for DIV. > Why? > DIV elements are not compatible with tabindex ([see the HTML 4.01 spec|http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex]). > I can create pull request :). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:39 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:39 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13569) Photoalbum: the change of users avatar doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13569: ------------------------------- Sprint: 4.3.7 Sprint 1 > Photoalbum: the change of users avatar doesn't work > --------------------------------------------------- > > Key: RF-13569 > URL: https://issues.jboss.org/browse/RF-13569 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.7 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # After the user's avatar is changed, the avatar is not updated in comments or search results (already resolved by https://github.com/richfaces4/dev-examples/commit/942575579f4e80c2d8dac5c3e1e57f8e706ee0cc) > # the avatar is not updated in the users profile after a second change of the avatar (but is updated in search result and in comments) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:40 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:40 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13592: ------------------------------- Sprint: 4.3.7 Sprint 2 > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Priority: Critical > Labels: gss > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:40 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:40 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13598: ------------------------------- Sprint: 4.3.7 Sprint 2 > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.7 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > See the https://community.jboss.org/thread/239391 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:40 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:40 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13478) VDL documentation typos In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13478: ---------------------------------- Assignee: Brian Leathem > VDL documentation typos > ----------------------- > > Key: RF-13478 > URL: https://issues.jboss.org/browse/RF-13478 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.3, 4.3.4 > Reporter: Vasil Lukach > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces VDL documentation typos: > 1) rich:fileUpload > - uploadLabel attribute : Add -> Upload > - execute attribute (proposal): remove "Some components make use of additional keywords" > 2) a4j:mediaOutput > element attribute: imj -> img > 3) accordion: epand -> expand -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:40 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:40 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13506) Incorrect information on showcase fileUpload sample page (maxRequestSize description) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13506: ---------------------------------- Assignee: Brian Leathem > Incorrect information on showcase fileUpload sample page (maxRequestSize description) > ------------------------------------------------------------------------------------- > > Key: RF-13506 > URL: https://issues.jboss.org/browse/RF-13506 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input, examples, showcase > Affects Versions: 4.3.4 > Reporter: Vasil Lukach > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload page contains incorrect information: > "maxRequestSize attribute defines max size in bytes of the uploaded files (1000000 for this example)". > But based on "This example allows you to upload up to 5 files. The file extension is limited to GIF, JPG, BMP, PNG and the maximum size of each file must not exceed 100kB" number 1000000 should be changed to 102400. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:54:40 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:54:40 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13512) Photoalbum: port fix from RF-13498 to RF4 photoalbum In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13512: ---------------------------------- Assignee: Michal Petrov > Photoalbum: port fix from RF-13498 to RF4 photoalbum > ---------------------------------------------------- > > Key: RF-13512 > URL: https://issues.jboss.org/browse/RF-13512 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.7 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:56:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:56:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13564) rich:pickList shows an outline when clicked In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-13564: ---------------------------------- Assignee: Brian Leathem > rich:pickList shows an outline when clicked > ------------------------------------------- > > Key: RF-13564 > URL: https://issues.jboss.org/browse/RF-13564 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Hi all, i use rich:pickList and i was amazing. If we press left button on a mouse(don't release left button) on rich:pickList we'll see rectangle. You can check it [here|http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=pickList&skin=blueSky]. > I found a solution: > in file template "picklist.template.xml" > {code} > ... >
cdk:passThrough="onclick:onclick ondblclick:ondblclick onmousedown:onmousedown onmouseup:onmouseup onmouseover:onmouseover > onmousemove:onmousemove onmouseout:onmouseout onkeypress:onkeypress onkeydown:onkeydown onkeyup:onkeyup"> > ... > {code} > used tabindex attribue for DIV. > Why? > DIV elements are not compatible with tabindex ([see the HTML 4.01 spec|http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex]). > I can create pull request :). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 11:56:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 11:56:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-11417) Tab: investigate why @action does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reassigned RF-11417: ---------------------------------- Assignee: Brian Leathem > Tab: investigate why @action does not work > ------------------------------------------ > > Key: RF-11417 > URL: https://issues.jboss.org/browse/RF-11417 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.1.0.CR1 > Reporter: Luk?? Fry? > Assignee: Brian Leathem > Fix For: 4.3.7 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Determine why rich:tab @action has not been implemented. > Verify that its implementation can't affect current applications (and try to find possible workaround). > Implement @action and @actionListener. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 12:34:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 12:34:33 -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: Brian Leathem created RF-13620: ---------------------------------- Summary: 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 Fix For: 4.5.0.Alpha3 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 13:08:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 13:08:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13478) VDL documentation typos In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13478: ------------------------------- Description: RichFaces VDL documentation typos: # rich:fileUpload #- uploadLabel attribute : Add -> Upload #- execute attribute (proposal): remove "Some components make use of additional keywords" # a4j:mediaOutput #- element attribute: imj -> img # rich:accordion #- epand -> expand was: RichFaces VDL documentation typos: 1) rich:fileUpload - uploadLabel attribute : Add -> Upload - execute attribute (proposal): remove "Some components make use of additional keywords" 2) a4j:mediaOutput element attribute: imj -> img 3) accordion: epand -> expand > VDL documentation typos > ----------------------- > > Key: RF-13478 > URL: https://issues.jboss.org/browse/RF-13478 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.3, 4.3.4 > Reporter: Vasil Lukach > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces VDL documentation typos: > # rich:fileUpload > #- uploadLabel attribute : Add -> Upload > #- execute attribute (proposal): remove "Some components make use of additional keywords" > # a4j:mediaOutput > #- element attribute: imj -> img > # rich:accordion > #- epand -> expand -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 13:12:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 13:12:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13478) VDL documentation typos In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13478. -------------------------------- Resolution: Done All updated execpet the _execute_ attribute. It is defined centrally, and there is insufficient benefit to "forking" the description for the fileUpload component at this point. > VDL documentation typos > ----------------------- > > Key: RF-13478 > URL: https://issues.jboss.org/browse/RF-13478 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.3, 4.3.4 > Reporter: Vasil Lukach > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces VDL documentation typos: > # rich:fileUpload > #- uploadLabel attribute : Add -> Upload > #- execute attribute (proposal): remove "Some components make use of additional keywords" > # a4j:mediaOutput > #- element attribute: imj -> img > # rich:accordion > #- epand -> expand -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 13:26:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 13:26:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13506) Incorrect information on showcase fileUpload sample page (maxRequestSize description) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964503#comment-12964503 ] Brian Leathem commented on RF-13506: ------------------------------------ The _org.richfaces.fileUpload.maxRequestSize_ context parameter takes it's value in bytes, and it is set to 100,000 bytes. The value in the text incorrectly says it's incroeectly set to 1,000,000 bytes. I will change this to 100,000. I will however leave the 100kB in the text, as that is generally accepted practice when discussing storage size (see this [wikipedia article|http://en.wikipedia.org/wiki/Kilobyte] for details). > Incorrect information on showcase fileUpload sample page (maxRequestSize description) > ------------------------------------------------------------------------------------- > > Key: RF-13506 > URL: https://issues.jboss.org/browse/RF-13506 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input, examples, showcase > Affects Versions: 4.3.4 > Reporter: Vasil Lukach > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload page contains incorrect information: > "maxRequestSize attribute defines max size in bytes of the uploaded files (1000000 for this example)". > But based on "This example allows you to upload up to 5 files. The file extension is limited to GIF, JPG, BMP, PNG and the maximum size of each file must not exceed 100kB" number 1000000 should be changed to 102400. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 13:28:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 13:28:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13506) Incorrect information on showcase fileUpload sample page (maxRequestSize description) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13506. -------------------------------- Resolution: Done > Incorrect information on showcase fileUpload sample page (maxRequestSize description) > ------------------------------------------------------------------------------------- > > Key: RF-13506 > URL: https://issues.jboss.org/browse/RF-13506 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input, examples, showcase > Affects Versions: 4.3.4 > Reporter: Vasil Lukach > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload page contains incorrect information: > "maxRequestSize attribute defines max size in bytes of the uploaded files (1000000 for this example)". > But based on "This example allows you to upload up to 5 files. The file extension is limited to GIF, JPG, BMP, PNG and the maximum size of each file must not exceed 100kB" number 1000000 should be changed to 102400. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 13:38:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 13:38:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13564) rich:pickList shows an outline when clicked In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13564. -------------------------------- Resolution: Done > rich:pickList shows an outline when clicked > ------------------------------------------- > > Key: RF-13564 > URL: https://issues.jboss.org/browse/RF-13564 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 4.3.5 > Reporter: alexey plotnikov > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Hi all, i use rich:pickList and i was amazing. If we press left button on a mouse(don't release left button) on rich:pickList we'll see rectangle. You can check it [here|http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=pickList&skin=blueSky]. > I found a solution: > in file template "picklist.template.xml" > {code} > ... >
cdk:passThrough="onclick:onclick ondblclick:ondblclick onmousedown:onmousedown onmouseup:onmouseup onmouseover:onmouseover > onmousemove:onmousemove onmouseout:onmouseout onkeypress:onkeypress onkeydown:onkeydown onkeyup:onkeyup"> > ... > {code} > used tabindex attribue for DIV. > Why? > DIV elements are not compatible with tabindex ([see the HTML 4.01 spec|http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex]). > I can create pull request :). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 13:44:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 13:44:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.28 in RichFaces 4.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13364: ------------------------------- Summary: Upgrade Mojarra to 2.1.28 in RichFaces 4.3.x (was: Upgrade Mojarra to 2.1.26 in RichFaces 4) > Upgrade Mojarra to 2.1.28 in RichFaces 4.3.x > -------------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 14:10:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 14:10:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.28 in RichFaces 4.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13364. -------------------------------- Labels: needs-code-review (was: ) Resolution: Done > Upgrade Mojarra to 2.1.28 in RichFaces 4.3.x > -------------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-code-review > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 14:10:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 14:10:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13364) Upgrade Mojarra to 2.1.28 in RichFaces 4.3.x In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13364: ------------------------------- Labels: needs-qe (was: needs-code-review) > Upgrade Mojarra to 2.1.28 in RichFaces 4.3.x > -------------------------------------------- > > Key: RF-13364 > URL: https://issues.jboss.org/browse/RF-13364 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.4 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.3.7 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > RichFaces 4 [1] now depends on Mojarra 2.1.19 (bundled in EAP 6.1.1). Upgrade it to the lastest version 2.1.26. > [1] https://github.com/richfaces4/build/blob/master/bom/pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 18:40:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 18:40:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964559#comment-12964559 ] Brian Leathem commented on RF-13592: ------------------------------------ The issue is that the _lastMessageNumber_ in the _RichFaces.Push_ closure is set on page load, and is not reset on ajax load. After ajax render the _message.number_ is compared to the _lastMessageNumber_, and the message is ignored if the number is too small. This can be seen in the attached sample as follows: 1) load the page 2) enable push 3) click send message X times 4) disable push 5) enable push 4) push send message X+1 times The message will not be displayed until the X+1st click. Resolution will involve resetting the _lastMessageNumber_ when the push component is destroyed. > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Priority: Critical > Labels: gss > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 19:40:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 19:40:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13592. -------------------------------- Labels: gss needs-qe (was: gss) Assignee: Brian Leathem Resolution: Done I rest the _lastMessageNumber_ when the RichFaces.Push#disconnect function is invoked. The resolves the problem in Chrome and Firefox (other browsers will bec verified by QE). QE: please also verify the correct behaviour when multiple push components are present on a page, and they are selectively re-rendered. > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Brian Leathem > Priority: Critical > Labels: gss, needs-qe > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 19:40:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 19:40:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964567#comment-12964567 ] Brian Leathem edited comment on RF-13592 at 4/29/14 7:40 PM: ------------------------------------------------------------- I reset the _lastMessageNumber_ when the RichFaces.Push#disconnect function is invoked. The resolves the problem in Chrome and Firefox (other browsers will bec verified by QE). QE: please also verify the correct behaviour when multiple push components are present on a page, and they are selectively re-rendered. was (Author: bleathem): I rest the _lastMessageNumber_ when the RichFaces.Push#disconnect function is invoked. The resolves the problem in Chrome and Firefox (other browsers will bec verified by QE). QE: please also verify the correct behaviour when multiple push components are present on a page, and they are selectively re-rendered. > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Brian Leathem > Priority: Critical > Labels: gss, needs-qe > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Tue Apr 29 19:44:33 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Tue, 29 Apr 2014 19:44:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964568#comment-12964568 ] Brian Leathem commented on RF-13598: ------------------------------------ [~ppitonak] please share your re-producing code. Also, given that this was caused by a mojarra change, it would be useful to try and reproduce this with Vanilla JSF (as requested in the forum thread). Finally, please confirm which browsers this affects. > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.7 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > See the https://community.jboss.org/thread/239391 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 02:38:34 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 02:38:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-13592: -------------------------------- > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Brian Leathem > Priority: Critical > Labels: gss, needs-qe > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 02:38:35 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 02:38:35 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13592: ------------------------------- Sprint: 4.3.7 Sprint 1 (was: 4.3.7 Sprint 2) > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Brian Leathem > Priority: Critical > Labels: gss, needs-qe > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 02:38:36 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 02:38:36 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13592. -------------------------------- Resolution: Done > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Brian Leathem > Priority: Critical > Labels: gss, needs-qe > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 03:16:34 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 30 Apr 2014 03:16:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13512) Photoalbum: port fix from RF-13498 to RF4 photoalbum In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13512. -------------------------------- Resolution: Done > Photoalbum: port fix from RF-13498 to RF4 photoalbum > ---------------------------------------------------- > > Key: RF-13512 > URL: https://issues.jboss.org/browse/RF-13512 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.7 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 04:04:33 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Wed, 30 Apr 2014 04:04:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13621) IE11 Changes DOM structure on JSF rerender In-Reply-To: References: Message-ID: Robert Becker created RF-13621: ---------------------------------- Summary: IE11 Changes DOM structure on JSF rerender Key: RF-13621 URL: https://issues.jboss.org/browse/RF-13621 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: base functionality Affects Versions: 3.3.4.Final Reporter: Robert Becker When rerendering regions with multiple child elements, IE11 breaks the DOM by nesting the former siblings. I tried changing sarrissa as described in this issue: https://issues.jboss.org/browse/RF-13443 But it does not seem related or helping. This stackoverflow question describes the issue perfectly: http://stackoverflow.com/questions/22015352/ie11-changes-dom-structure-on-jsf-rerender I'll attach a screenshot where this problem leads to multiple pagination controls, as the old dom elements reside instead of being replaced when rerendering. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 04:08:33 2014 From: issues at jboss.org (Robert Becker (JIRA)) Date: Wed, 30 Apr 2014 04:08:33 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13621) IE11 Changes DOM structure on JSF rerender In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Becker updated RF-13621: ------------------------------- Description: When rerendering regions with multiple child elements, IE11 breaks the DOM by nesting the former siblings. I tried changing sarrissa as described in this issue: https://issues.jboss.org/browse/RF-13443 But it does not seem related or helping. This stackoverflow question describes the issue perfectly: http://stackoverflow.com/questions/22015352/ie11-changes-dom-structure-on-jsf-rerender Here is a screenshot where this problem leads to multiple pagination controls, as the old dom elements reside instead of being replaced when rerendering: https://dl.dropboxusercontent.com/u/18449425/permanent/richfaces%20ie11%20a4j%20rerender.png was: When rerendering regions with multiple child elements, IE11 breaks the DOM by nesting the former siblings. I tried changing sarrissa as described in this issue: https://issues.jboss.org/browse/RF-13443 But it does not seem related or helping. This stackoverflow question describes the issue perfectly: http://stackoverflow.com/questions/22015352/ie11-changes-dom-structure-on-jsf-rerender I'll attach a screenshot where this problem leads to multiple pagination controls, as the old dom elements reside instead of being replaced when rerendering. > IE11 Changes DOM structure on JSF rerender > ------------------------------------------ > > Key: RF-13621 > URL: https://issues.jboss.org/browse/RF-13621 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 3.3.4.Final > Reporter: Robert Becker > > When rerendering regions with multiple child elements, IE11 breaks the DOM by nesting the former siblings. > I tried changing sarrissa as described in this issue: https://issues.jboss.org/browse/RF-13443 > But it does not seem related or helping. > This stackoverflow question describes the issue perfectly: > http://stackoverflow.com/questions/22015352/ie11-changes-dom-structure-on-jsf-rerender > Here is a screenshot where this problem leads to multiple pagination controls, as the old dom elements reside instead of being replaced when rerendering: https://dl.dropboxusercontent.com/u/18449425/permanent/richfaces%20ie11%20a4j%20rerender.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 05:26:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 30 Apr 2014 05:26:33 -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:comment-tabpanel&focusedCommentId=12964626#comment-12964626 ] Luk?? Fry? commented on RF-13505: --------------------------------- [~bleathem] no, it still resides in the [branch|https://github.com/richfaces/richfaces/tree/RF-13505-refactor-epvc-3]. I'm currently determining what's the status - whether we have good conditions to merge it. > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 05:40:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 30 Apr 2014 05:40:33 -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:comment-tabpanel&focusedCommentId=12964629#comment-12964629 ] Luk?? Fry? commented on RF-13505: --------------------------------- For the current status: *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 05:40:34 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 30 Apr 2014 05:40:34 -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:comment-tabpanel&focusedCommentId=12964629#comment-12964629 ] Luk?? Fry? edited comment on RF-13505 at 4/30/14 5:40 AM: ---------------------------------------------------------- For the current status: *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x was (Author: lfryc): For the current status: *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually Suggested action items: * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 05:40:34 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 30 Apr 2014 05:40:34 -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:comment-tabpanel&focusedCommentId=12964629#comment-12964629 ] Luk?? Fry? edited comment on RF-13505 at 4/30/14 5:40 AM: ---------------------------------------------------------- For the current status: *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually Suggested action items: * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x was (Author: lfryc): For the current status: *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 05:44:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 30 Apr 2014 05:44:33 -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:comment-tabpanel&focusedCommentId=12964629#comment-12964629 ] Luk?? Fry? edited comment on RF-13505 at 4/30/14 5:43 AM: ---------------------------------------------------------- For the current status: *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * look at [the issue Juraj identified|https://issues.jboss.org/browse/RF-13505?focusedCommentId=12953945&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12953945] * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x was (Author: lfryc): For the current status: *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 05:48:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 30 Apr 2014 05:48:33 -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:comment-tabpanel&focusedCommentId=12964629#comment-12964629 ] Luk?? Fry? edited comment on RF-13505 at 4/30/14 5:47 AM: ---------------------------------------------------------- For the current status: *Benefits of the patch* * addresses a compatibility with other third-party libraries and custom wrappers ** OmniFaces, PrimeFaces * makes the implementation future-proof ** by delegating as much tasks as possible to JSF impl *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * look at [the issue Juraj identified|https://issues.jboss.org/browse/RF-13505?focusedCommentId=12953945&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12953945] * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x was (Author: lfryc): For the current status: *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * look at [the issue Juraj identified|https://issues.jboss.org/browse/RF-13505?focusedCommentId=12953945&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12953945] * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 05:50:33 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 30 Apr 2014 05:50:33 -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:comment-tabpanel&focusedCommentId=12964629#comment-12964629 ] Luk?? Fry? edited comment on RF-13505 at 4/30/14 5:49 AM: ---------------------------------------------------------- For the current status: *Benefits of the patch* * addresses a compatibility with other third-party libraries and custom wrappers ** OmniFaces, PrimeFaces * makes the implementation future-proof ** by delegating as much tasks as possible to JSF impl In general, this patch should make sure we tackle with interoperability issues (both, already identified and future ones) *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * look at [the issue Juraj identified|https://issues.jboss.org/browse/RF-13505?focusedCommentId=12953945&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12953945] * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x was (Author: lfryc): For the current status: *Benefits of the patch* * addresses a compatibility with other third-party libraries and custom wrappers ** OmniFaces, PrimeFaces * makes the implementation future-proof ** by delegating as much tasks as possible to JSF impl *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * look at [the issue Juraj identified|https://issues.jboss.org/browse/RF-13505?focusedCommentId=12953945&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12953945] * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 08:26:34 2014 From: issues at jboss.org (David Baddeley (JIRA)) Date: Wed, 30 Apr 2014 08:26:34 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13443) Rerender after Ajax Request in Internet Explorer 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964660#comment-12964660 ] David Baddeley commented on RF-13443: ------------------------------------- Does this definitely work? I tried overriding AJAX.js with the line above but now the a4j:jsFunction never finishes the AJAX request (oncomplete doesn't fire) > Rerender after Ajax Request in Internet Explorer 11 > --------------------------------------------------- > > Key: RF-13443 > URL: https://issues.jboss.org/browse/RF-13443 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 3.3.4.Final > Reporter: Osman Y?ksel > Priority: Critical > Fix For: 3.Future > > > By using a4j:Funtcion in combination with "rerender" this is not working on Internet Explorer 11. The problem ist, that after Ajax-Request the Result in XML can not be correct append to the body. (Affects in version 3.3.4 Final) > Reason is simple: > Microsoft has changed the User-Agent for Internet Explorer 11 > Before: > IE10: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0) > Now: > IE11: Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv 11.0) like Gecko > Details: http://msdn.microsoft.com/en-us/library/ie/bg182625(v=vs.85).aspx > In richfaces-imp.jar there is the AJAX.js-File wich rerender the result ofthe Ajax-Request. Here is also Sarissa to identify the Browser. > Because of missing "msie", Sarissa can not identifiy an Internet Explorer 11 as an Internet Explorer. > That means, tha AJAX.js in "richfaces-imp/ort/ajax4jsf/javascript/scripts" has to be modify. > Before: > Sarissa._SARISSA_IS_IE = document.all && window.ActiveXObject && navigator.userAgent.toLowerCase().indexOf("msie") > -1 && navigator.userAgent.toLowerCase().indexOf("opera") == -1 > Now: > Sarissa._SARISSA_IS_IE = (document.all && window.ActiveXObject && navigator.userAgent.toLowerCase().indexOf("msie") > -1 && navigator.userAgent.toLowerCase().indexOf("opera") == -1) || (navigator.userAgent.toLowerCase().indexOf("like gecko") > -1 && navigator.userAgent.toLowerCase().indexOf("11.") > -1); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira From issues at jboss.org Wed Apr 30 10:09:56 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 30 Apr 2014 10:09:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964712#comment-12964712 ] Pavol Pitonak commented on RF-13598: ------------------------------------ I is reproducible with Metamer deployed to Tomcat 7. # deploy Metamer to Tomcat 7 and open http://localhost:8080/metamer/faces/components/a4jJSFunction/simple.xhtml # click the link invoking a4j:jsFunction or # deploy Metamer to Tomcat 7 and open http://localhost:8080/metamer/faces/components/richAccordion/simple.xhtml # switch the accordion item Both cases work fine in Chrome but do nothing in IE 10 and IE 11. > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.7 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > See the https://community.jboss.org/thread/239391 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 10:09:57 2014 From: issues at jboss.org (Pavol Pitonak (JIRA)) Date: Wed, 30 Apr 2014 10:09:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964712#comment-12964712 ] Pavol Pitonak edited comment on RF-13598 at 4/30/14 10:09 AM: -------------------------------------------------------------- I is reproducible with Metamer deployed to Tomcat 7. # deploy Metamer to Tomcat 7 and open http://localhost:8080/metamer/faces/components/a4jJSFunction/simple.xhtml # click the link invoking a4j:jsFunction or # deploy Metamer to Tomcat 7 and open http://localhost:8080/metamer/faces/components/richAccordion/simple.xhtml # switch the accordion item Both cases work fine in Chrome but do nothing in IE 10 and IE 11. What you mean by reproducing with vanilla JSF? This bug influences RichFaces components, I tried slider with f:ajax and it works fine. was (Author: ppitonak): I is reproducible with Metamer deployed to Tomcat 7. # deploy Metamer to Tomcat 7 and open http://localhost:8080/metamer/faces/components/a4jJSFunction/simple.xhtml # click the link invoking a4j:jsFunction or # deploy Metamer to Tomcat 7 and open http://localhost:8080/metamer/faces/components/richAccordion/simple.xhtml # switch the accordion item Both cases work fine in Chrome but do nothing in IE 10 and IE 11. > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.7 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > See the https://community.jboss.org/thread/239391 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 10:15:57 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 30 Apr 2014 10:15:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13569) Photoalbum: the change of users avatar doesn't work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michal Petrov resolved RF-13569. -------------------------------- Resolution: Done > Photoalbum: the change of users avatar doesn't work > --------------------------------------------------- > > Key: RF-13569 > URL: https://issues.jboss.org/browse/RF-13569 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ji?? ?tefek > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.7 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # After the user's avatar is changed, the avatar is not updated in comments or search results (already resolved by https://github.com/richfaces4/dev-examples/commit/942575579f4e80c2d8dac5c3e1e57f8e706ee0cc) > # the avatar is not updated in the users profile after a second change of the avatar (but is updated in search result and in comments) -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 10:19:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 10:19:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13617) CDK - NPE getOutputFileName In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13617: ------------------------------- Description: During backporting chart to 4.5.X I come across this exception. In RF5 CDK works ok. {code} {{[ERROR] Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException: NullPointerException -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at com.sun.tools.javac.main.Main.compile(Main.java:469) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:132) at org.richfaces.cdk.apt.AptBuilder.build(AptBuilder.java:47) at org.richfaces.cdk.Generator.execute(Generator.java:155) at org.richfaces.builder.mojo.GenerateMojo.execute(GenerateMojo.java:254) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) ... 20 more Caused by: java.lang.reflect.InvocationTargetException 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.richfaces.cdk.apt.LibraryProxyInterceptor.invoke(LibraryProxyInterceptor.java:18) at org.richfaces.cdk.generate.java.taghandler.TagHandlerWriter.render(TagHandlerWriter.java:48) at org.richfaces.cdk.apt.DefaultLibraryGenerator.generate(DefaultLibraryGenerator.java:28) at org.richfaces.cdk.apt.CdkProcessorImpl.generate(CdkProcessorImpl.java:157) at org.richfaces.cdk.apt.CdkProcessorImpl.continueAfterJavaSourceProcessing(CdkProcessorImpl.java:133) at org.richfaces.cdk.apt.CdkProcessorImpl.process(CdkProcessorImpl.java:106) at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793) at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$200(JavacProcessingEnvironment.java:97) at com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.runContributingProcs(JavacProcessingEnvironment.java:644) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1027) at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1185) at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1108) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824) at com.sun.tools.javac.main.Main.compile(Main.java:439) ... 25 more Caused by: java.lang.NullPointerException at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutputFileName(TagHandlerClassGenerator.java:87) at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutput(TagHandlerClassGenerator.java:80) at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.process(TagHandlerClassGenerator.java:60) at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.generateTagHandler(TagHandlerGeneratorVisitor.java:74) at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:49) at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:39) at org.richfaces.cdk.model.ComponentModel.accept(ComponentModel.java:45) at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:211) at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:206) at org.richfaces.cdk.model.ComponentLibrary.accept(ComponentLibrary.java:95) ... 43 more [ERROR]}} {code} was: During backporting chart to 4.5.X I come across this exception. In RF5 CDK works ok. {{[ERROR] Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException: NullPointerException -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at com.sun.tools.javac.main.Main.compile(Main.java:469) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:132) at org.richfaces.cdk.apt.AptBuilder.build(AptBuilder.java:47) at org.richfaces.cdk.Generator.execute(Generator.java:155) at org.richfaces.builder.mojo.GenerateMojo.execute(GenerateMojo.java:254) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) ... 20 more Caused by: java.lang.reflect.InvocationTargetException 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.richfaces.cdk.apt.LibraryProxyInterceptor.invoke(LibraryProxyInterceptor.java:18) at org.richfaces.cdk.generate.java.taghandler.TagHandlerWriter.render(TagHandlerWriter.java:48) at org.richfaces.cdk.apt.DefaultLibraryGenerator.generate(DefaultLibraryGenerator.java:28) at org.richfaces.cdk.apt.CdkProcessorImpl.generate(CdkProcessorImpl.java:157) at org.richfaces.cdk.apt.CdkProcessorImpl.continueAfterJavaSourceProcessing(CdkProcessorImpl.java:133) at org.richfaces.cdk.apt.CdkProcessorImpl.process(CdkProcessorImpl.java:106) at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793) at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$200(JavacProcessingEnvironment.java:97) at com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.runContributingProcs(JavacProcessingEnvironment.java:644) at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1027) at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1185) at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1108) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824) at com.sun.tools.javac.main.Main.compile(Main.java:439) ... 25 more Caused by: java.lang.NullPointerException at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutputFileName(TagHandlerClassGenerator.java:87) at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutput(TagHandlerClassGenerator.java:80) at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.process(TagHandlerClassGenerator.java:60) at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.generateTagHandler(TagHandlerGeneratorVisitor.java:74) at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:49) at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:39) at org.richfaces.cdk.model.ComponentModel.accept(ComponentModel.java:45) at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:211) at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:206) at org.richfaces.cdk.model.ComponentLibrary.accept(ComponentLibrary.java:95) ... 43 more [ERROR]}} > CDK - NPE getOutputFileName > --------------------------- > > Key: RF-13617 > URL: https://issues.jboss.org/browse/RF-13617 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Macko > Priority: Blocker > > During backporting chart to 4.5.X I come across this exception. In RF5 CDK works ok. > {code} > {{[ERROR] Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException: NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at com.sun.tools.javac.main.Main.compile(Main.java:469) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:132) > at org.richfaces.cdk.apt.AptBuilder.build(AptBuilder.java:47) > at org.richfaces.cdk.Generator.execute(Generator.java:155) > at org.richfaces.builder.mojo.GenerateMojo.execute(GenerateMojo.java:254) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > ... 20 more > Caused by: java.lang.reflect.InvocationTargetException > 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.richfaces.cdk.apt.LibraryProxyInterceptor.invoke(LibraryProxyInterceptor.java:18) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerWriter.render(TagHandlerWriter.java:48) > at org.richfaces.cdk.apt.DefaultLibraryGenerator.generate(DefaultLibraryGenerator.java:28) > at org.richfaces.cdk.apt.CdkProcessorImpl.generate(CdkProcessorImpl.java:157) > at org.richfaces.cdk.apt.CdkProcessorImpl.continueAfterJavaSourceProcessing(CdkProcessorImpl.java:133) > at org.richfaces.cdk.apt.CdkProcessorImpl.process(CdkProcessorImpl.java:106) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$200(JavacProcessingEnvironment.java:97) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.runContributingProcs(JavacProcessingEnvironment.java:644) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1027) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1185) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1108) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824) > at com.sun.tools.javac.main.Main.compile(Main.java:439) > ... 25 more > Caused by: java.lang.NullPointerException > at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutputFileName(TagHandlerClassGenerator.java:87) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutput(TagHandlerClassGenerator.java:80) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.process(TagHandlerClassGenerator.java:60) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.generateTagHandler(TagHandlerGeneratorVisitor.java:74) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:49) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:39) > at org.richfaces.cdk.model.ComponentModel.accept(ComponentModel.java:45) > at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:211) > at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:206) > at org.richfaces.cdk.model.ComponentLibrary.accept(ComponentLibrary.java:95) > ... 43 more > [ERROR]}} > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 10:36:24 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 30 Apr 2014 10:36:24 -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:comment-tabpanel&focusedCommentId=12964725#comment-12964725 ] Luk?? Fry? commented on RF-13505: --------------------------------- Let's work through the issues reported by QE until some significant blocker is uncovered. > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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.3#6260) From issues at jboss.org Wed Apr 30 10:39:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 30 Apr 2014 10:39:56 -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:comment-tabpanel&focusedCommentId=12964629#comment-12964629 ] Luk?? Fry? edited comment on RF-13505 at 4/30/14 10:37 AM: ----------------------------------------------------------- For the current status: *Benefits of the patch* * addresses a compatibility with other third-party libraries and custom wrappers ** OmniFaces, PrimeFaces * makes the implementation future-proof ** by delegating as much tasks as possible to JSF impl In general, this patch should make sure we tackle with interoperability issues (both, already identified and future ones) *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * [patched in Mojarra 2.1.28|https://java.net/jira/browse/JAVASERVERFACES-3157] ** will this be included in EAP 6.3? * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * look at [the issue Juraj identified|https://issues.jboss.org/browse/RF-13505?focusedCommentId=12953945&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12953945] * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x was (Author: lfryc): For the current status: *Benefits of the patch* * addresses a compatibility with other third-party libraries and custom wrappers ** OmniFaces, PrimeFaces * makes the implementation future-proof ** by delegating as much tasks as possible to JSF impl In general, this patch should make sure we tackle with interoperability issues (both, already identified and future ones) *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * look at [the issue Juraj identified|https://issues.jboss.org/browse/RF-13505?focusedCommentId=12953945&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12953945] * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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.3#6260) From issues at jboss.org Wed Apr 30 10:39:56 2014 From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=) Date: Wed, 30 Apr 2014 10:39:56 -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:comment-tabpanel&focusedCommentId=12964629#comment-12964629 ] Luk?? Fry? edited comment on RF-13505 at 4/30/14 10:39 AM: ----------------------------------------------------------- For the current status: *Benefits of the patch* * addresses a compatibility with other third-party libraries and custom wrappers ** OmniFaces, PrimeFaces * makes the implementation future-proof ** by delegating as much tasks as possible to JSF impl * this branch contains documentation and claritifaction work In general, this patch should make sure we tackle with interoperability issues (both, already identified and future ones) *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * [patched in Mojarra 2.1.28|https://java.net/jira/browse/JAVASERVERFACES-3157] ** will this be included in EAP 6.3? * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * look at [the issue Juraj identified|https://issues.jboss.org/browse/RF-13505?focusedCommentId=12953945&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12953945] * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x was (Author: lfryc): For the current status: *Benefits of the patch* * addresses a compatibility with other third-party libraries and custom wrappers ** OmniFaces, PrimeFaces * makes the implementation future-proof ** by delegating as much tasks as possible to JSF impl In general, this patch should make sure we tackle with interoperability issues (both, already identified and future ones) *Compatibility* * [Mojarra 2.2.6 is released|https://java.net/jira/secure/ReleaseNote.jspa?projectId=10204&version=16664] with the patch included ** included in WildFly 8.1.0.CR1 * [Mojarra 2.2.5-jbossorg-3|https://github.com/jboss/mojarra/commits/2.2.5-jbossorg-3] contains this patch for 3 months now ** included in WildFly 8.0.0.Final * [patched in Mojarra 2.1.28|https://java.net/jira/browse/JAVASERVERFACES-3157] ** will this be included in EAP 6.3? * MyFaces 2.x was always compatible ** in theory, but some testing might be needed (tests pass as far as I can remember) * risks ** patch is not included in GlassFish 4.0 - we will need to tell people using GF to upgrade manually *Suggested action items:* * look at [the issue Juraj identified|https://issues.jboss.org/browse/RF-13505?focusedCommentId=12953945&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12953945] * re-test compatibility with 4.5 branch ** run integration tests for PartialViewContext on WildFly 8.1.0.CR1 and MyFaces 2.2.x > 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? > Priority: Critical > Fix For: 4.5.0.Alpha3 > > 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.3#6260) From issues at jboss.org Wed Apr 30 11:13:56 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 30 Apr 2014 11:13:56 -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=12964736#comment-12964736 ] Michal Petrov commented on RF-13591: ------------------------------------ There seems to be a problem in the configuration, when the build process reaches richfaces-components-a4j the surefire plugin throws a RuntimeException. {{mvn -Dbrowser=phantomjs -Dintegration=wildfly80 -Dsmoke=true clean install}} bq. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (integration-tests) on project richfaces-components-a4j: Execution integration-tests of goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: java.lang.RuntimeException: null,null,null,null,null: source is null -> [Help 1] The configuration for the tests is in the [central POM|https://github.com/richfaces/richfaces/blob/4.5.x/pom.xml#L410]. > 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 > 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 Wed Apr 30 12:15:57 2014 From: issues at jboss.org (Michal Petrov (JIRA)) Date: Wed, 30 Apr 2014 12:15:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964750#comment-12964750 ] Michal Petrov commented on RF-13598: ------------------------------------ As reported, the ajax fails on [this line|https://github.com/jboss/mojarra/blob/2.1.28-jbossorg-1/jsf-api/src/main/resources/jsf.js#L962]. In IE element.name is undefined, in FF and Chrome it's "". (That doesn't seem to be the default state of IE, if you create a new element its name will be "") > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.7 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > See the https://community.jboss.org/thread/239391 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 12:19:56 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 12:19:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-12554) inside doesn't work without a dummy usage outside In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem reopened RF-12554: -------------------------------- Assignee: Pavol Pitonak QE, please re-produce > inside doesn't work without a dummy usage outside > ---------------------------------------------------------------------------- > > 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: Pavol Pitonak > Priority: Minor > > 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 Apr 30 12:19:56 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 12:19:56 -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 updated RF-12554: ------------------------------- Summary: in a doesn't work in composite components (was: inside doesn't work without a dummy usage outside) > 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: Pavol Pitonak > Priority: Minor > > 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 Apr 30 13:46:56 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 13:46:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13598: ------------------------------- Description: I recently tried to update the JSF to 2.1.28 with using Richfaces 4.2.3.Final or Richfaces 4.3.5.Final, and I had issue with AJAX calls. not sure if this is Richfaces issue or JSF issue. My setup is JSF2.1.28, Richfaces 4.2.3.Final (or 4.3.5.Final), WELD 2.1.2.Final, Tomcat 7.0.50, on the client is IE browser. The ajax call will stuck, I looked into the JSF.js, seems it added new method from 2.1.28, {code} var getEncodedUrlElement = function getEncodedUrlElement(form) { var encodedUrlElement = form['javax.faces.encodedURL']; if (encodedUrlElement) { return encodedUrlElement; } else { var formElements = form.elements; for (var i = 0, length = formElements.length; i < length; i++) { var formElement = formElements[i]; if (formElement.name.indexOf('javax.faces.encodedURL') >= 0) { return formElement; } } } return undefined; }; {code} In IE, form['javax.faces.encodedURL'] is undefined, and the " if (formElement.name.indexOf('javax.faces.encodedURL') >= 0) {" will throw exception before it return. this cause the Browser miss behavior, Just wondering is there anybody has the same issue or is Richface 4.x support this version of JSF? was: See the https://community.jboss.org/thread/239391 > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.7 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I recently tried to update the JSF to 2.1.28 with using Richfaces 4.2.3.Final or Richfaces 4.3.5.Final, and I had issue with AJAX calls. not sure if this is Richfaces issue or JSF issue. > My setup is JSF2.1.28, Richfaces 4.2.3.Final (or 4.3.5.Final), WELD 2.1.2.Final, Tomcat 7.0.50, on the client is IE browser. > The ajax call will stuck, I looked into the JSF.js, seems it added new method from 2.1.28, > {code} > var getEncodedUrlElement = function getEncodedUrlElement(form) { > var encodedUrlElement = form['javax.faces.encodedURL']; > > > if (encodedUrlElement) { > return encodedUrlElement; > } else { > var formElements = form.elements; > for (var i = 0, length = formElements.length; i < length; i++) { > var formElement = formElements[i]; > if (formElement.name.indexOf('javax.faces.encodedURL') >= 0) { > return formElement; > } > } > } > > > return undefined; > }; > {code} > In IE, form['javax.faces.encodedURL'] is undefined, and the " if (formElement.name.indexOf('javax.faces.encodedURL') >= 0) {" will throw exception before it return. this cause the Browser miss behavior, > > Just wondering is there anybody has the same issue or is Richface 4.x support this version of JSF? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 14:40:56 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 14:40:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964784#comment-12964784 ] Brian Leathem commented on RF-13598: ------------------------------------ I reproduced this with a vanilla JSF application. I filed an upstream issue here: https://java.net/jira/browse/JAVASERVERFACES-3261 > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.7 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I recently tried to update the JSF to 2.1.28 with using Richfaces 4.2.3.Final or Richfaces 4.3.5.Final, and I had issue with AJAX calls. not sure if this is Richfaces issue or JSF issue. > My setup is JSF2.1.28, Richfaces 4.2.3.Final (or 4.3.5.Final), WELD 2.1.2.Final, Tomcat 7.0.50, on the client is IE browser. > The ajax call will stuck, I looked into the JSF.js, seems it added new method from 2.1.28, > {code} > var getEncodedUrlElement = function getEncodedUrlElement(form) { > var encodedUrlElement = form['javax.faces.encodedURL']; > > > if (encodedUrlElement) { > return encodedUrlElement; > } else { > var formElements = form.elements; > for (var i = 0, length = formElements.length; i < length; i++) { > var formElement = formElements[i]; > if (formElement.name.indexOf('javax.faces.encodedURL') >= 0) { > return formElement; > } > } > } > > > return undefined; > }; > {code} > In IE, form['javax.faces.encodedURL'] is undefined, and the " if (formElement.name.indexOf('javax.faces.encodedURL') >= 0) {" will throw exception before it return. this cause the Browser miss behavior, > > Just wondering is there anybody has the same issue or is Richface 4.x support this version of JSF? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 15:21:56 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 15:21:56 -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:comment-tabpanel&focusedCommentId=12964799#comment-12964799 ] Brian Leathem commented on RF-13602: ------------------------------------ [~wdmmza] please provide specific versions of the container, mojarra, and RichFaces versions you are running. > 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, waiting_on_user > 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 Wed Apr 30 15:25:56 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 15:25:56 -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: ------------------------------- Fix Version/s: 4.3.8 > 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 > Fix For: 4.3.8 > > Attachments: edt.png > > > 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 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 15:25:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 15:25:57 -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: ------------------------------- Assignee: Michal Petrov > 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 > > > 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 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 15:25:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 15:25:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13616: ------------------------------- Steps to Reproduce: 1. Without moving the PopupPanel directly switch to Panel Item 2. 2. The PopupPanel is autosized as expected, correctly adjusting to the size difference between its previous and its current content. Now switch back to Panel Item 1. 3. Move the PopupPanel around and then switch back to Panel Item 2. 4. Notice that the PopupPanel isn't properly autosized anymore but is now stuck to the smaller width of Panel Item 1. Switching to Panel Item 2 will autosize the PopupPanel properly if and only if it hasn't been moved yet. Looking into the PopupPanel source code we found that while initially moving the PopupPanel, the width of the currently active Panel Item is hard-set on said divs in the PopupPanel RichFaces.ui.PopupPanel.prototype.doResizeOrMove method which prevents all further autosizing on move. A possible workaround:- which overrides the original doResizeOrMove method on the RichFaces.ui.PopupPanel prototype and simply undoes the modifications of the previously undefined CSS widths properties on the relevant divs if the PopupPanel autosized attribute is enabled--can be activated by uncommenting the following code in /main/webapp/resources/js/patch-popup-panel.js: {code} /* (function() { var richfacesUiPopupPanelDoResizeOrMove = RichFaces.ui.PopupPanel.prototype.doResizeOrMove; RichFaces.ui.PopupPanel.prototype.doResizeOrMove = function(diff) { var ret = richfacesUiPopupPanelDoResizeOrMove.call(this, diff); if (this.options.autosized) { this.cdiv.css("width", ""); this.contentDiv.css("width", ""); this.scrollerDiv.css("width", ""); this.shadowDiv.css("width", ""); } return ret; }; }()); */ {code} was: 1. Without moving the PopupPanel directly switch to Panel Item 2. 2. The PopupPanel is autosized as expected, correctly adjusting to the size difference between its previous and its current content. Now switch back to Panel Item 1. 3. Move the PopupPanel around and then switch back to Panel Item 2. 4. Notice that the PopupPanel isn't properly autosized anymore but is now stuck to the smaller width of Panel Item 1. Switching to Panel Item 2 will autosize the PopupPanel properly if and only if it hasn't been moved yet. Looking into the PopupPanel source code we found that while initially moving the PopupPanel, the width of the currently active Panel Item is hard-set on said divs in the PopupPanel RichFaces.ui.PopupPanel.prototype.doResizeOrMove method which prevents all further autosizing on move. A possible workaround:- which overrides the original doResizeOrMove method on the RichFaces.ui.PopupPanel prototype and simply undoes the modifications of the previously undefined CSS widths properties on the relevant divs if the PopupPanel autosized attribute is enabled--can be activated by uncommenting the following code in /main/webapp/resources/js/patch-popup-panel.js: /* (function() { var richfacesUiPopupPanelDoResizeOrMove = RichFaces.ui.PopupPanel.prototype.doResizeOrMove; RichFaces.ui.PopupPanel.prototype.doResizeOrMove = function(diff) { var ret = richfacesUiPopupPanelDoResizeOrMove.call(this, diff); if (this.options.autosized) { this.cdiv.css("width", ""); this.contentDiv.css("width", ""); this.scrollerDiv.css("width", ""); this.shadowDiv.css("width", ""); } return ret; }; }()); */ > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final, 4.3.6 > Reporter: abhishek vijra > Attachments: popupPanel.zip > > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 15:27:56 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 15:27:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13616: ------------------------------- Labels: gss (was: ) > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final, 4.3.6 > Reporter: abhishek vijra > Labels: gss > Attachments: popupPanel.zip > > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:01:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:01:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13605: ------------------------------- Labels: gss waiting_on_user (was: ) > a4j:ajax button click event gets lost > ------------------------------------- > > Key: RF-13605 > URL: https://issues.jboss.org/browse/RF-13605 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.6 > Reporter: abhishek vijra > Labels: gss, waiting_on_user > Attachments: queue.zip > > > Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints. > Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior. > {code} > > > > > > > > > > > > > > > > > > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:07:56 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 30 Apr 2014 16:07:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964813#comment-12964813 ] Juraj H?ska commented on RF-13592: ---------------------------------- I have verified the fix with 4.3.7-SNAPSHOT. I have tried on variety of browsers, including IE. I have checked it also for regressions, everything seems to be running just OK. Metamer page simulating also the multipe push example can be found here: https://github.com/richfaces/richfaces-qa/blob/master/metamer/application/src/main/webapp/components/a4jPush/rf-13592.xhtml > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Brian Leathem > Priority: Critical > Labels: gss, needs-qe > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:09:58 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 30 Apr 2014 16:09:58 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska updated RF-13592: ----------------------------- Labels: gss (was: gss needs-qe) > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Brian Leathem > Priority: Critical > Labels: gss > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:10:00 2014 From: issues at jboss.org (=?UTF-8?Q?Juraj_H=C3=BAska_=28JIRA=29?=) Date: Wed, 30 Apr 2014 16:10:00 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13592) a4j:push doesn't work after rendering In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juraj H?ska closed RF-13592. ---------------------------- > a4j:push doesn't work after rendering > ------------------------------------- > > Key: RF-13592 > URL: https://issues.jboss.org/browse/RF-13592 > 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: Chrome 33.0.1750.154 and IE 8.0.7601.17514 > JSF 2.19, Richfaces 4.3.5 > Reporter: Igor Bolshakov > Assignee: Brian Leathem > Priority: Critical > Labels: gss > Fix For: 4.3.7 > > Attachments: a4j.log, localhost.har, push-test.zip, push-test.zip, screenshot.png, web.xml > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I use {{rendered}} attribute to start/stop a4j:push component in example below. After rendering of a4j:push element the handling of incoming push messages is broken. In my simple example I set alert to notify about recieved message (see attached screenshot). > View xhtml code: > {code:xml} > xmlns:a4j="http://richfaces.org/a4j" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets"> > > > rendered="#{testBean.enabled}"/> > > > > > > {code} > Backing bean class: > {code}public class TestBean { > private boolean enabled = false; > public boolean isEnabled() { > return enabled; > } > public void startPush() { > enabled = true; > } > public void stopPush() { > enabled = false; > } > public void sendMessage() throws MessageException { > TopicsContext.lookup().publish(new TopicKey("TEST_ADDRESS"), "Hello World"); > } > }{code} > Configuration in web.xml (see attachment). > Scenario: > 1) Open page > 2) Click "Start Push" button > 3) Click "Send Message" button > 4) Alert "event.rf.data=Hello World" is shown (see attached screenshot) > 5) Click "Stop Push" button > 6) Polling is closed (see localhost.har in attachment) > 7) Click "Start Push" button > 8) Polling is started (see localhost.har in attachment) > 9) Click "Send Message" button > 10) Message is recieved (see localhost.har in attachment) > 11) No alert, no javascript error > For more details I saved a4j:log output in a4j.log file. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:33:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:33:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13619) RichFaces.javascriptServiceComplete(); is not called on normal GET/POST request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964820#comment-12964820 ] Brian Leathem commented on RF-13619: ------------------------------------ $.ready() callbacks are executed once the page is loaded, not after an AJAX update. > RichFaces.javascriptServiceComplete(); is not called on normal GET/POST request > ------------------------------------------------------------------------------- > > Key: RF-13619 > URL: https://issues.jboss.org/browse/RF-13619 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.3.6 > Environment: Richfaces 4.3.6.Final, Tomcat 7.0.53, JSF 2.1.27, Java7u55 > Reporter: Wang Liyu > > In AJAX Response Richfaces added RichFaces.javascriptServiceComplete(); at the end of the response, the default implementation is fire a event, so if I have $.ready() want to do something on delay-constructed Richfaces Objects, this would be the place, I can call $.one('javascriptServiceComplete', functionname); > But if the same page is called with GET/POST method (normal requestion), it won't call this method, is there any reason why is that? > Here is the discussion on the forum: > https://community.jboss.org/thread/240501 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:33:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:33:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13619) RichFaces.javascriptServiceComplete(); is not called on normal GET/POST request In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13619. -------------------------------- Resolution: Rejected > RichFaces.javascriptServiceComplete(); is not called on normal GET/POST request > ------------------------------------------------------------------------------- > > Key: RF-13619 > URL: https://issues.jboss.org/browse/RF-13619 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 4.3.6 > Environment: Richfaces 4.3.6.Final, Tomcat 7.0.53, JSF 2.1.27, Java7u55 > Reporter: Wang Liyu > > In AJAX Response Richfaces added RichFaces.javascriptServiceComplete(); at the end of the response, the default implementation is fire a event, so if I have $.ready() want to do something on delay-constructed Richfaces Objects, this would be the place, I can call $.one('javascriptServiceComplete', functionname); > But if the same page is called with GET/POST method (normal requestion), it won't call this method, is there any reason why is that? > Here is the discussion on the forum: > https://community.jboss.org/thread/240501 -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:35:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:35:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13621) IE11 Changes DOM structure on JSF rerender In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13621: ------------------------------- Fix Version/s: 3.Future > IE11 Changes DOM structure on JSF rerender > ------------------------------------------ > > Key: RF-13621 > URL: https://issues.jboss.org/browse/RF-13621 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 3.3.4.Final > Reporter: Robert Becker > Fix For: 3.Future > > > When rerendering regions with multiple child elements, IE11 breaks the DOM by nesting the former siblings. > I tried changing sarrissa as described in this issue: https://issues.jboss.org/browse/RF-13443 > But it does not seem related or helping. > This stackoverflow question describes the issue perfectly: > http://stackoverflow.com/questions/22015352/ie11-changes-dom-structure-on-jsf-rerender > Here is a screenshot where this problem leads to multiple pagination controls, as the old dom elements reside instead of being replaced when rerendering: https://dl.dropboxusercontent.com/u/18449425/permanent/richfaces%20ie11%20a4j%20rerender.png -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:35:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:35:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13621) IE11 Changes DOM structure on JSF rerender In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964823#comment-12964823 ] Brian Leathem commented on RF-13621: ------------------------------------ RichFaces 3 is no longer supported. Migrate you applications to RichFaces 4. > IE11 Changes DOM structure on JSF rerender > ------------------------------------------ > > Key: RF-13621 > URL: https://issues.jboss.org/browse/RF-13621 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: base functionality > Affects Versions: 3.3.4.Final > Reporter: Robert Becker > Fix For: 3.Future > > > When rerendering regions with multiple child elements, IE11 breaks the DOM by nesting the former siblings. > I tried changing sarrissa as described in this issue: https://issues.jboss.org/browse/RF-13443 > But it does not seem related or helping. > This stackoverflow question describes the issue perfectly: > http://stackoverflow.com/questions/22015352/ie11-changes-dom-structure-on-jsf-rerender > Here is a screenshot where this problem leads to multiple pagination controls, as the old dom elements reside instead of being replaced when rerendering: https://dl.dropboxusercontent.com/u/18449425/permanent/richfaces%20ie11%20a4j%20rerender.png -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:37:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:37:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem resolved RF-13598. -------------------------------- Resolution: Deferred Marking as resolved since it's an upstream issue. > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.3.7 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I recently tried to update the JSF to 2.1.28 with using Richfaces 4.2.3.Final or Richfaces 4.3.5.Final, and I had issue with AJAX calls. not sure if this is Richfaces issue or JSF issue. > My setup is JSF2.1.28, Richfaces 4.2.3.Final (or 4.3.5.Final), WELD 2.1.2.Final, Tomcat 7.0.50, on the client is IE browser. > The ajax call will stuck, I looked into the JSF.js, seems it added new method from 2.1.28, > {code} > var getEncodedUrlElement = function getEncodedUrlElement(form) { > var encodedUrlElement = form['javax.faces.encodedURL']; > > > if (encodedUrlElement) { > return encodedUrlElement; > } else { > var formElements = form.elements; > for (var i = 0, length = formElements.length; i < length; i++) { > var formElement = formElements[i]; > if (formElement.name.indexOf('javax.faces.encodedURL') >= 0) { > return formElement; > } > } > } > > > return undefined; > }; > {code} > In IE, form['javax.faces.encodedURL'] is undefined, and the " if (formElement.name.indexOf('javax.faces.encodedURL') >= 0) {" will throw exception before it return. this cause the Browser miss behavior, > > Just wondering is there anybody has the same issue or is Richface 4.x support this version of JSF? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:37:58 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:37:58 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13598) Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13598: ------------------------------- Fix Version/s: (was: 4.3.7) > Richfaces 4.3.5.Final ajax calls broke with JSF2.1.28 > ------------------------------------------------------ > > Key: RF-13598 > URL: https://issues.jboss.org/browse/RF-13598 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility > Affects Versions: 4.2.3.Final, 4.3.5 > Environment: Tomcat 7.0.50, Richfaces 4.3.5.Final, JSF 2.1.28, client side: IE8+ > Reporter: Wang Liyu > Assignee: Brian Leathem > Priority: Critical > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I recently tried to update the JSF to 2.1.28 with using Richfaces 4.2.3.Final or Richfaces 4.3.5.Final, and I had issue with AJAX calls. not sure if this is Richfaces issue or JSF issue. > My setup is JSF2.1.28, Richfaces 4.2.3.Final (or 4.3.5.Final), WELD 2.1.2.Final, Tomcat 7.0.50, on the client is IE browser. > The ajax call will stuck, I looked into the JSF.js, seems it added new method from 2.1.28, > {code} > var getEncodedUrlElement = function getEncodedUrlElement(form) { > var encodedUrlElement = form['javax.faces.encodedURL']; > > > if (encodedUrlElement) { > return encodedUrlElement; > } else { > var formElements = form.elements; > for (var i = 0, length = formElements.length; i < length; i++) { > var formElement = formElements[i]; > if (formElement.name.indexOf('javax.faces.encodedURL') >= 0) { > return formElement; > } > } > } > > > return undefined; > }; > {code} > In IE, form['javax.faces.encodedURL'] is undefined, and the " if (formElement.name.indexOf('javax.faces.encodedURL') >= 0) {" will throw exception before it return. this cause the Browser miss behavior, > > Just wondering is there anybody has the same issue or is Richface 4.x support this version of JSF? -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:39:56 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:39:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13617) CDK - NPE getOutputFileName In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964826#comment-12964826 ] Brian Leathem commented on RF-13617: ------------------------------------ [~lukindo] are you able to make progress with the workaround suggested by [~michpetrov]? > CDK - NPE getOutputFileName > --------------------------- > > Key: RF-13617 > URL: https://issues.jboss.org/browse/RF-13617 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Reporter: Luk?? Macko > Priority: Blocker > > During backporting chart to 4.5.X I come across this exception. In RF5 CDK works ok. > {code} > {{[ERROR] Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException: NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate (cdk-generate-sources) on project richfaces-components-rich: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution cdk-generate-sources of goal org.richfaces.cdk:richfaces-cdk-maven-plugin:4.5.0.Alpha2:generate failed: java.lang.reflect.InvocationTargetException > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at com.sun.tools.javac.main.Main.compile(Main.java:469) > at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:132) > at org.richfaces.cdk.apt.AptBuilder.build(AptBuilder.java:47) > at org.richfaces.cdk.Generator.execute(Generator.java:155) > at org.richfaces.builder.mojo.GenerateMojo.execute(GenerateMojo.java:254) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > ... 20 more > Caused by: java.lang.reflect.InvocationTargetException > 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.richfaces.cdk.apt.LibraryProxyInterceptor.invoke(LibraryProxyInterceptor.java:18) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerWriter.render(TagHandlerWriter.java:48) > at org.richfaces.cdk.apt.DefaultLibraryGenerator.generate(DefaultLibraryGenerator.java:28) > at org.richfaces.cdk.apt.CdkProcessorImpl.generate(CdkProcessorImpl.java:157) > at org.richfaces.cdk.apt.CdkProcessorImpl.continueAfterJavaSourceProcessing(CdkProcessorImpl.java:133) > at org.richfaces.cdk.apt.CdkProcessorImpl.process(CdkProcessorImpl.java:106) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$200(JavacProcessingEnvironment.java:97) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.runContributingProcs(JavacProcessingEnvironment.java:644) > at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1027) > at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1185) > at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1108) > at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824) > at com.sun.tools.javac.main.Main.compile(Main.java:439) > ... 25 more > Caused by: java.lang.NullPointerException > at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutputFileName(TagHandlerClassGenerator.java:87) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.getOutput(TagHandlerClassGenerator.java:80) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerClassGenerator.process(TagHandlerClassGenerator.java:60) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.generateTagHandler(TagHandlerGeneratorVisitor.java:74) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:49) > at org.richfaces.cdk.generate.java.taghandler.TagHandlerGeneratorVisitor.visitComponent(TagHandlerGeneratorVisitor.java:39) > at org.richfaces.cdk.model.ComponentModel.accept(ComponentModel.java:45) > at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:211) > at org.richfaces.cdk.model.ModelSet.accept(ModelSet.java:206) > at org.richfaces.cdk.model.ComponentLibrary.accept(ComponentLibrary.java:95) > ... 43 more > [ERROR]}} > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:41:56 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:41:56 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13616: ------------------------------- Fix Version/s: 4.3.7 > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final, 4.3.6 > Reporter: abhishek vijra > Labels: gss > Fix For: 4.3.7 > > Attachments: popupPanel.zip > > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:41:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:41:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13616: ------------------------------- Sprint: 4.3.7 Sprint 2 > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final, 4.3.6 > Reporter: abhishek vijra > Labels: gss > Fix For: 4.3.7 > > Attachments: popupPanel.zip > > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 16:41:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 16:41:57 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13616: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final, 4.3.6 > Reporter: abhishek vijra > Labels: gss > Fix For: 4.3.7 > > Attachments: popupPanel.zip > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message was sent by Atlassian JIRA (v6.2.3#6260) From issues at jboss.org Wed Apr 30 17:29:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 17:29:57 -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 ] Brian Leathem updated RF-13505: ------------------------------- Assignee: Luk?? Fry? > 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 > > 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.3#6260) From issues at jboss.org Wed Apr 30 17:29:57 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 17:29:57 -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 ] Brian Leathem updated RF-13591: ------------------------------- Assignee: Luk?? Fry? > 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 Wed Apr 30 19:16:13 2014 From: issues at jboss.org (Brian Leathem (JIRA)) Date: Wed, 30 Apr 2014 19:16:13 -0400 (EDT) Subject: [richfaces-issues] [JBoss JIRA] (RF-13616) PopupPanel autosize with togglePanel doesn't resize In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/RF-13616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964843#comment-12964843 ] Brian Leathem commented on RF-13616: ------------------------------------ [~avijra] can you please provide a compilable reproducer? (ie. a maven project) Binaries don't help much with coming to an issue resolution. > PopupPanel autosize with togglePanel doesn't resize > --------------------------------------------------- > > Key: RF-13616 > URL: https://issues.jboss.org/browse/RF-13616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final, 4.3.6 > Reporter: abhishek vijra > Labels: gss > Fix For: 4.3.7 > > Attachments: popupPanel.zip > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > PopupPanel doesn't autosize correctly after move. Moving a PopupPanel with 'autosized' attribute enabled causes the width properties of its inner container div, content div, srcoller div, and shadow div to be hard-set such that a subsequent content change doesn't trigger the auto-resize of the PopupPanel any longer. The PopupPanel height is apparently unaffected. > Attached is a testcase to demonstrate the problem, see the attached zip file containing a minimal JSF application which reproduces the undesired behavior. -- This message was sent by Atlassian JIRA (v6.2.3#6260)