November 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-10783) showcase wrong description of components

by Juraj Huska (JIRA)

showcase wrong description of components ---------------------------------------- Key: RF-10783 URL: https://issues.jboss.org/browse/RF-10783 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.0.0.Final Environment: showcase version v.4.0.0-SNAPSHOT SVN r.22194 Reporter: Juraj Huska There are wrong descriptions of these components: a4j:region, The button inside the first panel should not work according to the description, but actually it works. Client Side Validation, JSR 303 Validators, There is written that there should be ajax fallback when user click on the check box, and there is no ajax fallback. But the checkbox has rich:validator tag also, so the behavior is correct, only the text says something different, so either correct the text or the source code of that page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
4
0 / 0

[JBoss JIRA] (RF-11478) showcase - during deployment on Tomcat java.io.NotSerializableException: org.richfaces.demo.ui.UserAgentProcessor is thrown

by Juraj Huska (Created) (JIRA)

showcase - during deployment on Tomcat java.io.NotSerializableException: org.richfaces.demo.ui.UserAgentProcessor is thrown --------------------------------------------------------------------------------------------------------------------------- Key: RF-11478 URL: https://issues.jboss.org/browse/RF-11478 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone2 Environment: app: richfaces-showcase-4.1.0-SNAPSHOT (20111009.222204-72) container: Tomcat 6.0.32 Reporter: Juraj Huska When deploying on Tomcat 6 the exception is thrown, however the deployment is not halted, and the application is accessible. The stacktrace of that exception is: {code} SEVERE: IOException while loading persisted sessions: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.richfaces.demo.ui.UserAgentProcessor java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.richfaces.demo.ui.UserAgentProcessor at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1485) at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:987) at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:394) at org.apache.catalina.session.StandardManager.load(StandardManager.java:321) at org.apache.catalina.session.StandardManager.start(StandardManager.java:648) at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:446) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4630) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at org.apache.catalina.core.StandardService.start(StandardService.java:525) at org.apache.catalina.core.StandardServer.start(StandardServer.java:754) at org.apache.catalina.startup.Catalina.start(Catalina.java:595) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by: java.io.NotSerializableException: org.richfaces.demo.ui.UserAgentProcessor at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) at org.apache.catalina.session.StandardSession.writeObject(StandardSession.java:1561) at org.apache.catalina.session.StandardSession.writeObjectData(StandardSession.java:1004) at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:528) at org.apache.catalina.session.StandardManager.unload(StandardManager.java:469) at org.apache.catalina.session.StandardManager.stop(StandardManager.java:678) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4875) at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:932) at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1357) at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1328) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:326) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1094) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1106) at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:468) at org.apache.catalina.core.StandardService.stop(StandardService.java:604) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:788) at org.apache.catalina.startup.Catalina.stop(Catalina.java:662) at org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:706) Oct 10, 2011 10:25:28 AM org.apache.catalina.session.StandardManager start SEVERE: Exception loading sessions from persistent storage java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.richfaces.demo.ui.UserAgentProcessor at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1332) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1946) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1870) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1485) at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:987) at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:394) at org.apache.catalina.session.StandardManager.load(StandardManager.java:321) at org.apache.catalina.session.StandardManager.start(StandardManager.java:648) at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:446) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4630) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061) at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at org.apache.catalina.core.StandardService.start(StandardService.java:525) at org.apache.catalina.core.StandardServer.start(StandardServer.java:754) at org.apache.catalina.startup.Catalina.start(Catalina.java:595) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by: java.io.NotSerializableException: org.richfaces.demo.ui.UserAgentProcessor at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) at org.apache.catalina.session.StandardSession.writeObject(StandardSession.java:1561) at org.apache.catalina.session.StandardSession.writeObjectData(StandardSession.java:1004) at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:528) at org.apache.catalina.session.StandardManager.unload(StandardManager.java:469) at org.apache.catalina.session.StandardManager.stop(StandardManager.java:678) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4875) at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:932) at org.apache.catalina.startup.HostConfig.undeployApps(HostConfig.java:1357) at org.apache.catalina.startup.HostConfig.stop(HostConfig.java:1328) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:326) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1094) at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1106) at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:468) at org.apache.catalina.core.StandardService.stop(StandardService.java:604) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:788) at org.apache.catalina.startup.Catalina.stop(Catalina.java:662) at org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:706) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
3
0 / 0

[JBoss JIRA] (RF-11538) showcase - demo rich:notify - sample Attributes of Notify - there is range from 0 to 100 for opacity value and it works only for IE

by Juraj Huska (Created) (JIRA)

showcase - demo rich:notify - sample Attributes of Notify - there is range from 0 to 100 for opacity value and it works only for IE ------------------------------------------------------------------------------------------------------------------------------------ Key: RF-11538 URL: https://issues.jboss.org/browse/RF-11538 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone3 Environment: app: richfaces-showcase-4.1.0.20111011-M3 container: JBoss AS 7.0.2.Final browser: Chrome, Firefox, IE Reporter: Juraj Huska The opacity value can be set in range from 0 to 100. This range should work only for IE, it certainly does not work in Chrome and FF. Need to have possibility to set double value from 0 to 1 for Chrome and FF and from 0 to 100 for IE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

7
9
0 / 0

[JBoss JIRA] (RF-11539) showcase - demo rich:extendedDataTable - sample Table Filtering - no error message when incorrect input is given for mileage input

by Juraj Huska (Created) (JIRA)

