January 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12725) Metamer: rich:placeholder & input and textarea: error status on submit, output not updated

by Ján Jamrich (JIRA)

Ján Jamrich created RF-12725: -------------------------------- Summary: Metamer: rich:placeholder & input and textarea: error status on submit, output not updated Key: RF-12725 URL: https://issues.jboss.org/browse/RF-12725 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3.0.CR1 Environment: RichFaces 4.3.0.CR1 Metamer 4.3.0.20130114-CR1 JBoss Application Server: Weld Integration 7.1.1.Final JBoss AS 7.1.1.Final Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Chrome 23.0.1271.95 @ Linux i686 Metamer: cfd26771e2c1d9e693fe6844055eba27 metamer-4.3.0.20130114-CR1-jbas71.war NOTE: it is working correctly with MyFaces Reporter: Ján Jamrich Input and textarea examples using placeholder doesn't work correctly. When submit empty form, the Error status appears in Metamer. When submit non empty form, output values are not updated, and the Error status appears instead. But using MyFaces, textarea works correctly, and for input example no Error status, but output values are not update (but have to make sure that there is nothing wrong with outputs, since there are 3 inputs and just 2 outputs, which is a little bit confusing for me) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12692) rich:select - unknown validator SelectLabelValueValidator

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12692?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-12692: ---------------------------------- Verified that {{SelectLabelValueValidator}} is registered in {{faces-config.xml}} instead of using annotation. The workaround functionality verified by the user. Therefore closing. > rich:select - unknown validator SelectLabelValueValidator > --------------------------------------------------------- > > Key: RF-12692 > URL: https://issues.jboss.org/browse/RF-12692 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.M2, 4.3.0.M3 > Environment: Windows7, Tomee 1.0.0 / Webpshere 8.0.0.3, Myfaces 2.0.2/MyFaces 2.1.7 > Reporter: Erdem YILMAZ > Assignee: Lukáš Fryč > Labels: regression > Fix For: 4.3.0.CR1 > > > We have trying our application with the new M3 release/snapshots but have error in all simple pages with rich:select component. We think that on build time SelectLabelValueValidator.class is not added to the richfaces-components-ui-4.3.0.XX.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12692) rich:select - unknown validator SelectLabelValueValidator

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12692?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12692. ---------------------------- > rich:select - unknown validator SelectLabelValueValidator > --------------------------------------------------------- > > Key: RF-12692 > URL: https://issues.jboss.org/browse/RF-12692 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.M2, 4.3.0.M3 > Environment: Windows7, Tomee 1.0.0 / Webpshere 8.0.0.3, Myfaces 2.0.2/MyFaces 2.1.7 > Reporter: Erdem YILMAZ > Assignee: Lukáš Fryč > Labels: regression > Fix For: 4.3.0.CR1 > > > We have trying our application with the new M3 release/snapshots but have error in all simple pages with rich:select component. We think that on build time SelectLabelValueValidator.class is not added to the richfaces-components-ui-4.3.0.XX.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12624) rich:placeholder: placeholder text does not disappear after focus in rich:editor

by Ján Jamrich (JIRA)

