August 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13136) a4j:log with mode=console doesn't take log level into consideration

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13136?page=com.atlassian.jira.plugin.s... ] Matej Novotny commented on RF-13136: ------------------------------------ Issue verified. Can be closed. > a4j:log with mode=console doesn't take log level into consideration > ------------------------------------------------------------------- > > Key: RF-13136 > URL: https://issues.jboss.org/browse/RF-13136 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.3 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > > Here the log.js [logs message to browser console|https://github.com/richfaces4/components/blob/4.3.3.20130710-Fina...] > but it ignores [log level check|https://github.com/richfaces4/components/blob/4.3.3.20130710-Final/...] which happens only for other modes. -- This message is automatically generated by JIRA. 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13017) richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13017?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-13017: ------------------------------------ Verified in 4.3.4, it's ready to be closed. > richfaces-bom 4.3.2.Final, JSF-API 2.1.0 not compatible > ------------------------------------------------------- > > Key: RF-13017 > URL: https://issues.jboss.org/browse/RF-13017 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.2 > Reporter: Himanshu Bhardwaj > Assignee: Brian Leathem > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > In the bom of RichFaces, the version of JSF-API being used is > {code} > <version.com.sun.faces.jsf-api>2.1.0</version.com.sun.faces.jsf-api> > {code} > > but the version of JSF-IMPL put in use is: > {code} > <version.org.jboss.javax.faces.jsf-impl>2.1.19-jbossorg-1</version.org.jboss.javax.faces.jsf-impl> > {code} > > Both the version don't seem to go together. Got the following stack-trace: > > {code} > SEVERE: ContainerBase.addChild: start: > org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]] > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) > at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977) > at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655) > at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > Caused by: java.lang.NullPointerException > at com.sun.faces.config.InitFacesContext.cleanupInitMaps(InitFacesContext.java:281) > at com.sun.faces.config.InitFacesContext.<init>(InitFacesContext.java:107) > at com.sun.faces.config.FacesInitializer.onStartup(FacesInitializer.java:115) > at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5274) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > ... 11 more > > > May 21, 2013 11:30:43 AM org.apache.catalina.startup.HostConfig deployWAR > SEVERE: Error deploying web application archive F:\DevTools\apache-tomcat-7.0.34\webapps\abc.war > java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/abc]] > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633) > at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:977) > at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1655) > at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > {code} > > I had to manually delete the 2.1.0 jsf-api jar from the war file and copy 2.1.19, with this I was able to bypass this 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13137) a4j:log - wrong log levels in attribute description

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13137?page=com.atlassian.jira.plugin.s... ] Matej Novotny commented on RF-13137: ------------------------------------ Verified, issue can be closed. > a4j:log - wrong log levels in attribute description > --------------------------------------------------- > > Key: RF-13137 > URL: https://issues.jboss.org/browse/RF-13137 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > > The description is: > {code} > Sets the logging level, can be one of "ERROR", "FATAL", "INFO", "WARN", "ALL" > {code} > but should be: > {code} > Sets the logging level, can be one of 'debug', 'info', 'warn', 'error'. > {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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13140) PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13140?page=com.atlassian.jira.plugin.s... ] Matej Novotny reopened RF-13140: -------------------------------- > PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet > ------------------------------------------------------------------------------------------ > > Key: RF-13140 > URL: https://issues.jboss.org/browse/RF-13140 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.3 > Reporter: Lukáš Fryč > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > In RF-13052 and RF-10697 we have discussed that @keepVisualState and @visualOptions attributes do not work cause they were just partiaully implemented. > Moreover, @visualOptions seems to be used just as a storage, thus it should be hidden. -- This message is automatically generated by JIRA. 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13140) PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13140?page=com.atlassian.jira.plugin.s... ] Matej Novotny edited comment on RF-13140 at 8/22/13 8:42 AM: ------------------------------------------------------------- Verified - issue can be closed. was (Author: manovotn): Verified - closing issue. > PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet > ------------------------------------------------------------------------------------------ > > Key: RF-13140 > URL: https://issues.jboss.org/browse/RF-13140 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.3 > Reporter: Lukáš Fryč > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > In RF-13052 and RF-10697 we have discussed that @keepVisualState and @visualOptions attributes do not work cause they were just partiaully implemented. > Moreover, @visualOptions seems to be used just as a storage, thus it should be hidden. -- This message is automatically generated by JIRA. 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13140) PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13140?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13140. ------------------------------ Assignee: (was: Lukáš Fryč) > PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet > ------------------------------------------------------------------------------------------ > > Key: RF-13140 > URL: https://issues.jboss.org/browse/RF-13140 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.3 > Reporter: Lukáš Fryč > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > In RF-13052 and RF-10697 we have discussed that @keepVisualState and @visualOptions attributes do not work cause they were just partiaully implemented. > Moreover, @visualOptions seems to be used just as a storage, thus it should be hidden. -- This message is automatically generated by JIRA. 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13140) PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13140?page=com.atlassian.jira.plugin.s... ] Matej Novotny commented on RF-13140: ------------------------------------ Verified - closing issue. > PopupPanel: Hide @visualOptions and @keepVisualState options which weren't implemented yet > ------------------------------------------------------------------------------------------ > > Key: RF-13140 > URL: https://issues.jboss.org/browse/RF-13140 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.3 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > In RF-13052 and RF-10697 we have discussed that @keepVisualState and @visualOptions attributes do not work cause they were just partiaully implemented. > Moreover, @visualOptions seems to be used just as a storage, thus it should be hidden. -- This message is automatically generated by JIRA. 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13010) Popup panel inside popup panel: button not rendered in IE10

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13010?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-13010: ------------------------------------ Verified in 4.3.4, it's ready to be closed. > Popup panel inside popup panel: button not rendered in IE10 > ----------------------------------------------------------- > > Key: RF-13010 > URL: https://issues.jboss.org/browse/RF-13010 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.2, 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.13 > EAP 6.0.1 > Java(TM) SE Runtime Environment 1.6.0_32-b05 @ Linux > works in Chrome 27.0.1453.93 @ Linux x86_64 > broken in IE10 @ Win 8, IE9 @ Win 7 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe, regression > Fix For: 4.3.4 > > Attachments: buttonInPopupPanel.png > > > # deploy Metamer and open http://192.168.122.1:8080/metamer/faces/components/richPopupPanel/simple.... > # change template to "Rich Popup Panel" > # click the "Call the popup" button > result: > * the is a button between paragraph and link inside popup panel in Chrome/Firefox > * the button is missing in IE 10 > * it might be related to RF-12850 or RF-12958 > * worked fine in 4.3.1.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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12943) ExtendedDataTable: clearing of filter input doesnt work correctly

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12943?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-12943: ------------------------------------ Verified in 4.3.4, it's ready to be closed. > ExtendedDataTable: clearing of filter input doesnt work correctly > ----------------------------------------------------------------- > > Key: RF-12943 > URL: https://issues.jboss.org/browse/RF-12943 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.1 > Environment: Tomcat 7, Mojarra 2.1.21 > Reporter: dako ak > Assignee: Brian Leathem > Labels: testcase_provided > Fix For: 4.3.4 > > Attachments: JSF2-RichFaces-Test.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > According to my appended test project: > I have a simple extendedDataTable with one column (firstName) with a filter input component within the header. This is the default filter input created by the extendedDataTable. The second column (city) has a filterType="custom" and an inputText componenent within the header. > The filterType attribute with value "custom" has a problem such that I can't clear this filter input text components by a a4j:commandButton. The table is correct filtered but the filter input text fields are not cleared. -- This message is automatically generated by JIRA. 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13038) Command button/link: attribute tabindex missing

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13038?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-13038: ------------------------------------ Verified in 4.3.4, it's ready to be closed. > Command button/link: attribute tabindex missing > ----------------------------------------------- > > Key: RF-13038 > URL: https://issues.jboss.org/browse/RF-13038 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.2, 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Components command button and command link don't have attribute "tabindex", however, when it's set on the component, it's rendered correctly. This issue is similar to one for accesskey attribute (RF-12846). -- This message is automatically generated by JIRA. 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, 7 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 August 2013