showcase - demo rich:extendedDataTable - sample Table Filtering - no error message when incorrect input is given for mileage input ---------------------------------------------------------------------------------------------------------------------------------- Key: RF-11539 URL: https://issues.jboss.org/browse/RF-11539 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone3 Environment: app: richfaces-showcase-4.1.0.20111011-M3 container: JBoss AS 7.0.2.Final browsers: all Reporter: Juraj Huska When user writes characters to the mileage input or too high number there is *no error message shown* like for mileage input in the sample for filtering table in rich:dataTable demo. The reason is that there is *missing rich:messages* tag in the src/main/webapp/richfaces/extendedDataTable/samples/edt-filtering-sample.xhtml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
5
0 / 0

[JBoss JIRA] (RF-11632) showcase - rich:inplaceSelect - example which is activated by doubleClick should be disabled for mobile, not for desktops

by Juraj Huska (Created) (JIRA)

showcase - rich:inplaceSelect - example which is activated by doubleClick should be disabled for mobile, not for desktops ------------------------------------------------------------------------------------------------------------------------- Key: RF-11632 URL: https://issues.jboss.org/browse/RF-11632 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects, showcase Affects Versions: 4.1.0.Milestone4 Environment: app: richfaces-showcase-4.1.0.20111030-M4 containers: all, browsers: all Reporter: Juraj Huska Priority: Trivial In the sample for rich:inplaceSelect, there is example which should be activated by doubleClick disabled for desktop, not for mobile. *It should be other way round.* I think that it is *just typo* in the file: https://github.com/richfaces/showcase/blob/develop/src/main/webapp/richfa... particularly on the line 20: {code} <a4j:outputPanel rendered="#{userAgent.phone or userAgent.tablet}"> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

5
5
0 / 0

[JBoss JIRA] (RF-11530) Metamer and IE 8: can't set attributes after interaction with component

by Jan Papousek (Created) (JIRA)

Metamer and IE 8: can't set attributes after interaction with component ----------------------------------------------------------------------- Key: RF-11530 URL: https://issues.jboss.org/browse/RF-11530 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Milestone3 Reporter: Jan Papousek After I did some interaction with component, I can't set any component attribute (the attribute form can't be submitted). To reproduce it: # open http://localhost:8080/metamer/faces/components/richAccordion/simple.xhtml in IE 8 # click on _item 2_ # try to set _cycledSwitching_ to _true_ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

11
16
0 / 0

[JBoss JIRA] (RF-11574) Showcase: rich:autocomplete with custom popup layout -> filtering doesn't work

by Jan Papousek (Created) (JIRA)

Showcase: rich:autocomplete with custom popup layout -> filtering doesn't work ------------------------------------------------------------------------------ Key: RF-11574 URL: https://issues.jboss.org/browse/RF-11574 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input, showcase Affects Versions: 4.1.0.Milestone3 Environment: Firefox 6.0 Google Chrome 12.0.742.112 Reporter: Jan Papousek The Showcase demo containing custom layout for autocomplete popups doesn't work properly. When something is typed into the input field, popup is displated, but the items are not filtered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
2
0 / 0

[JBoss JIRA] (RF-11571) rich:extendedDataTable inside rich:collapsiblePanel and Google Chrome 12: dissappearing table

by Jan Papousek (Created) (JIRA)

rich:extendedDataTable inside rich:collapsiblePanel and Google Chrome 12: dissappearing table --------------------------------------------------------------------------------------------- Key: RF-11571 URL: https://issues.jboss.org/browse/RF-11571 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.1.0.Milestone3 Environment: Google Chrome 12.0.742.112 Reporter: Jan Papousek Attachments: buggy-richfaces-snapshot.zip, google_chrome12-buggy.png Using Google Chrome 12, the rich:extendedDataTable disappears sometimes (see steps to reproduce). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
4
0 / 0

[JBoss JIRA] (RF-11570) rich:extendedDataTable inside rich:collapsiblePanel and IE 8: disappearing header

by Jan Papousek (Created) (JIRA)

rich:extendedDataTable inside rich:collapsiblePanel and IE 8: disappearing header --------------------------------------------------------------------------------- Key: RF-11570 URL: https://issues.jboss.org/browse/RF-11570 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.1.0.Milestone3 Environment: IE 8 Reporter: Jan Papousek Using IE 8, the rich:extendedDataTable header disappears sometimes (see steps to reproduce). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
7
0 / 0

[JBoss JIRA] (RF-11558) showcase - rich:notify - sample Attributes of Notify - in some configuration it is not possible to close notification

by Juraj Huska (Created) (JIRA)

showcase - rich:notify - sample Attributes of Notify - in some configuration it is not possible to close notification --------------------------------------------------------------------------------------------------------------------- Key: RF-11558 URL: https://issues.jboss.org/browse/RF-11558 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone3 Environment: app: richfaces-showcase-4.1.0.20111014-M3 all containers all browsers Reporter: Juraj Huska Priority: Minor In one specific configuration it is not possible to close notify component, despite that it said so in the notify message. These attributes needs to be set to achieve this: It has to be unchecked "show close button" and checked "sticky". On the notification is written this: This message is sticky, it will stay here until you close it. However this behavior can be desired( user wants to have notifications which are not possible to close, to not to forget on them ....). So IMHO this can be solved in three ways: 1. alter the notification text in this configurations of attributes on something like: This message is sticky, it will stay here until you refresh the page" 2. forbid such a behavior with always checked "show close button" when "sticky" is checked 3. change code of notify in the way that it can not be set Personally I like second way the most. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2011