[ https://issues.jboss.org/browse/RF-12624?page=com.atlassian.jira.plugin.s... ] Ján Jamrich commented on RF-12624: ---------------------------------- Seems that it is not required create another JIRA for placeholder problems with editor, so just for evidence :-) When submit editor with placeholder, the text from placeholder appears as common editor content... Maybe it is what this JIRA is already reporting. > rich:placeholder: placeholder text does not disappear after focus in rich:editor > -------------------------------------------------------------------------------- > > Key: RF-12624 > URL: https://issues.jboss.org/browse/RF-12624 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Reporter: Jiří Štefek > Fix For: 5-Future > > > When you focus on editor with placeholder, the placeholder's text does not hide. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12718) Missing name attribute for input tags in components listed below

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12718?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-12718: ---------------------------------- Please let me know If I should carefully find all components/files which need a fix. > Missing name attribute for input tags in components listed below > ---------------------------------------------------------------- > > Key: RF-12718 > URL: https://issues.jboss.org/browse/RF-12718 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-validators, third-party > Affects Versions: 4.3.0.CR1 > Reporter: Juraj Húska > Priority: Trivial > > According to the RF-12693 all {{input}} elements should have {{name}} attribute. > The RichFaces components were already fixed. > There are still some (which are created dynamically) which need this fix. > * file {{jquery.pnotify.js}} - RF-12701 is resolved so we can proceed with this one (mode info at [this|https://issues.jboss.org/browse/RF-12693?focusedCommentId=12744223&p...] comment) > * {{jquery-ui.custom.js}} on line [5436|https://github.com/jhuska/components/blob/develop/common/ui/src/main...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12718) Missing name attribute for input tags in components listed below

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12718?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-12718: ----------------------------- Description: According to the RF-12693 all {{input}} elements should have {{name}} attribute. The RichFaces components were already fixed. There are still some (which are created dynamically) which need this fix. * file {{jquery.pnotify.js}} - RF-12701 is resolved so we can proceed with this one (mode info at [this|https://issues.jboss.org/browse/RF-12693?focusedCommentId=12744223&p...] comment) * {{jquery-ui.custom.js}} on line [5436|https://github.com/jhuska/components/blob/develop/common/ui/src/main...] was: According to the RF-12693 all {{input}} elements should have {{name}} attribute. All was done except of {{jquery.pnotify.js}}, as we waited for upgrading. More on [this|https://issues.jboss.org/browse/RF-12693?focusedCommentId=12744223&p...] comment. RF-12701 is done, so could we proceed with this file as well ? > Missing name attribute for input tags in components listed below > ---------------------------------------------------------------- > > Key: RF-12718 > URL: https://issues.jboss.org/browse/RF-12718 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-validators, third-party > Affects Versions: 4.3.0.CR1 > Reporter: Juraj Húska > Priority: Trivial > > According to the RF-12693 all {{input}} elements should have {{name}} attribute. > The RichFaces components were already fixed. > There are still some (which are created dynamically) which need this fix. > * file {{jquery.pnotify.js}} - RF-12701 is resolved so we can proceed with this one (mode info at [this|https://issues.jboss.org/browse/RF-12693?focusedCommentId=12744223&p...] comment) > * {{jquery-ui.custom.js}} on line [5436|https://github.com/jhuska/components/blob/develop/common/ui/src/main...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12718) Missing name attribute for input tags in components listed below

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12718?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-12718: ----------------------------- Summary: Missing name attribute for input tags in components listed below (was: Add name attribute for input tags in jquery.pnotify.js) > Missing name attribute for input tags in components listed below > ---------------------------------------------------------------- > > Key: RF-12718 > URL: https://issues.jboss.org/browse/RF-12718 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-validators, third-party > Affects Versions: 4.3.0.CR1 > Reporter: Juraj Húska > Priority: Trivial > > According to the RF-12693 all {{input}} elements should have {{name}} attribute. > All was done except of {{jquery.pnotify.js}}, as we waited for upgrading. More on [this|https://issues.jboss.org/browse/RF-12693?focusedCommentId=12744223&p...] comment. > RF-12701 is done, so could we proceed with this file as well ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12693) Mojarra fails to encode form inputs correctly when they doesn't have name attribute

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12693?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-12693. ---------------------------- I have verified that all RF components have now {{<input />}} tags with name. Therefore closing. Components which are created dynamically do not have all {<input />} tags with name. Thus I have created one issue for components like that: RF-12718 Its main purpose is to track components which suffers from this problem. > Mojarra fails to encode form inputs correctly when they doesn't have name attribute > ----------------------------------------------------------------------------------- > > Key: RF-12693 > URL: https://issues.jboss.org/browse/RF-12693 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.M3 > Environment: JBoss 7.1.1 with the stock "jsf-impl-2.1.7-jbossorg-2.jar" or upgraded to "jsf-impl-2.1.15.jar" > Reporter: Justin Rosenberg > Assignee: Lukáš Fryč > Fix For: 4.3.0.CR1 > > Attachments: JSFButtonBug-1.0.0-SNAPSHOT.war, mojarraBug.zip > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > When using the Richfaces a4j:commandButton I get the following stack trace when using Internet Explorer 7. This problem does not occur in IE8+ or Chrome. > {code} > 15:19:57,630 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception: java.lang.NullPointerException > at com.sun.faces.context.PartialViewContextImpl.createPartialResponseWriter(PartialViewContextImpl.java:441) [jsf-impl-2.1.15.jar:2.1.15] > at com.sun.faces.context.PartialViewContextImpl.access$300(PartialViewContextImpl.java:71) [jsf-impl-2.1.15.jar:2.1.15] > at com.sun.faces.context.PartialViewContextImpl$DelayedInitPartialResponseWriter.getWrapped(PartialViewContextImpl.java:582) [jsf-impl-2.1.15.jar:2.1.15] > at javax.faces.context.PartialResponseWriter.startDocument(PartialResponseWriter.java:115) [jsf-api-2.1.15.jar:2.1] > at com.sun.faces.context.AjaxExceptionHandlerImpl.handlePartialResponseError(AjaxExceptionHandlerImpl.java:199) [jsf-impl-2.1.15.jar:2.1.15] > at com.sun.faces.context.AjaxExceptionHandlerImpl.handle(AjaxExceptionHandlerImpl.java:124) [jsf-impl-2.1.15.jar:2.1.15] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.15.jar:2.1.15] > at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) [jsf-impl-2.1.15.jar:2.1.15] > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.15.jar:2.1.15] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jsf-api-2.1.15.jar:2.1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:489) [jbossweb-7.0.13.Final.jar:] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.13.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] > at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_20] > {code} > I was surprised that this was only an IE7 issue, but I did find that PrimeFaces ran into a similar problem (http://code.google.com/p/primefaces/issues/detail?id=4361). > Is there a workaround for this? Is this a Mojarra, RichFaces, or JBoss issue? > I created http://java.net/jira/browse/JAVASERVERFACES-2666 in case this is a Mojarra problem, maybe we could help them resolve the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12724) rich:inplaceInput: correct style class names according to Component Reference

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12724: -------------------------------- Summary: rich:inplaceInput: correct style class names according to Component Reference Key: RF-12724 URL: https://issues.jboss.org/browse/RF-12724 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jiří Štefek Priority: Minor Correct the style class names as in component reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-11030) rich:inplaceSelect suggestions disappear when move scroller (in Chrome)

by Ján Jamrich (JIRA)

[ https://issues.jboss.org/browse/RF-11030?page=com.atlassian.jira.plugin.s... ] Ján Jamrich updated RF-11030: ----------------------------- Affects Version/s: 4.3.0.CR1 > rich:inplaceSelect suggestions disappear when move scroller (in Chrome) > ----------------------------------------------------------------------- > > Key: RF-11030 > URL: https://issues.jboss.org/browse/RF-11030 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Milestone1, 4.3.0.CR1 > Reporter: Ján Jamrich > Priority: Minor > Fix For: 5-Future > > > When move scroller by mouse in rich:inplaceSelect without confirmation button (immediate selection) in Chrome browser, whole pop-up with selects disappear. > But scroller works corectly in Forefox. > I made some test changes in ShowCase - added more options into first inplaceSelect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2013