January 2013 - richfaces-issues - Jboss List Archives

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

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12692?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12692: --------------------------------- I would recommend you to investigate the issue more deeply and find out why your container doesn't want to grab JSF annotation - this might be serious issue in implementation. > 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: SelectLabelValueValidator, missing, 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, 4 months

1
0
0 / 0

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

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12692?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12692: ---------------------------- Workaround Description: Use application {{faces-config.xml}} to register validator: {code:xml} <validator> <validator-id>org.richfaces.validator.SelectLabelValueValidator</validator-id> <validator-class>org.richfaces.validator.SelectLabelValueValidator</validator-class> </validator> {code} Workaround: Workaround Exists > 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: SelectLabelValueValidator, missing, 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, 4 months

1
0
0 / 0

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

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12692?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12692: --------------------------------- Hey Erdem, there must be problem with auto-discovery of [{{@FacesValidator}} annotation on SelectLabelValueValidator class|https://github.com/richfaces/components/blob/develop/input/ui/src/m...]. in your environment. You can work around this problem with manually registering validator in {{faces-config.xml}} - see workaround description above. To avoid such problems, I will take more defensive approach and I will use RichFaces {{faces-config.xml}} to register this validator instead of using annotation. > 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: SelectLabelValueValidator, missing, 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-11565) Showcase: multiple selections in rich:autocomplete doesn't work when "clicking" is used

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-11565?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-11565: --------------------------------- Fixed in {{develop}}. QE: Could you please verify that it works for all supported browsers? > Showcase: multiple selections in rich:autocomplete doesn't work when "clicking" is used > --------------------------------------------------------------------------------------- > > Key: RF-11565 > URL: https://issues.jboss.org/browse/RF-11565 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.1.0.Milestone3, 4.2.3.CR1, 4.3.0.M3 > Environment: iPhone 4 (Safari) > Nexus (Android 2.3.6) > Google Chrome 12.0.742.112 > Reporter: Jan Papousek > Assignee: Lukáš Fryč > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > The second a third autocomplete input in Showcase demo http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=autoco... [1] doesn't work properly on the mentioned browsers/devices: > # type "Al" > # select "Alabama" -> input field is containing "Alabama" > # type ", P" > # select "Pennsylvania" with mouse/finger -> input field is containing "Pennsylvania, P" (it should contain "Alabama, Pennsylvania") > The Safari developer's console on iPhone doesn't display any error. > It works properly on: > - Opera 11.50 > - Firefox 6.0 > [1] http://10.0.2.2:8080/showcase/#autocomplete:modes in movile 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-11565) Showcase: multiple selections in rich:autocomplete doesn't work when "clicking" is used

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-11565?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-11565. ----------------------------- Resolution: Done > Showcase: multiple selections in rich:autocomplete doesn't work when "clicking" is used > --------------------------------------------------------------------------------------- > > Key: RF-11565 > URL: https://issues.jboss.org/browse/RF-11565 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.1.0.Milestone3, 4.2.3.CR1, 4.3.0.M3 > Environment: iPhone 4 (Safari) > Nexus (Android 2.3.6) > Google Chrome 12.0.742.112 > Reporter: Jan Papousek > Assignee: Lukáš Fryč > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > The second a third autocomplete input in Showcase demo http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=autoco... [1] doesn't work properly on the mentioned browsers/devices: > # type "Al" > # select "Alabama" -> input field is containing "Alabama" > # type ", P" > # select "Pennsylvania" with mouse/finger -> input field is containing "Pennsylvania, P" (it should contain "Alabama, Pennsylvania") > The Safari developer's console on iPhone doesn't display any error. > It works properly on: > - Opera 11.50 > - Firefox 6.0 > [1] http://10.0.2.2:8080/showcase/#autocomplete:modes in movile 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12522) rich:editor - submitting leads to javascript error

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12522?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12522: ---------------------------- Fix Version/s: (was: 4.3.0.CR1) > rich:editor - submitting leads to javascript error > -------------------------------------------------- > > Key: RF-12522 > URL: https://issues.jboss.org/browse/RF-12522 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.CR1 > Environment: RichFaces 4.2.3.CR1 > Metamer 4.2.3.20121004-CR1 > Unknown version of JSF > JBoss AS 7.1.1.Final / Apache Tomcat 7.0.30 > Java(TM) SE Runtime Environment 1.7.0_07-b10 @ Linux > Firefox 15.0.1 @ Linux x86_64 > Reporter: Jan Papousek > Assignee: Juraj Húska > Attachments: rich_editor.png > > > It works correctly on IE 8. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12447) Editor: color picking doesn't work in Internet Explorer 10

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12447?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12447: ---------------------------- CKEditor {{3.6.6}} is avialable for download now. > Editor: color picking doesn't work in Internet Explorer 10 > ---------------------------------------------------------- > > Key: RF-12447 > URL: https://issues.jboss.org/browse/RF-12447 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.2.Final, 4.3.0.M1 > Environment: RichFaces 4.2.2.Final, 4.3.0.M1 > Internet Explorer 10 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Labels: waiting_on_upstream > Fix For: 4.3.0.CR1 > > Attachments: editor-ie10.png > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > # open Showcase http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=editor&... > # open developers tools and change document mode to "Standards" > # try to change color of title > result: > * popup for color chooser is misplaced > * when a color is selected, nothing happens > * there are JavaScript errors in the console > * works fine when document mode is set to "IE8 standards" -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12447) Editor: color picking doesn't work in Internet Explorer 10

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12447?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-12447: ------------------------------- Assignee: Lukáš Fryč > Editor: color picking doesn't work in Internet Explorer 10 > ---------------------------------------------------------- > > Key: RF-12447 > URL: https://issues.jboss.org/browse/RF-12447 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.2.Final, 4.3.0.M1 > Environment: RichFaces 4.2.2.Final, 4.3.0.M1 > Internet Explorer 10 > Reporter: Pavol Pitonak > Assignee: Lukáš Fryč > Labels: waiting_on_upstream > Fix For: 4.3.0.CR1 > > Attachments: editor-ie10.png > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > # open Showcase http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=editor&... > # open developers tools and change document mode to "Standards" > # try to change color of title > result: > * popup for color chooser is misplaced > * when a color is selected, nothing happens > * there are JavaScript errors in the console > * works fine when document mode is set to "IE8 standards" -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-10853) dataScroller: do not works with a4j:status properly

by nimo stephan (JIRA)

[ https://issues.jboss.org/browse/RF-10853?page=com.atlassian.jira.plugin.s... ] nimo stephan commented on RF-10853: ----------------------------------- I have also this issue: onstart is called, but onstop not. But my usecase is a little different: <h:form id="form"> <a4j:status onstart="#{rich:component('splash')}.show()" onstop="#{rich:component('splash')}.hide()" /> <h:panelGroup id="myPanel"> <a4j:commandButton id="myAction" action=".." render="myPanel"></a4j:commandButton> </h:panelGroup> </h:form> So you see, I render mypanel after clicking myAction. The onstop is never called. > dataScroller: do not works with a4j:status properly > --------------------------------------------------- > > Key: RF-10853 > URL: https://issues.jboss.org/browse/RF-10853 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: base functionality , component-tables > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Fix For: 5-Tracking > > > 1) do not works properly with form scoped default status. onstart called but onstop - not. > Problem seems in dataScroller because the same case with the button works see [1] > 2) do not works at all using status="status". Seems just not implemented. > [1] > {code} > // > <rich:popupPanel id="splash" autosized="true" width="200" height="80" moveable="false" resizeable="false"> > <f:facet name="header"><h:outputText value="WAIT" /></f:facet> > <h:outputText value="WAIT!" /> > </rich:popupPanel> > <h:form id="form"> > <a4j:status onstart="#{rich:component('splash')}.show()" onstop="#{rich:component('splash')}.hide()" /> > <h:panelGrid columnClasses="acent"> > <rich:dataScroller for="table" maxPages="5" /> > <rich:dataTable value="#{carsBean.allInventoryItems}" var="car" > id="table" rows="#{userBean.age}"> > ................ > </rich:dataTable> > <rich:dataScroller for="table" maxPages="5" status="status"/> > </h:panelGrid> > <a4j:commandButton ></a4j:commandButton> > </h:form> > {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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12694) <rich:dropDownMenu> throwing a warning: "Cannot set header. Response already committed."

by Srinivas Reddy Malipeddi (JIRA)

[ https://issues.jboss.org/browse/RF-12694?page=com.atlassian.jira.plugin.s... ] Srinivas Reddy Malipeddi commented on RF-12694: ----------------------------------------------- Myfaces 2.0.2, IBM implementation. I did not check for Mojarra. I will check and let you know Thanks Srinivas > <rich:dropDownMenu> throwing a warning: "Cannot set header. Response already committed." > ---------------------------------------------------------------------------------------- > > Key: RF-12694 > URL: https://issues.jboss.org/browse/RF-12694 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.3.Final > Environment: Tested in Galssfish3.1 and WAS8 > Reporter: Srinivas Reddy Malipeddi > Priority: Minor > Labels: richfaces, waiting_on_user > > When rich component like <rich:dropDownMenu is used, throwing warning" > {quote} > com.ibm.ws.webcontainer.srt.SRTServletResponse setIntHeader SRVE8094W: WARNING: Cannot set header. Response already committed. > {quote} > Project details: JSF2.0, Myfaces implementation, richfaces 4.2.3 jars > My project have only one page index.xhtml with one component like below. If richfaces component is not used then the warning is not coming. > {code:title=index.xhtml} > <?xml version="1.0" encoding="UTF-8" ?> > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:rich="http://richfaces.org/rich"> > <h:head> > > </h:head> > <h:body> > <rich:dropDownMenu label="IT Asset"> > <rich:menuItem label="Search" /> > <rich:menuItem label="Create" /> > </rich:dropDownMenu> > </h:body> > </ui:composition> > {code} > {code:title=Web.xml} > <?xml version="1.0" encoding="UTF-8"?> > <web-app id="WebApp_ID" version="3.0" > xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"> > <display-name>TestWeb</display-name> > <context-param> > <description> > The location where state information is saved. > Valid values are 'server' (typically saved in HttpSession) and 'client' (typically > saved as a hidden field in the form. > Default is server.</description> > <param-name>javax.faces.STATE_SAVING_METHOD</param-name> > <param-value>server</param-value> > </context-param> > <context-param> > <description> > Comma-delimited list of context-relative resource paths under which the JSF implementation > will look for application configuration resources, before loading a configuration resource > named /WEB-INF/faces-config.xml (if such a resource exists).</description> > <param-name>javax.faces.CONFIG_FILES</param-name> > <param-value></param-value> > </context-param> > <context-param> > <description> > The default suffix for extension-mapped resources that contain JSF components. > Default is '.jsp'.</description> > <param-name>javax.faces.DEFAULT_SUFFIX</param-name> > <param-value>.xhtml</param-value> > </context-param> > <context-param> > <description> > A human readable string describing where this particular JSF application is > in the software development lifecycle. > Valid values are 'Development', 'UnitTest', 'SystemTest' and 'Production'. > Default is 'Production'. > This parameter is not available in JSF 1.x.</description> > <param-name>javax.faces.PROJECT_STAGE</param-name> > <param-value>Development</param-value> > </context-param> > <context-param> > <description> > Monitors Faces JSP files for modifications and synchronizes a running server with > the changes without restarting the server. If this parameter is set to false or > removed from the deployment descriptor, any changes made to Faces JSP files may > not be seen by the server until it is restarted. This parameter is usually set > to true while the Faces JSP files are being developed and debugged in order to > improve the performance of the development environment.</description> > <param-name>com.ibm.ws.jsf.JSP_UPDATE_CHECK</param-name> > <param-value>true</param-value> > </context-param> > <context-param> > <description> > Load JSF runtime when the application server starts up. If this parameter is set to false or removed, > JSF runtime will be loaded and initialized when the first JSF request is processed. > This may disable custom JSF extensions, such as factories defined in the project.</description> > <param-name>com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP</param-name> > <param-value>true</param-value> > </context-param> > > <servlet> > <servlet-name>Faces Servlet</servlet-name> > <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> > <load-on-startup>-1</load-on-startup> > <enabled>true</enabled> > <async-supported>false</async-supported> > </servlet> > <servlet-mapping> > <servlet-name>Faces Servlet</servlet-name> > <url-pattern>*.xhtml</url-pattern> > </servlet-mapping> > <servlet-mapping> > <servlet-name>Faces Servlet</servlet-name> > <url-pattern> > *.faces</url-pattern> > </servlet-mapping> > <servlet-mapping> > <servlet-name>Faces Servlet</servlet-name> > <url-pattern> > /faces/*</url-pattern> > </servlet-mapping> > <welcome-file-list> > <welcome-file>index.xhtml</welcome-file> > </welcome-file-list> > </web-app> > {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

11 years, 4 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