February 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-8440) problems with fileUpload controls labels

by Ilya Shaikovsky (JIRA)

problems with fileUpload controls labels ---------------------------------------- Key: RF-8440 URL: https://jira.jboss.org/jira/browse/RF-8440 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 3.3.3.CR1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Priority: Critical 1) as you could see in renderer we using tags instead of CSS for some labels. /** Default labels values */ private static final String[] defaultLables = { "Add...", "Upload", "Stop", "Clear All", "Cancel", "Clear", "Stop", "Done", "File size restricted", "Transfer error occurred","uploading"}; 2) MAIN PROBLEM. redefined labels do not escape text properly(writeText seems not used) so I could add tags around custom label using the code: uploadControlLabel="Upload1" -- 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, 6 months

5
6
0 / 0

[JBoss JIRA] Created: (RF-8368) dropDownMenu: inputs still not fully accessible inside

by Ilya Shaikovsky (JIRA)

dropDownMenu: inputs still not fully accessible inside ------------------------------------------------------ Key: RF-8368 URL: https://jira.jboss.org/jira/browse/RF-8368 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 3.3.3.BETA1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Fix For: 3.3.3.CR1 right click blocked. so can't paste for example via mouse. -- 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, 6 months

5
8
0 / 0

[JBoss JIRA] Created: (RF-8269) problems with sorting API (i.e. ExtendedDataModel + Modifiable) that goes with the rich:*dataTable components

by Ian Springer (JIRA)

problems with sorting API (i.e. ExtendedDataModel + Modifiable) that goes with the rich:*dataTable components ------------------------------------------------------------------------------------------------------------- Key: RF-8269 URL: https://jira.jboss.org/jira/browse/RF-8269 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 3.3.2.SR1 Reporter: Ian Springer I recently tried to implement server-side sorting by implementing ExtendedDataModel + Modifiable. I had several issues: 1) the name and usage of the Modifiable interface seem to assume that the sorting will be done on the items from the currently loaded page of data (i.e. "modifying" that in-memory list), but I think the more intuitive thing to do, particularly for large data sets, is to sort the entire data set (e.g. using ORDER BY if the data set is stored in a relational DB), and then return the appropriate page from the sorted data set. 2) when I click on a sortable column header, modify() is called several times. The first few times, the original/previous values of the SortField2s are passed in, which serves no purpose. modify() should be called exactly once per request, and the new sort fields and filter fields should be passed in. Ideally, the same method would also support passing new page range settings. 3) The order of the items in the List<SortField2> is not at all intuitive - it appears to be as follows: - The items in the list are ordered in reverse precedence (i.e. they are ordered from the lowest priority fields to the highest priority fields, with the following exception: If the last column clicked was already one of the sort fields (i.e. the user has requested flipping that field from ASC->DESC or DESC-<ASC), the corresponding SortField2 keeps its current position in the List, rather than being moved to the end of the List, to signify it is now has the highest precedence (as it should, for consistency sake) It would be much more intuitive if the List was ordered by precedence, with the highest priority fields first in the list, which is the same way sort fields are ordered in an ORDER BY clause. Also, as described above, when toggling a column between ASC and DESC, that column's should also be bumped up to the highest precedence. Filter fields should also be ordered with the higher precedence filters first in the list, rather than last. If I were to revamp the paging/sorting/filtering API, I'd make it look something like the following and stick it right in the ExtendedDataModel interface: void reloadData(List<FilterField> filterFields, List<SortField2> sortFields, Range range) This would allow the user of the API to load a new page of data with updated filtering, sorting, and/or range in one swoop. The RF component impl would only call this method if at least one of filterFields, sortFields, or range had been changed by the GUI user since the last time reloadData() was called. It would also call the method exactly once per request. This would save the implementer of the interface from having to cache the previous values to track if any of them had actually changed or if reloadData() had already been called for the current request. I'm attaching the implementation of ExtendedDataModel + Modifiable that I did to prototype using them for the Red Hat RHQ project. It shows the various ugly hacks I had to do to make the API work. Based on the prototype, we have decided to stick with custom components and facets we have been using, rather than using the sorting support currently provided by rich:dataTable and rich:extendedDataTable. I hope the issues I've described in this JIRA can be addressed, so we can switch over to using pure RichFaces. -- 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, 6 months

6
7
0 / 0

[JBoss JIRA] Created: (RF-7395) dataScroller: tableStyle doesn't work

by Vadim Mikovoz (JIRA)

