July 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-10849) RichFaces client-side validation: i variable is implicitly declared

by Ilya Shaikovsky (JIRA)

RichFaces client-side validation: i variable is implicitly declared ------------------------------------------------------------------- Key: RF-10849 URL: https://issues.jboss.org/browse/RF-10849 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky richfaces-csv.js contains variable i declared as global, see method validate(), 174 line, for (i=0;i<validators.length;i++). It should be a local variale. potentially dangerous in case one more js with such mistake will be included to page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-11109) Made Showcase Push demo optional

by Lukáš Fryč (JIRA)

Made Showcase Push demo optional -------------------------------- Key: RF-11109 URL: https://issues.jboss.org/browse/RF-11109 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.0.Milestone1 GAE profile in Showcase is currently not working (RF-11108). Made showcase demo optional with notification that Push is not working on GAE and feature-complete application servers should be used instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (RF-11074) FileUpload ontyperejected not working

by Jesse Bowes (JIRA)

FileUpload ontyperejected not working ------------------------------------- Key: RF-11074 URL: https://issues.jboss.org/browse/RF-11074 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Final Reporter: Jesse Bowes ontyperejected doesn't appear to be working in the 4.0.0.Final Code Snippet: {quote} <rich:fileUpload fileUploadListener="#{bean.listener}" id="upload" acceptedTypes="txt, pdf" ontyperejected="alert('wrong file type');" immediateUpload="true" maxFilesQuantity="10" allowFlash="true"> </rich:fileUpload> {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
14
0 / 0

[JBoss JIRA] Created: (RF-4192) Add "noDataLabel" to rich:dataTable for purposes of display a message if the dataTable is empty

by Chris Simons (JIRA)

Add "noDataLabel" to rich:dataTable for purposes of display a message if the dataTable is empty ----------------------------------------------------------------------------------------------- Key: RF-4192 URL: https://jira.jboss.org/jira/browse/RF-4192 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.2.1, 3.2.0.SR1, 3.2.0, 3.1.6, 3.1.5, 3.1.4 Reporter: Chris Simons Priority: Optional An excellent, small addition to rich:dataTable would allow for a textual message to be displayed in the event that a dataTable is empty. For example: <rich:dataTable id="myTable" noDataLabel="#{messages['dataTable.noData']}" ....> </rich:dataTable> When the condition is true that the underlying data model or list is empty, the message would display in one row that spans the entire dataTable. The headers and dataTable title would still remain. Please vote for this issue if you would like to see this feature added. -- 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

13 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (RF-10439) Introduce SelectionChange API

by Martin Kočí (JIRA)

Introduce SelectionChange API ----------------------------- Key: RF-10439 URL: https://issues.jboss.org/browse/RF-10439 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Milestone5 Environment: RichFaces 4.0 trunk svn rev 21496 Reporter: Martin Kočí Priority: Optional Fix For: 4.Future I don't know if it is intended or not but current RF 4.0 don't have listener/event for API for "SelectionChange" behaviour. Suggestions: 1. introduce SelectionChangeEvent, SelectionChangeListener, SelectionChangeSource API - there is TreeSelectionChangeEvent already - I think the new SelectionChangeEvent can be base class for TreeSelectionChangeEvent 2. add methods addSelectionChangeListener, removeSelectionChangeListener, setSelectionListener(MethodExpression) etc. at UIExtendedDataTable 3. rename client event name from "selectionchange" to "selectionChange" - ValueChange has that convention 4. RC showcase contains selection handling based on AjaxBehaviourEvent -> modify it for r:extendedDataTable selectionChangeListener="#{}" usage -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (RF-10972) Taglib: attributes action and actionListener of tab should be hidden

by Pavol Pitonak (JIRA)

