December 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel (4.2.3)

by Kaveh A. (JIRA)

Kaveh A. created RF-12682: ----------------------------- Summary: extendedDataTable render issue with rich:tabPanel (4.2.3) Key: RF-12682 URL: https://issues.jboss.org/browse/RF-12682 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-tables Reporter: Kaveh A. Fix For: 4.2.3.Final This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time). In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue. https://community.jboss.org/message/783787 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION

by Dupont Dupont (JIRA)

[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ] Dupont Dupont commented on RF-12670: ------------------------------------ I have the impression with Java EE 6 all spec impl are linked : * you cannot change jsf impl easily in an appServer otherwise (even if it works) you won't have access to CDI managed beans from your JSF pages. * same thing, you cannot change CDI impl in an appServer, otherwise (even if it works) you don't have access to EJBs. Illustration of this problem for JBoss is here : https://issues.jboss.org/browse/AS7-1628. In this context, I'm not sure that requiring JSF 2.1 is a good decision (JSF 2.1 isn't integrated into Java EE 6 and it won't be integrated in Java EE 7). A better approach (IMO), would be to align RF with a Java EE version (so Java EE6 = JSF 2.0, Java EE 7 = JSF 2.2). Did I miss something ? > JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION > --------------------------------------------------------------------------------------------------- > > Key: RF-12670 > URL: https://issues.jboss.org/browse/RF-12670 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.M3 > Reporter: Dupont Dupont > Assignee: Brian Leathem > > When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a > {code} > java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION > at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387) > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at javax.faces.component.UIForm.visitTree(UIForm.java:269) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90) > at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171) > at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at > {code} > RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor. > See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12670) JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION

by Dupont Dupont (JIRA)