dataScroller: tableStyle doesn't work ------------------------------------- Key: RF-7395 URL: https://jira.jboss.org/jira/browse/RF-7395 Project: RichFaces Issue Type: Bug Components: component-ScrollableDataTable Affects Versions: 3.3.2.CR1 Environment: all provided browsers rfVersion - v.3.3.2-SNAPSHOT Reporter: Vadim Mikovoz Assignee: Nick Belaevski Priority: Minor Define tableStyle attribute for dataScroller, e.g.: tableStyle="background-color: red; font-style: oblique;" 1. Open test page 2. Look at the dataScroller ------------------------------------ tableStyle didn't apply -- 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, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (RF-8123) Development: filtering control

by Anton Belevich (JIRA)

Development: filtering control ------------------------------ Key: RF-8123 URL: https://jira.jboss.org/jira/browse/RF-8123 Project: RichFaces Issue Type: Sub-task Reporter: Anton Belevich Assignee: Anton Belevich Fix For: 4.0.0.ALPHA2 -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-8122) Develpment: sorting control

by Anton Belevich (JIRA)

Develpment: sorting control --------------------------- Key: RF-8122 URL: https://jira.jboss.org/jira/browse/RF-8122 Project: RichFaces Issue Type: Sub-task Reporter: Anton Belevich Assignee: Anton Belevich Fix For: 4.0.0.ALPHA2 -- 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, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (RF-8389) Fix references to SNAPSHOT in docs

by Sean Rogers (JIRA)

Fix references to SNAPSHOT in docs ---------------------------------- Key: RF-8389 URL: https://jira.jboss.org/jira/browse/RF-8389 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: doc Affects Versions: 3.3.3.CR1 Reporter: Sean Rogers Assignee: Sean Rogers Fix For: 3.3.3.GA Fix references to SNAPSHOT in uploaded 3.3.3.CR1 docs -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (RF-8359) Fileupload component hanging during upload

by Charles Crouch (JIRA)

Fileupload component hanging during upload ------------------------------------------ Key: RF-8359 URL: https://jira.jboss.org/jira/browse/RF-8359 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.2.SR1, 3.3.2.GA Reporter: Charles Crouch Priority: Critical The file upload component is failing in RHQ, See https://bugzilla.redhat.com/show_bug.cgi?id=562751 for more details. Its definitely a problem in 3.3.2.GA and 3.3.2.SR1. This used to work so we're going to try dropping back versions until we find one that works. -- 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, 6 months

8
24
0 / 0

[JBoss JIRA] Created: (RF-8366) FileUpload: throw javascript error in Firefox

by Patrick Dahms (JIRA)

FileUpload: throw javascript error in Firefox --------------------------------------------- Key: RF-8366 URL: https://jira.jboss.org/jira/browse/RF-8366 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 3.3.2.SR1 Reporter: Patrick Dahms I get an javascript error in firefox 3.6 if i want to upload an file (xml). No problem in IE (8). xhtml: ================== <a4j:form id="upload-form"> <a4j:keepAlive beanName="uploadBean"/> [...] <rich:fileUpload id="uploadControl" fileUploadListener="#{uploadBean.uploadListener}"></rich:fileUpload> [...] </a4j:form> Controller: (Request) ================== [...] public void uploadListener( UploadEvent event ) throws IOException { UploadItem uploadItem = event.getUploadItem(); File uploadedFile = uploadItem.getFile(); FileInputStream in = new FileInputStream( uploadedFile ); byte[] data = new byte[( int ) uploadedFile.length()]; in.read( data ); in.close(); LOGGER.info( "Write file to temp dir -> " + uploadItem.getFile().getCanonicalPath() ); catalogXml = data; } [...] JavaScript Error (Firebug): ==================== Nicht definierte Entität http://localhost:8080/a4j/g/3_3_2.SR1org.ajax4jsf.javascript.AjaxScript.x... Line 101 An invalid or illegal string was specified" code: "12 http://localhost:8080/a4j/g/3_3_2.SR1org.ajax4jsf.javascript.PrototypeScr... Line 154 -- 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, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (RF-7640) Demo: Wrong handling with page in session

by Lukas Fryc (JIRA)

Demo: Wrong handling with page in session ----------------------------------------- Key: RF-7640 URL: https://jira.jboss.org/jira/browse/RF-7640 Project: RichFaces Issue Type: Bug Components: examples Affects Versions: 3.3.1 Environment: RichFaces Live Demo, 3.3.1.GA, 3.3.2-SNAPSHOT Reporter: Lukas Fryc When some page is chosen and then we will return to initial state of richfaces-demo (go to context-path, e.g. /richfaces-demo), last page is remembered and page controls seems like to be on last page, but content pertains to "Welcome" page. Try this: 1. open RichFaces Live Demo ( http://livedemo.exadel.com/richfaces-demo/index.jsp ) 2. go to Ajax Support - Status page 3. open RichFaces Live Demo again ( http://livedemo.exadel.com/richfaces-demo/index.jsp ) 4. FAILURE: we are on the welcome screen, but header, menu controls are from Status -- 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, 6 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2010