December 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-8149) Demo: Ajax Validator -- Bean Validator could not be instantiated

by Pavol Pitonak (JIRA)

Demo: Ajax Validator -- Bean Validator could not be instantiated ---------------------------------------------------------------- Key: RF-8149 URL: https://jira.jboss.org/jira/browse/RF-8149 Project: RichFaces Issue Type: Bug Components: examples Affects Versions: 3.3.3.BETA1 Environment: Linux, Tomcat 6.0.20, RF 3.3.3-SNAPSHOT (Revision: 15940) Reporter: Pavol Pitonak In richfaces-demo, page Ajax Validator it throws an exception to server's console after typing "a" into name field and clicking into age field. Nov 20, 2009 11:02:37 AM org.richfaces.validator.ObjectValidator createInstance WARNING: Bean Validator could not be instantiated javax.validation.ValidationException: Unable to find a default provider at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:264) at javax.validation.Validation.buildDefaultValidatorFactory(Validation.java:111) at org.richfaces.validator.BeanValidator.<init>(BeanValidator.java:35) at org.richfaces.validator.ObjectValidator.createInstance(ObjectValidator.java:54) at org.richfaces.validator.ObjectValidator.getInstance(ObjectValidator.java:85) at org.richfaces.validator.FacesBeanValidator.validate(FacesBeanValidator.java:104) at org.richfaces.component.html.HtmlInputText.validateValue(HtmlInputText.java:52) at javax.faces.component.UIInput.validate(UIInput.java:875) at javax.faces.component.UIInput.executeValidate(UIInput.java:1072) at javax.faces.component.UIInput.processValidators(UIInput.java:672) at org.ajax4jsf.component.AjaxViewRoot$3.invokeContextCallback(AjaxViewRoot.java:442) at org.ajax4jsf.component.ContextCallbackWrapper.invokeContextCallback(ContextCallbackWrapper.java:44 Does it something in common with https://jira.jboss.org/jira/browse/RF-7226 ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

6
7
0 / 0

[JBoss JIRA] Created: (RF-8179) extendeDataTable: can't select all the rows using shift

by Ilya Shaikovsky (JIRA)

extendeDataTable: can't select all the rows using shift ------------------------------------------------------- Key: RF-8179 URL: https://jira.jboss.org/jira/browse/RF-8179 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 3.3.3.BETA1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski info at forum. checked that reproduces and not a regerssion. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-8188) rf-demo ftest - add cmd-line parameter for focusing and maximizing selenium window

by Lukas Fryc (JIRA)

rf-demo ftest - add cmd-line parameter for focusing and maximizing selenium window ---------------------------------------------------------------------------------- Key: RF-8188 URL: https://jira.jboss.org/jira/browse/RF-8188 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: QA-environment Reporter: Lukas Fryc Assignee: Lukas Fryc Priority: Optional There is need for cmd-line parameter intended to debugging since in hudson environment (xvnc display) is created windows too small and makes difficult to be debugged. We need to add selenium.windowMaximize() selenium.windowFocus() before each test method to satisfy that we can watch the progress of tests. Integrate new parameter to maven pom and implement method which will test this parameter inside tests. Modify all hudson jobs to follow this parameter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-8209) inputNumberSlider: onchange event - this passed to handler should be input and not slider object as for any other inputs.

by Ilya Shaikovsky (JIRA)

inputNumberSlider: onchange event - this passed to handler should be input and not slider object as for any other inputs. ------------------------------------------------------------------------------------------------------------------------- Key: RF-8209 URL: https://jira.jboss.org/jira/browse/RF-8209 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 3.3.2.SR1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Priority: Optional <rich:inputNumberSlider id="slider" > <a4j:support event="onchange" onsubmit="myFunc(this, event)" requestDelay="1000" reRender="part" /> </rich:inputNumberSlider> <rich:calendar > <a4j:support event="onchanged" onsubmit="myFunc(this,event)" requestDelay="1000" reRender="part" /> </rich:calendar> <h:inputText value="" > <a4j:support event="onchange" onsubmit="myFunc(this,event)" requestDelay="1000" reRender="part" /> </h:inputText> for inputText and calendar - this passed as input DOM element and for slider - passed as slider object. so I can't get form as usually using this.form -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-8208) in 3.3.0 extendedDataTable does not provide a method to hide/disable the grouping menu

by uwe albert (JIRA)

in 3.3.0 extendedDataTable does not provide a method to hide/disable the grouping menu -------------------------------------------------------------------------------------- Key: RF-8208 URL: https://jira.jboss.org/jira/browse/RF-8208 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 3.3.0 Reporter: uwe albert in 3.3.0 extendedDataTable does not provide a method to hide/disable the grouping menu the attribute "enableContextMenu" does not work (probabely it is not meant for hiding the grouping menu) To us it is important to disable the grouping -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-8173) Regression: Calendar: converter is not working

by Joseph Miller (JIRA)

