July 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12613) rich:select with enablemanualinput selects wrong items

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12613?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12613: ---------------------------- Fix Version/s: 4.5.0.Alpha1 (was: 5-Tracking) > rich:select with enablemanualinput selects wrong items > ------------------------------------------------------ > > Key: RF-12613 > URL: https://issues.jboss.org/browse/RF-12613 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final, 4.3.0.M2 > Reporter: geert olaerts > Fix For: 4.5.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > When using rich:select with enablemanualinput = "true", the wrong item might be selected. If the list of possible items is (in this order): "test test" and "test" and the user selects "test" richfaces will select "test test" as input. The same happens if the user types "test". If the list is "test" and "test test" and the user selects or types "test" the correct item is selected. -- 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-13101) rich:select Method getSelectInputLabel is not working when using objects

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13101?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13101: ---------------------------- Fix Version/s: 4.5.0.Alpha1 > rich:select Method getSelectInputLabel is not working when using objects > ------------------------------------------------------------------------ > > Key: RF-13101 > URL: https://issues.jboss.org/browse/RF-13101 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, component-selects > Affects Versions: 4.3.2, 5.0.0.Alpha1 > Reporter: J W > Labels: rich:select, select > Fix For: 4.5.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The condition of the if-statement in org.richfaces.renderkit.SelectHelper.getSelectInputLabel(FacesContext facesContext, UIComponent component) is not working with the string-representations of the items. If using cloned objects the equals method will return false, even if the items are the same, because the IDs are different. > The method should use only the strings of the objects, similiar to how MyFaces has solved this (check workarround). -- 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-13102) rich:calendar with date pattern- input gets cleared on click

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/RF-13102?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev updated RF-13102: ------------------------------- Assignee: Brian Leathem > rich:calendar with date pattern- input gets cleared on click > ------------------------------------------------------------ > > Key: RF-13102 > URL: https://issues.jboss.org/browse/RF-13102 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.Final, 4.3.2 > Reporter: Jonáš Trantina > Assignee: Brian Leathem > > When a rich:calendar component has datePattern without a day (e.g. MM/yyyy) then selected date is cleared when opening the calendar (you can see today date instead of the previously selected date). > However, when the form is sent, the value is correctly assigned to the binded value. > Example: > {noformat} > <rich:calendar value="#{richBean.date}" datePattern="yyyy-MM"/> > {noformat} -- 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-12950) Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on RF-12950 at 7/26/13 9:49 AM: ----------------------------------------------------------- Rejecting pull request, because I forget that it depends on richfaces-qa repository. This will be solved once page fragments are moved to different repository (RF-12802) as well as XHRHalter. Then we can proceed with this showcase-ftest migrating. was (Author: jhuska): Rejecting pull request, because I forget that it depends on richfaces-qa repository. This will be solved once page fragments are moved to different repository as well as XHRHalter. Then we can proceed with this showcase-ftest migrating. > Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests > ------------------------------------------------------------------------------------------------------ > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Lukáš Fryč > Assignee: Juraj Húska > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- 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-12950) Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on RF-12950 at 7/26/13 9:50 AM: ----------------------------------------------------------- Rejecting pull request, because I forget that it depends on richfaces-qa repository. This will be solved once * page fragments are moved to different repository (RF-12802) * as well as XHRHalter to {{build-resources}}. Then we can proceed with this showcase-ftest migrating. was (Author: jhuska): Rejecting pull request, because I forget that it depends on richfaces-qa repository. This will be solved once page fragments are moved to different repository (RF-12802) as well as XHRHalter. Then we can proceed with this showcase-ftest migrating. > Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests > ------------------------------------------------------------------------------------------------------ > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Lukáš Fryč > Assignee: Juraj Húska > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- 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-12950) Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.s... ] Juraj Húska updated RF-12950: ----------------------------- Git Pull Request: (was: https://github.com/richfaces/richfaces/pull/43) > Move Showcase ftests from QA repo to the examples/showcase module and mark some of them as smoke tests > ------------------------------------------------------------------------------------------------------ > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Lukáš Fryč > Assignee: Juraj Húska > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- 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-13108) rich:calendar nested a4j:ajax event not firing