Taglib: attributes action and actionListener of tab should be hidden -------------------------------------------------------------------- Key: RF-10972 URL: https://issues.jboss.org/browse/RF-10972 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.0.0.Final Environment: RichFaces 4.1.0-SNAPSHOT r.22463 Metamer 4.1.0-SNAPSHOT r.22465 Mojarra 2.1.0-FCS GlassFish Server Open Source Edition 3.1 Java(TM) SE Runtime Environment 1.6.0_24-b07 @ Linux Chrome 11.0.696.57 @ Linux i686 Reporter: Pavol Pitonak Component rich:tab should not have attributes action and actionListener. They don't work and other switchable panels (accordion, toggle panel) don't have these attributes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
9
0 / 0

[JBoss JIRA] Created: (RF-10731) Validation: ajax requests not sent

by Pavol Pitonak (JIRA)

Validation: ajax requests not sent ---------------------------------- Key: RF-10731 URL: https://issues.jboss.org/browse/RF-10731 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.0.0.CR1 Environment: RichFaces 4.0.0-SNAPSHOT r.22114 Metamer 4.0.0-SNAPSHOT r.22123 Mojarra 2.1.0-FCS GlassFish Server Open Source Edition 3.1-SNAPSHOT OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux Chrome 10.0.648.127 @ Linux x86_64 Reporter: Pavol Pitonak 1. deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/csv.xhtml 2. type "aaa" to the first input result: validation is performed correctly but no ajax request is sent -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
4
0 / 0

[JBoss JIRA] Created: (RF-11100) Fix up the showcase starting page to contain more project information

by Jay Balunas (JIRA)

Fix up the showcase starting page to contain more project information --------------------------------------------------------------------- Key: RF-11100 URL: https://issues.jboss.org/browse/RF-11100 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: examples, showcase Reporter: Jay Balunas Fix For: 4.1.0.Final The opening page of the showcase demo is boring. We need to get it updated with information like what is on the project site. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (RF-10882) Upgrade jQuery to 1.5.2 version

by George Gastaldi (JIRA)

Upgrade jQuery to 1.5.2 version ------------------------------- Key: RF-10882 URL: https://issues.jboss.org/browse/RF-10882 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: client-lib Affects Versions: 4.0.0.Final Reporter: George Gastaldi Priority: Trivial As for http://jquery.com/, the latest version available is 1.5.2. Consider upgrading jQuery to that version. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

5
13
0 / 0

[JBoss JIRA] Created: (RF-10940) Client side validation refers to non existing javascript function

by Niels Soeffers (JIRA)

Client side validation refers to non existing javascript function ----------------------------------------------------------------- Key: RF-10940 URL: https://issues.jboss.org/browse/RF-10940 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.0.0.Final Reporter: Niels Soeffers Client Side Javascript functions are called on the component tags (for example onChange attribute) and defined at the bottom of the rendered page. We encountered a case where the function called in the onchange attribute is not defined at the bottom of the page. Our domain layer contains two different classes RG and SRG (they do not inherit from each other). However they both embed an embeddable class E with a field "name" In the GUI we have a page with a single form and two regions. One for adding a RG object and one for adding a SRG object. Both regions contain a h:inputText for the "name" field. So the first inputText is bound to {{RG.embedded.name}} and the second on {{SRG.embedded.name}}. Both inputTexts have a rich:validator tag as a child component. When the page is initially rendered both h:inputText have the same javascript function referred to in their onchange attribute (RGName_3Av). Which is not wrong because the validation (@NotNull on the "name" field in the Embedded class) is the same for both value bindings. It is a little bit confusing to see a method with a name of RGName_3Av on a component that is actually bound to SRG and so we would expect the method to call SRGName_3Av, but it's certainly not wrong and I even find it a very nice optimization. However when we click on an a:commandButton in the second region and rerender this second region, then suddenly the javascript function in the onchange attribute of the second inputText is changed and the name refers to the SRG component (SRGName_3Av), but this javascript method is never defined, because it was optimized when we initially rendered the complete page. Hope you can reproduce the problem with the above description and fix the problem or provide a workaround? Kind Regards, Niels -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

7
22
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues July 2011