November 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13209) RichTree JS onselectionchange() with a4jregion template

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13209?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13209: ------------------------------- Fix Version/s: 5-Tracking > RichTree JS onselectionchange() with a4jregion template > ------------------------------------------------------- > > Key: RF-13209 > URL: https://issues.jboss.org/browse/RF-13209 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final, 4.3.3, 4.3.4 > Reporter: Matej Novotny > Fix For: 5-Tracking > > > There is a bug when using onselectionchange() JS API in RichTree component using A4jRegion template (rest of the templates cause no problems). > The event will be called twice - in my case I tested it with simple alert("text") in Metamer using JBoss AS 7.1. > This bug appears in older version as well, so far I have tested it with 4.3.4, 4.3.3 and 4.2.3 Final builds all of which caused the same double event. -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13207) Table having multiple sub-rows within a main row in extended datatable

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13207?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13207: ------------------------------- Labels: waiting_on_user (was: ) > Table having multiple sub-rows within a main row in extended datatable > ---------------------------------------------------------------------- > > Key: RF-13207 > URL: https://issues.jboss.org/browse/RF-13207 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk, component-tables > Affects Versions: 4.3.1 > Environment: windows 7 , JRE 7 > Reporter: sathiyan venkatesh > Labels: waiting_on_user > -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13206) Failure to reset ClassLoader when AWT Initialization errors

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13206?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13206: ------------------------------- Labels: low_hanging_fruit (was: ) > Failure to reset ClassLoader when AWT Initialization errors > ----------------------------------------------------------- > > Key: RF-13206 > URL: https://issues.jboss.org/browse/RF-13206 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.3 > Environment: ServiceMix > Reporter: Donald Oakes > Priority: Minor > Labels: low_hanging_fruit > Fix For: 5-Tracking > > > In org.richfaces.application.InitializationListener.AWTInitializer, the initalize() method can fail to reset the context ClassLoader despite the finally block that should do that (from line 195): > {code:title=org.richfaces.application.InitializationListener.AWTInitializer#195} > } finally { > if (testStream != null) { > try { > testStream.close(); > } catch (IOException e) { > LOGGER.error(e.getMessage(), e); > } > } > thread.setContextClassLoader(initialTCCL); > } > {code} > In my OSGi environment, the testStream.close() invocation throws the NoClassDefFoundError pasted below. This circumvents the subsequent intention to restore the context ClassLoader. In effect, if AWT initialization fails the context ClassLoader is left in a bad state that prevents future ServiceTracker processing and hoses up the Faces initialization. > {code} > java.lang.NoClassDefFoundError: javax/imageio/stream/ImageInputStream > at org.richfaces.application.InitializationListener$AWTInitializer.initialize(InitializationListener.java:198) > at org.richfaces.application.InitializationListener.initializeAWT(InitializationListener.java:94) > at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:78) > at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:152) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43) > at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2471) > at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:120) > at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2662) > at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:601) > at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:286) > at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:154) > at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119) > {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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13206) Failure to reset ClassLoader when AWT Initialization errors

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13206?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13206: ------------------------------- Fix Version/s: 5-Tracking > Failure to reset ClassLoader when AWT Initialization errors > ----------------------------------------------------------- > > Key: RF-13206 > URL: https://issues.jboss.org/browse/RF-13206 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.3 > Environment: ServiceMix > Reporter: Donald Oakes > Priority: Minor > Fix For: 5-Tracking > > > In org.richfaces.application.InitializationListener.AWTInitializer, the initalize() method can fail to reset the context ClassLoader despite the finally block that should do that (from line 195): > {code:title=org.richfaces.application.InitializationListener.AWTInitializer#195} > } finally { > if (testStream != null) { > try { > testStream.close(); > } catch (IOException e) { > LOGGER.error(e.getMessage(), e); > } > } > thread.setContextClassLoader(initialTCCL); > } > {code} > In my OSGi environment, the testStream.close() invocation throws the NoClassDefFoundError pasted below. This circumvents the subsequent intention to restore the context ClassLoader. In effect, if AWT initialization fails the context ClassLoader is left in a bad state that prevents future ServiceTracker processing and hoses up the Faces initialization. > {code} > java.lang.NoClassDefFoundError: javax/imageio/stream/ImageInputStream > at org.richfaces.application.InitializationListener$AWTInitializer.initialize(InitializationListener.java:198) > at org.richfaces.application.InitializationListener.initializeAWT(InitializationListener.java:94) > at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:78) > at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:152) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43) > at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2471) > at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:120) > at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2662) > at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:601) > at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:286) > at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:154) > at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119) > {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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13206) Failure to reset ClassLoader when AWT Initialization errors

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13206?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13206: ------------------------------------ [~oakesville] would you like to formulate a pull request with a fix for this issue? https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA > Failure to reset ClassLoader when AWT Initialization errors > ----------------------------------------------------------- > > Key: RF-13206 > URL: https://issues.jboss.org/browse/RF-13206 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.3 > Environment: ServiceMix > Reporter: Donald Oakes > Priority: Minor > > In org.richfaces.application.InitializationListener.AWTInitializer, the initalize() method can fail to reset the context ClassLoader despite the finally block that should do that (from line 195): > {code:title=org.richfaces.application.InitializationListener.AWTInitializer#195} > } finally { > if (testStream != null) { > try { > testStream.close(); > } catch (IOException e) { > LOGGER.error(e.getMessage(), e); > } > } > thread.setContextClassLoader(initialTCCL); > } > {code} > In my OSGi environment, the testStream.close() invocation throws the NoClassDefFoundError pasted below. This circumvents the subsequent intention to restore the context ClassLoader. In effect, if AWT initialization fails the context ClassLoader is left in a bad state that prevents future ServiceTracker processing and hoses up the Faces initialization. > {code} > java.lang.NoClassDefFoundError: javax/imageio/stream/ImageInputStream > at org.richfaces.application.InitializationListener$AWTInitializer.initialize(InitializationListener.java:198) > at org.richfaces.application.InitializationListener.initializeAWT(InitializationListener.java:94) > at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:78) > at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:152) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:43) > at org.apache.myfaces.application.ApplicationImpl._traverseListenerList(ApplicationImpl.java:2471) > at org.apache.myfaces.application.ApplicationImpl.access$000(ApplicationImpl.java:120) > at org.apache.myfaces.application.ApplicationImpl$SystemListenerEntry.publish(ApplicationImpl.java:2662) > at org.apache.myfaces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:601) > at org.apache.myfaces.webapp.AbstractFacesInitializer._dispatchApplicationEvent(AbstractFacesInitializer.java:286) > at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:154) > at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:119) > {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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13287) rich:extendedDataTable column resizing with ajax loading not working properly

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13287?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13287: ------------------------------------ Thanks for resolving this [~michpetrov]. Would you mind porting the fix to the 4.5 and 5.0 branches as well? this way we will get the fix out ASAP. > rich:extendedDataTable column resizing with ajax loading not working properly > ----------------------------------------------------------------------------- > > Key: RF-13287 > URL: https://issues.jboss.org/browse/RF-13287 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2, Mojarra 2.1.26, IE10, IE8, Chrome 30, > Reporter: Andreas G > Assignee: Michal Petrov > Labels: needs-qe, testcase_provided > Fix For: 4.3.5 > > > In a rich:extendedDataTable with ajax loading turned on: When you resize a column and scroll down (load data), the size of the columns reset to their original value. Only the header keeps its size. The header and the data are not matching anymore. > Reproducible in the 4.3.4 showcase! -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13287) rich:extendedDataTable column resizing with ajax loading not working properly

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13287?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13287: ------------------------------- Labels: needs-qe testcase_provided (was: testcase_provided) > rich:extendedDataTable column resizing with ajax loading not working properly > ----------------------------------------------------------------------------- > > Key: RF-13287 > URL: https://issues.jboss.org/browse/RF-13287 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.4 > Environment: Glassfish 3.1.2.2, Mojarra 2.1.26, IE10, IE8, Chrome 30, > Reporter: Andreas G > Assignee: Michal Petrov > Labels: needs-qe, testcase_provided > Fix For: 4.3.5 > > > In a rich:extendedDataTable with ajax loading turned on: When you resize a column and scroll down (load data), the size of the columns reset to their original value. Only the header keeps its size. The header and the data are not matching anymore. > Reproducible in the 4.3.4 showcase! -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13290) Push framework tests fail after upgrade to 1.0.17 (probably Warp issue)

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13290?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13290: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Push framework tests fail after upgrade to 1.0.17 (probably Warp issue) > ----------------------------------------------------------------------- > > Key: RF-13290 > URL: https://issues.jboss.org/browse/RF-13290 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, tests - functional > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Fix For: 5.0.0.Alpha3 > > > The push is correctly using 'long-polling' technique, > the request is sent, but the response is never sent back, > that's why I believe the Warp server-side handling fails. > ---- > Note that I have tried to upgrade to 1.0.18 and it didn't help. > ---- > I'm marking those tests as {{Failing}}. -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13327) pickList - setting of multiple attributes does not have any effect on the component

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13327: ------------------------------------ Thanks [~jhuska] > pickList - setting of multiple attributes does not have any effect on the component > ----------------------------------------------------------------------------------- > > Key: RF-13327 > URL: https://issues.jboss.org/browse/RF-13327 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow). > *Buttons text* > * addAllText > * addText > * removeAllText > * removeText > * downBottomText > * downText > * upText > * upTopText > *List style* > * maxListHeight > * minListHeight > * style > * columnClasses > *Other RW options* > * switchByClick > * switchByDblClick > *Callbacks* > * onremoveitems > * onadditems > * value > * valueChangeListener > I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src...] ? -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13344) pickList - maxListHeight & minListHeight need to have set units along with number to work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13344?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13344: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > pickList - maxListHeight & minListHeight need to have set units along with number to work > ----------------------------------------------------------------------------------------- > > Key: RF-13344 > URL: https://issues.jboss.org/browse/RF-13344 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > Fix For: 5.0.0.Alpha2 > > > {{pickList}} attributes: > * {{minListHeight}} and {{maxListHeight}} > need to have set units along with the number value (e.g. 200px) in order to work correctly. > In RF4 and in RichWidgets, these attributes can be left without units. -- This message is automatically generated by JIRA. 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, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2013