August 2011 - richfaces-issues - Jboss List Archives

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

by Ilya Shaikovsky (JIRA)

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: component-tables Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky 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] <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> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-11111) <a4j:status> for <rich:tree> works on selecting a node; not on toggling (via Ajax) in RF4.0.0

by Bastian Ulke (JIRA)

<a4j:status> for <rich:tree> works on selecting a node; not on toggling (via Ajax) in RF4.0.0 --------------------------------------------------------------------------------------------- Key: RF-11111 URL: https://issues.jboss.org/browse/RF-11111 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Final Environment: WinXP; 6.0.0.Final; RichFaces 4.0.0 Reporter: Bastian Ulke I have got the following tree: <rich:tree var="item" id="someTree" selectionType="ajax" toggleType="ajax" treeSelectionChangeListener="#{someBean.selectionChanged}" selectionChangeListener="#{someBean.selectionChanged}"> <rich:treeModelRecursiveAdaptor roots="#{someBean.entities}" nodes="#{someBean.getSomeSubItems(item.id)}"> <rich:treeNode> <a4j:outputPanel> <h:outputText value="#{item.fullName}" /> </a4j:outputPanel> </rich:treeNode> </rich:treeModelRecursiveAdaptor> </rich:tree> And a status indicator: <a4j:status layout="block" startStyleClass="startAjax" > <f:facet name="start"> <img src="ajax-loader.gif" /> </f:facet </a4j:status> The combination works well for selecting (!) a node: When the AJAX-request is sent, it displays the gif, when it is received, it is removed. Unfortunatly, when performing a toggle on a node, the gif is displayed but never removed, although the data is correctly received and the view is updated. I added some alert('..') messages for the on{success|error|stop}-Properties of the <a4j:status> - same again: well fired for the selection of a particular node; but none ever executed for toggling. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (RF-11125) a4j:ajax listener method expression behaves differently for one or zero parameter methods

by James G (JIRA)

a4j:ajax listener method expression behaves differently for one or zero parameter methods ----------------------------------------------------------------------------------------- Key: RF-11125 URL: https://issues.jboss.org/browse/RF-11125 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Final Environment: MyFace 2.0.7, Tomcat 6, Richfaces 4.0 Reporter: James G When using a4j:ajax and setting the listener to a bean method, the call works correctly if the bean method has one parameter of type AjaxBehaviorEvent. If the method has no parameters then it may not be called correctly. This situation occurs if the method expression uses a variable scoped in facelets. For example using a ui:param under a ui:decorate. The method expression for one parameter is created using a call to ExpressionFactory.createMethodExpression( faceletContext, ... ) but the method expression for zero parameters is created using ExpressionFactory.createMethodExpression( elContext, ... ). The elContext does not contain the facelet variable mapping and so will not impart this to the method expression. This needs to be refactory to pass in the faceletContext when creating the zero parameter method expression. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-11134) ComponentIdResolver does not resolve clientId correctly

by Val Blant (JIRA)