by nathan dennis (JIRA)

nathan dennis created RF-13108: ---------------------------------- Summary: rich:calendar nested a4j:ajax event not firing Key: RF-13108 URL: https://issues.jboss.org/browse/RF-13108 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core, component-validators Affects Versions: 4.3.2 Environment: jboss 7.1.3 richfaces 4.3.2.final, chrome Reporter: nathan dennis nested a4j:ajax change event isn't functioning as expected. ajax event isn't always fired. after speaking with ppitonak it seemed as if the order of the ajax with relation to the validators was import. however after closer inspection (and may be a different problem), the value wasnt making back to the bean even when the event was fired. {code:xml} <?xml version='1.0' encoding='UTF-8' ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich" template="/resources/scaffold/pageTemplate.xhtml"> <f:metadata> <f:viewParam name="id" value="#{screeningBean.id}"/> </f:metadata> <ui:define name="main"> <h:form id="create"> <h:panelGrid columnClasses="label,component,required" columns="3"> <h:outputLabel for="startTimeOverride" value="Start Time Override:"/> <rich:calendar value="#{screeningBean.screening.beginTime}" id="startTimeOverride" popup="true" datePattern="dd/M/yy hh:mm a" required="true" showApplyButton="true" > <f:validateRequired /> <a4j:ajax event="change" bypassUpdates="#{true}"/> </rich:calendar> <rich:message for="startTimeOverride" ajaxRendered="true" /> <h:outputLabel for="endTimeOverride" value="End Time Override:" /> <rich:calendar value="#{screeningBean.screening.endTime}" id="endTimeOverride" popup="true" datePattern="dd/M/yy hh:mm a" showApplyButton="true" > <f:validateRequired /> <f:validator validatorId="dateRangeValidator" /> <rich:validator /> <a4j:ajax event="change" bypassUpdates="#{true}"/> </rich:calendar> <rich:message for="endTimeOverride" ajaxRendered="true" /> </h:panelGrid> <div class="buttons"> <a4j:commandButton value="Complete" action="#{screeningBean.updateScreening(2)}" execute="@form" onclick="this.disabled=true; var that = this; setTimeout(function() that.disabled=false;},500);" styleClass="btn btn-primary btn-primary-a4j" /> </div> </h:form> </ui:define> </ui:composition> {code} {code:title=DateRangeValidator.java} /************************************************************** * Copyright (c) 2012 - 2013, Monarch, All rights reserved. * * @author Nathan Dennis * */ package org.monarchnc.view.validators; import java.text.DateFormat; import java.text.SimpleDateFormat; import java.util.Date; import javax.faces.application.FacesMessage; import javax.faces.component.UIComponent; import javax.faces.component.UIInput; import javax.faces.context.FacesContext; import javax.faces.validator.FacesValidator; import javax.faces.validator.Validator; import javax.faces.validator.ValidatorException; import javax.persistence.EntityManager; import org.apache.deltaspike.core.api.provider.BeanProvider; import org.monarchnc.view.ScreeningBean; // TODO: Auto-generated Javadoc /** * The Class DateRangeValidator. */ @FacesValidator("dateRangeValidator") public class DateRangeValidator implements Validator { /* (non-Javadoc) * @see javax.faces.validator.Validator#validate(javax.faces.context.FacesContext, javax.faces.component.UIComponent, java.lang.Object)f */ public void validate(final FacesContext ctx, final UIComponent component, final Object value) throws ValidatorException { ScreeningBean screeningBean = BeanProvider.getContextualReference(screeningBean.class, false); Date date =(Date) value; if(screeningBean.getScreening().getBeginTime() != null && date != null) if(!date.after(screeningBean.getScreening().getBeginTime())){ throw new ValidatorException(new FacesMessage(FacesMessage.SEVERITY_ERROR,"End Date must be after Start Date!!.\n","End Date must be after Start Date!!\n")); } } } {code} {code:title=ScreeningBean.java} @Named @Transactional @ConversationScoped public class ScreeningBean implements Serializable{ Screening screening = new Screening(); public Class<? extends ViewConfig> claim(){ if (this.conversation.isTransient()) { this.conversation.begin(); }... } public Screening getScreening() { return screening; } public void setScreening(Screening screening) { this.screening = screening; } } {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-13102) rich:calendar with date pattern- input gets cleared on click

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-13102?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-13102: ---------------------------------------------- Jonáš Trantina <jtrantin(a)redhat.com> made a comment on [bug 988405|https://bugzilla.redhat.com/show_bug.cgi?id=988405] Mixed up Actual and Expected results, correct version: Actual results: Today date is selected and input is cleared. Expected results: Previously chosen date should be selected in the calendar, the date should stay in the input. > rich:calendar with date pattern- input gets cleared on click > ------------------------------------------------------------ > > Key: RF-13102 > URL: https://issues.jboss.org/browse/RF-13102 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.Final, 4.3.2 > Reporter: Jonáš Trantina > > When a rich:calendar component has datePattern without a day (e.g. MM/yyyy) then selected date is cleared when opening the calendar (you can see today date instead of the previously selected date). > However, when the form is sent, the value is correctly assigned to the binded value. > Example: > {noformat} > <rich:calendar value="#{richBean.date}" datePattern="yyyy-MM"/> > {noformat} -- 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-13102) rich:calendar with date pattern- input gets cleared on click

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-13102?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-13102: ---------------------------------------------- Jonáš Trantina <jtrantin(a)redhat.com> made a comment on [bug 988405|https://bugzilla.redhat.com/show_bug.cgi?id=988405] Description of problem: When a rich:calendar component has datePattern without a day (e.g. MM/yyyy) then selected date is cleared when opening the calendar (you can see today date instead of the previously selected date). However, when the form is sent, the value is correctly assigned to the binded value. Example: <rich:calendar value="#{richBean.date}" datePattern="yyyy-MM"/> Version-Release number of selected component (if applicable): How reproducible: Create a project with the tag from above. Steps to Reproduce: 1. Open the page with the calendar tag 2. Select some date 3. Click on the input to open up the calendar, the input gets clear, today date is selected Actual results: Previously chosen date should be selected in the calendar, the date should stay in the input. Expected results: Today date is selected and input is > rich:calendar with date pattern- input gets cleared on click > ------------------------------------------------------------ > > Key: RF-13102 > URL: https://issues.jboss.org/browse/RF-13102 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.Final, 4.3.2 > Reporter: Jonáš Trantina > > When a rich:calendar component has datePattern without a day (e.g. MM/yyyy) then selected date is cleared when opening the calendar (you can see today date instead of the previously selected date). > However, when the form is sent, the value is correctly assigned to the binded value. > Example: > {noformat} > <rich:calendar value="#{richBean.date}" datePattern="yyyy-MM"/> > {noformat} -- 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-13102) rich:calendar with date pattern- input gets cleared on click

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-13102?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated RF-13102: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=988405 > rich:calendar with date pattern- input gets cleared on click > ------------------------------------------------------------ > > Key: RF-13102 > URL: https://issues.jboss.org/browse/RF-13102 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.Final, 4.3.2 > Reporter: Jonáš Trantina > > When a rich:calendar component has datePattern without a day (e.g. MM/yyyy) then selected date is cleared when opening the calendar (you can see today date instead of the previously selected date). > However, when the form is sent, the value is correctly assigned to the binded value. > Example: > {noformat} > <rich:calendar value="#{richBean.date}" datePattern="yyyy-MM"/> > {noformat} -- 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 July 2013