January 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12717) “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1.

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12717?page=com.atlassian.jira.plugin.s... ] Juraj Húska reassigned RF-12717: -------------------------------- Assignee: Brian Leathem (was: Juraj Húska) > “Component ID <componentId> has already been found in the view” exception when using rich:dataTable with JSF 2.1.13 on EAP 6.0.1. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12717 > URL: https://issues.jboss.org/browse/RF-12717 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Brian Leathem > Fix For: 4.3.0.Final > > Attachments: sample.rar > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > This is a problem with <richataTable>. The component id for each row is reused. If you change the markup to use an ordinary <h:dataTable> and <h:column> then it works correctly. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-12682: ------------------------------------ It affects all versions since 4.2.3.Final. I didn't try older versions of RichFaces. > extendedDataTable render issue with rich:tabPanel > ------------------------------------------------- > > Key: RF-12682 > URL: https://issues.jboss.org/browse/RF-12682 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1 > Reporter: Kaveh A. > Assignee: Pavol Pitonak > Labels: extendedDataTable, render, richfaces, tabpanel > Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip > > > This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time). > In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue. > https://community.jboss.org/message/783787 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12366) Uploading 2 files despite rich:fileUpload:maxFilesQuantity="1"

by Thomas Jodes (JIRA)

[ https://issues.jboss.org/browse/RF-12366?page=com.atlassian.jira.plugin.s... ] Thomas Jodes edited comment on RF-12366 at 1/28/13 6:06 AM: ------------------------------------------------------------ Having a look at the showcase demo (rf 4.2.3.FINAL), you can upload two or more file in the same case if you do the following: 1. Choose a file. 2. Press Upload. 3. Uploaded File resides in the server now. 4. Delete that file in the widget. 5. You can begin at step 1. uploaded an other file... and so on ... So for me, the documentation's quote: "maxFilesQuantity The maxFilesQuantity parameter defines maximum number of files allowed to be uploaded. After a number of files in the list equals to the value of this attribute, "Add" button disappears and nothing could be uploaded even if you clear the whole list. In order to upload files again you should rerender the component." is broken. was (Author: jenskreidler): Having a look at the showcase demo (rf 4.2.3.FINAL), you can upload two or more file in the same case if you do the following: 1. Choose a file. 2. Press Upload. 3. Uploaded File resides in the server now. 4. Delete that file in the widget. 5. You can begin at step 1. uploaded an other file... and so on ... My first thougts on that is that the upload component uses plain javascript - NOT evaluating any server-side relevant data. Thus setting the disabled-attribute in rich:fileUpload will not work to restrict the max. number of files. > Uploading 2 files despite rich:fileUpload:maxFilesQuantity="1" > --------------------------------------------------------------- > > Key: RF-12366 > URL: https://issues.jboss.org/browse/RF-12366 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.2.Final > Environment: JDK1.6, > JBoss 6.0.Final > richfaces 4.2.2.Final > seam 3.1 > Chrome > Reporter: Artur Mioduszewski > Fix For: 5-Tracking > > > Button 'Add' does not disable after starting file uploading. > In case: maxFilesQuantity="1" in rich:fileUpload I am able to upload more than 1 file using below scenario: > I start to upload large file lala.wmv. During uploading of lala.wmv file, button "Add" is not blocked, so I am able to select second file to upload. > Finally 2 files are uploaded despite maxFilesQuantity="1". -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12366) Uploading 2 files despite rich:fileUpload:maxFilesQuantity="1"

by Thomas Jodes (JIRA)

[ https://issues.jboss.org/browse/RF-12366?page=com.atlassian.jira.plugin.s... ] Thomas Jodes commented on RF-12366: ----------------------------------- Having a look at the showcase demo (rf 4.2.3.FINAL), you can upload two or more file in the same case if you do the following: 1. Choose a file. 2. Press Upload. 3. Uploaded File resides in the server now. 4. Delete that file in the widget. 5. You can begin at step 1. uploaded an other file... and so on ... My first thougts on that is that the upload component uses plain javascript - NOT evaluating any server-side relevant data. Thus setting the disabled-attribute in rich:fileUpload will not work to restrict the max. number of files. > Uploading 2 files despite rich:fileUpload:maxFilesQuantity="1" > --------------------------------------------------------------- > > Key: RF-12366 > URL: https://issues.jboss.org/browse/RF-12366 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.2.Final > Environment: JDK1.6, > JBoss 6.0.Final > richfaces 4.2.2.Final > seam 3.1 > Chrome > Reporter: Artur Mioduszewski > Fix For: 5-Tracking > > > Button 'Add' does not disable after starting file uploading. > In case: maxFilesQuantity="1" in rich:fileUpload I am able to upload more than 1 file using below scenario: > I start to upload large file lala.wmv. During uploading of lala.wmv file, button "Add" is not blocked, so I am able to select second file to upload. > Finally 2 files are uploaded despite maxFilesQuantity="1". -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12763) a4j:mediaOutput does not work in composite component : accessing cc evaluates to null

by Thomas Jodes (JIRA)

[ https://issues.jboss.org/browse/RF-12763?page=com.atlassian.jira.plugin.s... ] Thomas Jodes updated RF-12763: ------------------------------ Attachment: richfaces-mediaoutput.zip - Plain maven wtp project to see / test this issue > a4j:mediaOutput does not work in composite component : accessing cc evaluates to null > ------------------------------------------------------------------------------------- > > Key: RF-12763 > URL: https://issues.jboss.org/browse/RF-12763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.3.Final > Environment: JSF-RI 2.1.6 > RichFaces 4.2.3.FINAL > Reporter: Thomas Jodes > Attachments: richfaces-mediaoutput.zip > > > Using a4j:mediaOutput in any compsite component cannot evaluate cc (is null). > Thus, using mediaOutput's createContent-Attribute like "#{cc.attrs.handler.paintImage}" will not work. > --- > Relevant part of the exception: > javax.el.PropertyNotFoundException: /resources/components/media.xhtml @27,24 createContent="#{cc.attrs.handler.paintImage}": Target Unreachable, identifier 'cc' resolved to null -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12763) a4j:mediaOutput does not work in composite component : accessing cc evaluates to null

by Thomas Jodes (JIRA)

Thomas Jodes created RF-12763: --------------------------------- Summary: a4j:mediaOutput does not work in composite component : accessing cc evaluates to null Key: RF-12763 URL: https://issues.jboss.org/browse/RF-12763 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.2.3.Final Environment: JSF-RI 2.1.6 RichFaces 4.2.3.FINAL Reporter: Thomas Jodes Using a4j:mediaOutput in any compsite component cannot evaluate cc (is null). Thus, using mediaOutput's createContent-Attribute like "#{cc.attrs.handler.paintImage}" will not work. --- Relevant part of the exception: javax.el.PropertyNotFoundException: /resources/components/media.xhtml @27,24 createContent="#{cc.attrs.handler.paintImage}": Target Unreachable, identifier 'cc' resolved to null -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12763) a4j:mediaOutput does not work in composite component : accessing cc evaluates to null

by Thomas Jodes (JIRA)

[ https://issues.jboss.org/browse/RF-12763?page=com.atlassian.jira.plugin.s... ] Thomas Jodes updated RF-12763: ------------------------------ Issue Type: Bug (was: Feature Request) > a4j:mediaOutput does not work in composite component : accessing cc evaluates to null > ------------------------------------------------------------------------------------- > > Key: RF-12763 > URL: https://issues.jboss.org/browse/RF-12763 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.3.Final > Environment: JSF-RI 2.1.6 > RichFaces 4.2.3.FINAL > Reporter: Thomas Jodes > > Using a4j:mediaOutput in any compsite component cannot evaluate cc (is null). > Thus, using mediaOutput's createContent-Attribute like "#{cc.attrs.handler.paintImage}" will not work. > --- > Relevant part of the exception: > javax.el.PropertyNotFoundException: /resources/components/media.xhtml @27,24 createContent="#{cc.attrs.handler.paintImage}": Target Unreachable, identifier 'cc' resolved to null -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12728) rich:fileUpload doesn't accept valid file after its unsuccessful multiple upload

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12728?page=com.atlassian.jira.plugin.s... ] Jan Papousek reopened RF-12728: ------------------------------- Brian: I don't understand to your solution. Is here something I should change in Metamer to fix the sample? Metamer doesn't set @name attribute value. > rich:fileUpload doesn't accept valid file after its unsuccessful multiple upload > -------------------------------------------------------------------------------- > > Key: RF-12728 > URL: https://issues.jboss.org/browse/RF-12728 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.CR1 > Environment: RichFaces 4.3.0.CR1 > Metamer 4.3.0.20130114-CR1 > Weld Servlet (Uber Jar) 20120106-1159 > Apache Tomcat 7.0.34 > Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux > Firefox 16.0 @ Linux x86_64 > RichFaces 4.3.0.CR1 > Metamer 4.3.0.20130114-CR1 > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux > Firefox 16.0 @ Linux x86_64 > Reporter: Jan Papousek > Assignee: Brian Leathem > Labels: needs-qe, regression > Fix For: 4.3.0.Final > > Attachments: to_upload.png > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > Using 4.3.0.M3 I've successfuly uploaded 3 files from the attachment in one time. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12710) rich:calendar - currentDate attribute has confusing name and documentation

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12710?page=com.atlassian.jira.plugin.s... ] Jan Papousek reopened RF-12710: ------------------------------- I suppose it should be: {quote} Used to define -the define- the month and year which will be displayed {quote} > rich:calendar - currentDate attribute has confusing name and documentation > -------------------------------------------------------------------------- > > Key: RF-12710 > URL: https://issues.jboss.org/browse/RF-12710 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.CR1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.Final > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Rich:calendar@currentDate sets a default month which will be displayed in its popup. The VDL doc says {quote}Defines the current date{quote} > I think the attribute name should be more explanatory and its documentation should be updated. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12695) rich:select incorrect behavior on IE9 with many selectItems

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12695?page=com.atlassian.jira.plugin.s... ] Juraj Húska reassigned RF-12695: -------------------------------- Assignee: (was: Juraj Húska) > rich:select incorrect behavior on IE9 with many selectItems > ----------------------------------------------------------- > > Key: RF-12695 > URL: https://issues.jboss.org/browse/RF-12695 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.1.0.Final > Environment: Internet Explorer 9, Windows 7 > Reporter: kevin 2 > Fix For: 5-Tracking > > > rich:select component has incorrect behavior on IE9 when it contains many items. > {code:html} > <rich:select id="selectId"> > <f:selectItems value="#{select.hugeList}"/> > </rich:select> > {code} > When you scroll up and down few times, try to select a value in the bottom of the list, then the scrollbar moves down indefinitely so the hovered value cannot be selected. > The problem seems to appear with a list of 100 elements or more. -- 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, 11 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 January 2013