Regression: Calendar: converter is not working ---------------------------------------------- Key: RF-8173 URL: https://jira.jboss.org/jira/browse/RF-8173 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input, regression Affects Versions: 3.3.2.SR1 Environment: JBoss 5.0 / Seam 2.1.2.GA Reporter: Joseph Miller I have a model property with is a Joda LocalDate. For normal input fields, I have a converter, which is working fine. However, when I try to use the converter with rich:calendar, it complains: <rich:calendar id="from" locale="AU" showApplyButton="false" popup="true" enableManualInput="true" datePattern="dd/MM/yyyy" value="#{adviserAvailability.validFrom}"> <f:converter converterId="localDateConverter" /> </rich:calendar> javax.faces.convert.ConverterException: Value must be a date at javax.faces.convert.DateTimeConverter.getAsObject(DateTimeConverter.java:401) at org.richfaces.component.UICalendar.getAsDate(UICalendar.java:399) at org.richfaces.component.UICalendar.getAsDate(UICalendar.java:410) at org.richfaces.component.UICalendar.getCurrentDateOrDefault(UICalendar.java:374) at org.richfaces.renderkit.html.CalendarRenderer.doEncodeEnd(CalendarRenderer.java:381) at org.richfaces.renderkit.html.CalendarRenderer.doEncodeEnd(CalendarRenderer.java:531) at org.ajax4jsf.renderkit.RendererBase.encodeEnd(RendererBase.java:134) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:861) ... I'm defining the converter as such: @Name( "localDateConverter" ) @BypassInterceptors @Converter( forClass = LocalDate.class, id = "localDateConverter") public class LocalDateConverter implements javax.faces.convert.Converter { public Object getAsObject( ... ) { .... } public String getAsString( ... ) { .... } } If I turn the property into a Date by using: value="#{adviserAvailability.validFrom.toDateMidnight().toDate()}" I get a conversion error, as I would expect from with LocalDateConverter.getAsObject, so it's definitely being made available. I get the same issue regardless of if I use <f:converter> or the converter attribute of <rich:calendar> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

5
11
0 / 0

[JBoss JIRA] Created: (RF-8203) Extensive memory usage for a4j:support component under JSF 2.0

by Nick Belaevski (JIRA)

Extensive memory usage for a4j:support component under JSF 2.0 -------------------------------------------------------------- Key: RF-8203 URL: https://jira.jboss.org/jira/browse/RF-8203 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component, JSF 2.0, performance Affects Versions: 3.3.3.BETA1 Reporter: Nick Belaevski Assignee: Nick Belaevski Priority: Critical Fix For: 3.3.3.BETA1 Extensive memory usage is reproducible for RF 3.3.x running under JSF 2.0 when a4j:support is used. Heap analysis shows that org.ajax4jsf.component.EventValueExpression is stored in session (as part of component tree state) holding active references to view components, thus not allowing component tree to be reclaimed by GC. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (RF-3453) rich:modalPanel does not work with event listeners added using a4j:support

by Paul Speijers (JIRA)

rich:modalPanel does not work with event listeners added using a4j:support -------------------------------------------------------------------------- Key: RF-3453 URL: http://jira.jboss.com/jira/browse/RF-3453 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.5, 3.1.x Reporter: Paul Speijers Fix For: 3.1.6, 3.1.x I wanted to perform some finalization work when I hide a modalPanel and an obvious solution would be to register an action to the onhide event using an a4j:support. However, the action is never executed and it seems like the event listener is not registered with the onhide event. <rich:modalPanel id="#{modalPanelId}" height="600" top="20" left="112" width="900" resizeable="false" moveable="true" onshow="focusFirstModalPanelElement('#{modalPanelId}')"> <a4j:support event="onhide" action="#{modalPanelDelegator.closePanel}" oncomplete="alert('test2')"/> ..... </rich:modalPanel> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (RF-5240) Exception processing in the richfaces custom listeners

by Anton Belevich (JIRA)

Exception processing in the richfaces custom listeners ------------------------------------------------------- Key: RF-5240 URL: https://jira.jboss.org/jira/browse/RF-5240 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.0 Reporter: Anton Belevich Assignee: Anton Belevich Fix For: Future exception which could occur in our listeners should be wrapped with AbortProcessingException (see MethodBindingValueChangeListener, MethodExpressionValueChangeListener for the implementation details) Hint: It's seems we should change componentTag.vm (setProperties) component.vm (getters generation) templates in our component generator for this purpose and implement custom MethodExpressionListeners, MethodBindingListeners like sun do with valueChangeListener, actionListener -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (RF-8170) Extended Data Table : width and Height to 100%

by Nicolas Gaudin (JIRA)

Extended Data Table : width and Height to 100% ---------------------------------------------- Key: RF-8170 URL: https://jira.jboss.org/jira/browse/RF-8170 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Nicolas Gaudin Hi, This would be great that you can include with scrolling features, the possibility to set height to 100%. This missing feature would be greatly appreciated by community I think What do you think... Many thanks in advance Regards -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues December 2009