[ https://issues.jboss.org/browse/RF-12670?page=com.atlassian.jira.plugin.s... ] Dupont Dupont commented on RF-12670: ------------------------------------ IBM provides a mean to upgrade WAS JSF impl : http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm... Problem is : when jsf impl is upgraded, JSF doesn't have access anymore to CDI beans (only to JSF managed beans). IMO, this is a blocker (at least for us). I'm in contact with IBM support, so I'll let you know - hopefully on 27 dec (holidays). > JSF 2.0 compatibility issue, NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION > --------------------------------------------------------------------------------------------------- > > Key: RF-12670 > URL: https://issues.jboss.org/browse/RF-12670 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.M3 > Reporter: Dupont Dupont > Assignee: Brian Leathem > > When using RF 4.3.0-SNAPSHOT with a JSF 2.0 implementation (i.e. Websphere 8), I get a > {code} > java.lang.NoSuchFieldError: javax/faces/component/visit/VisitHint.SKIP_ITERATION > at org.richfaces.component.UIDataAdaptor.requiresRowIteration(UIDataAdaptor.java:1387) > at org.richfaces.component.UIDataAdaptor.visitTree(UIDataAdaptor.java:1304) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at javax.faces.component.UIForm.visitTree(UIForm.java:269) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at javax.faces.component.UIComponent.visitTree(UIComponent.java:793) > at javax.faces.component.UIComponentBase.visitTree(UIComponentBase.java:1007) > at org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.processComponentBinding(DefaultRestoreViewSupport.java:90) > at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:142) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:171) > at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) > at > {code} > RF 4.3.0-SNAPSHOT is using an API introduced with JSF 2.1 in UIDataAdaptor. > See https://github.com/richfaces/components/commit/d65e614ef03adf87c0b6df2288... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12681) Curious settings for rf-cal-hov in calendar.ecss

by Lutz Ulrich (JIRA)

Lutz Ulrich created RF-12681: -------------------------------- Summary: Curious settings for rf-cal-hov in calendar.ecss Key: RF-12681 URL: https://issues.jboss.org/browse/RF-12681 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.3.Final Reporter: Lutz Ulrich Priority: Trivial CSS specification is redundant / inconsistent: .rf-cal-hov { background-color: '#{richSkin.calendarSpecBackgroundColor}'; background-color: '#{richSkin.calendarSpecTextColor}'; } Perhaps 'color' should be mapped to richSkin.calendarSpecTextColor . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12674) Write fundamental tests for Autocomplete tokenizing feature

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12674?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12674: ---------------------------- Fix Version/s: 5.0.0.M1 > Write fundamental tests for Autocomplete tokenizing feature > ----------------------------------------------------------- > > Key: RF-12674 > URL: https://issues.jboss.org/browse/RF-12674 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.3.0.M3 > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Fix For: 5.0.0.M1 > > > According to RF-12664 and meeting discussion, > the new tests should be introduced to cover Autocomplete tokenizing feature by fundamental tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12674) Write fundamental tests for Autocomplete tokenizing feature

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12674?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12674: ---------------------------- Fix Version/s: 5-Tracking (was: 5.0.0.M1) > Write fundamental tests for Autocomplete tokenizing feature > ----------------------------------------------------------- > > Key: RF-12674 > URL: https://issues.jboss.org/browse/RF-12674 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.3.0.M3 > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Fix For: 5-Tracking > > > According to RF-12664 and meeting discussion, > the new tests should be introduced to cover Autocomplete tokenizing feature by fundamental tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12678) Rich:editor - unterminated string literal JS error when submitting editor value

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12678?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-12678: ----------------------------- Steps to Reproduce: # load http://localhost:8080/metamer/faces/components/richEditor/simple.xhtml # write something to the editor # make BLUR on the editor or submit via button # see the JS errors was: # load http://localhost:8080/metamer/faces/components/richEditor/simple.xhtml # write something to the editor # make BLUR on the editor or submit via button > Rich:editor - unterminated string literal JS error when submitting editor value > -------------------------------------------------------------------------------- > > Key: RF-12678 > URL: https://issues.jboss.org/browse/RF-12678 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.M3 > Environment: RichFaces 4.3.0.20121214-M3 > Metamer 4.3.0.20121218-M3 > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_05-b06 @ Linux > Firefox 17.0 @ Linux x86_64, Chrome > Reporter: Juraj Húska > Priority: Minor > Labels: regression > Attachments: editorJSerror1.png, editorJSerror2.png > > > When submitting value from {{rich:editor}} JS error are thrown. Please see the attachment. > I have not found any broken functionality though, just those JS errors. > Is it caused by update of CKEditor or JQuery libraries ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12680) Infinite XHR after error on fileUpload

by Siarhei Khamenka (JIRA)

[ https://issues.jboss.org/browse/RF-12680?page=com.atlassian.jira.plugin.s... ] Siarhei Khamenka updated RF-12680: ---------------------------------- Attachment: infinite-progress.png > Infinite XHR after error on fileUpload > -------------------------------------- > > Key: RF-12680 > URL: https://issues.jboss.org/browse/RF-12680 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.2.Final > Reporter: Siarhei Khamenka > Attachments: infinite-progress.png > > > After fileUpload failed due to HTTP error "413 Request Entity Too Large" progress bar sends infinite requests to server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12680) Infinite XHR after error on fileUpload

by Siarhei Khamenka (JIRA)

Siarhei Khamenka created RF-12680: ------------------------------------- Summary: Infinite XHR after error on fileUpload Key: RF-12680 URL: https://issues.jboss.org/browse/RF-12680 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.2.Final Reporter: Siarhei Khamenka After fileUpload failed due to HTTP error "413 Request Entity Too Large" progress bar sends infinite requests to server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12679) onerror attribute is missing in fileUpload

by Siarhei Khamenka (JIRA)

Siarhei Khamenka created RF-12679: ------------------------------------- Summary: onerror attribute is missing in fileUpload Key: RF-12679 URL: https://issues.jboss.org/browse/RF-12679 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.2.Final Reporter: Siarhei Khamenka Priority: Critical onerror attribute is missing from in:fileUpload in 4.2.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2012