ComponentIdResolver does not resolve clientId correctly ------------------------------------------------------- Key: RF-11134 URL: https://issues.jboss.org/browse/RF-11134 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Final Reporter: Val Blant Please consider the following test code: {code} <rich:dataTable id="testTable" value="#{dataTableTestBackingBean.rowsModel}" var="rowVar"> <f:facet name="header"> <rich:column> <h:outputText value="Column 1" /> </rich:column> </f:facet> <rich:column> <h:inputText id="valTest" value="#{rowVar.col1}" > <a4j:ajax event="blur" render="testColumn, footerTest" limitRender="true" execute="@this" /> </h:inputText> </rich:column> <rich:column> <h:outputText id="testColumn" value="#{dataTableTestBackingBean.footerValue}" /> </rich:column> <f:facet name="footer"> <rich:column> <h:outputText id="footerTest" value="#{dataTableTestBackingBean.footerValue}" /> </rich:column> </f:facet> </rich:dataTable> {code} This example will fail with the following Javascript error in the browser: {color:red} {quote} Error: During update: formId:testTable:0:footerTest not found {quote} {color} This is expected, b/c the correct id for the footer is _formId:testTable:footerTest_. The bug is in _org.richfaces.context.ComponentIdResolver_. Here is what happens: # The _RenderComponentCallback_ is executed on the input component (_'valTest'_ in the example) and it reads the list of short ids to render from the attached Ajax Behavior. Note that we got here by walking the parent data table model, so the current rowKey is 0 # _RenderComponentCallback_ asks _ComponentIdResolver_ to resolve short ids into client IDs # _ComponentIdResolver_ starts ascending up the tree from _'valTest'_ and looking at facets and children until it finds _'footerTest'_. # At this point it asks for the clientId of _'footerTest'_ w/o regard for the fact that the data model has a rowKey that is set 0 So, we get the wrong id b/c we call UiData.getClientId() outside of the normal walking order of that model. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (RF-11168) PickList component should support client side validation for required=true

by Brian Leathem (JIRA)

PickList component should support client side validation for required=true -------------------------------------------------------------------------- Key: RF-11168 URL: https://issues.jboss.org/browse/RF-11168 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Milestone1 Reporter: Brian Leathem The PickList component does not currently support client side validation for required = true -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-11321) Input Number Slider - placed in Popup Panel - moving the slider with mouse

by Jan Papousek (JIRA)

Input Number Slider - placed in Popup Panel - moving the slider with mouse --------------------------------------------------------------------------- Key: RF-11321 URL: https://issues.jboss.org/browse/RF-11321 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Milestone1 Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc Metamer 4.1.0-SNAPSHOT r.22637 Mojarra 2.1.2-FCS Apache Tomcat 6.0.32 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Firefox 5.0 @ Linux x86_64 Reporter: Jan Papousek When the rich:inputNumberSlider is placed in rich:popupPanel, it can't be moved correctly with mouse. This can be reproduced in Metamer - faces/components/richInputNumberSlider/simple.xhtml (select 'Rich Popup Panel' template in the top menu and click on 'Load'). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (RF-11092) rich:autocomplete - attribute tabindex doesn't work

by Rene O (JIRA)

rich:autocomplete - attribute tabindex doesn't work --------------------------------------------------- Key: RF-11092 URL: https://issues.jboss.org/browse/RF-11092 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Milestone1 Environment: latest richfaces-4.1.0-SNAPSHOT, IE8, Firefox5, Chrome Reporter: Rene O code-snippet to reproduce the issue: ... <h:form id="testForm"> <h:inputText value="" tabindex="1" /> <rich:autocomplete value="" ... tabindex="2" /> <h:inputText value="" tabindex="3" /> </h:form> ... If you tab from inputText1, inputText2 will gain the focus, instead of the autocomplete component -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
4
0 / 0

[JBoss JIRA] Created: (RF-10976) EDT columns cant be resized

by Lukáš Fryč (JIRA)

EDT columns cant be resized --------------------------- Key: RF-10976 URL: https://issues.jboss.org/browse/RF-10976 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Final Environment: RichFaces 4.1.0-SNAPSHOT r.22477 MEtamer 4.1.0-SNAPSHOT r.22479 Mojarra 2.0.4-b09 Apache Tomcat 6.0.29 OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux Chrome 11.0.696.57 @ Linux i686 Firefox 4.0 Reporter: Lukáš Fryč -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (RF-11118) Write unit tests

by Brian Leathem (JIRA)

Write unit tests ---------------- Key: RF-11118 URL: https://issues.jboss.org/browse/RF-11118 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: component-selects Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.0.1.Milestone1 Write appropriate unit tests -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (RF-11049) Write server side unit tests for Editor

by Lukáš Fryč (JIRA)

Write server side unit tests for Editor --------------------------------------- Key: RF-11049 URL: https://issues.jboss.org/browse/RF-11049 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: component-input, tests - unit Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.0.Milestone1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2011