January 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12707) rich:calendar - setValue(...) method from javascript API doesn't work correctly

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12707?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12707. -------------------------------- Resolution: Done Added an overide applySelection parameter to the internal __selectDate method > rich:calendar - setValue(...) method from javascript API doesn't work correctly > ------------------------------------------------------------------------------- > > Key: RF-12707 > URL: https://issues.jboss.org/browse/RF-12707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.CR1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12707) rich:calendar - setValue(...) method from javascript API doesn't work correctly

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12707?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12707: ------------------------------------ The setValue method fails because the attribute _showApplyButton_ is set to true. The javascript does not apply the new value until the apply button is clicked. You can see this for yourself in the Metamer sample if you expand the calendar dropdown and click the apply button. This is not a regression, but a bug nevertheless. The fix is to ignore the _showApplyButton_ attribute when setting the value via the _setValue_ API method. > rich:calendar - setValue(...) method from javascript API doesn't work correctly > ------------------------------------------------------------------------------- > > Key: RF-12707 > URL: https://issues.jboss.org/browse/RF-12707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.CR1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12715) richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12715?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12715: ------------------------------------ I don't believe we will be able to do this check reliably on the client-side, as there is not portable marker that an HTML element belongs to a JSF component (perhaps we should file a spec issue asking for this). I removing the searchForComponentRoortOrReturn method, and instead do the event re-mapping server side, as described [in this forum post|https://community.jboss.org/message/628872#628872]. > richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components > -------------------------------------------------------------------------------------- > > Key: RF-12715 > URL: https://issues.jboss.org/browse/RF-12715 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.CR1 > Reporter: Brian Leathem > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The searchForComponentRootOrReturn function in richfaces.js was created to correct the source element of jsf events to jsf components. However the check of whether an element belongs to a component fails for non JSF components. > A concrete example of this failure can be seen when an event generates from a nested _f:ajax_ tag. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12715) richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12715?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12715: ------------------------------------ I created a javscript method (isParentDistinct) in [this jsfiddle|http://jsfiddle.net/LNjdp/] that looks for the ":" separator character to determine component boundaries. This could be used to only replace the source id when the new source id is not across a component boundary. To make this a viable solution however, we need to know the component separator _javax.faces.SEPARATOR_CHAR_ from javascript. > richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components > -------------------------------------------------------------------------------------- > > Key: RF-12715 > URL: https://issues.jboss.org/browse/RF-12715 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.CR1 > Reporter: Brian Leathem > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The searchForComponentRootOrReturn function in richfaces.js was created to correct the source element of jsf events to jsf components. However the check of whether an element belongs to a component fails for non JSF components. > A concrete example of this failure can be seen when an event generates from a nested _f:ajax_ tag. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12714) Showcase and rich:dataTable: sorting in Arrangable demo doesn't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12714?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12714: ------------------------------------ This is caused by RF-12715 > Showcase and rich:dataTable: sorting in Arrangable demo doesn't work > -------------------------------------------------------------------- > > Key: RF-12714 > URL: https://issues.jboss.org/browse/RF-12714 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: regression > Affects Versions: 4.3.0.CR1 > Environment: JBoss AS 7.1.1, Java 1.7.0_10, Firefox 16.0.2 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12715) richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12715?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12715: ------------------------------- Sprint: 4.3.0.CR1 - Sprint > richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components > -------------------------------------------------------------------------------------- > > Key: RF-12715 > URL: https://issues.jboss.org/browse/RF-12715 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.CR1 > Reporter: Brian Leathem > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The searchForComponentRootOrReturn function in richfaces.js was created to correct the source element of jsf events to jsf components. However the check of whether an element belongs to a component fails for non JSF components. > A concrete example of this failure can be seen when an event generates from a nested _f:ajax_ tag. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12715) richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components

by Brian Leathem (JIRA)

Brian Leathem created RF-12715: ---------------------------------- Summary: richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components Key: RF-12715 URL: https://issues.jboss.org/browse/RF-12715 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.3.0.CR1 Reporter: Brian Leathem Priority: Blocker Fix For: 4.3.0.CR1 The searchForComponentRootOrReturn function in richfaces.js was created to correct the source element of jsf events to jsf components. However the check of whether an element belongs to a component fails for non JSF components. A concrete example of this failure can be seen when an event generates from a nested _f:ajax_ tag. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12304) A javascript error is thrown when the number of frozen columns = total number of columns

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-12304?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-12304: ---------------------------------------------- ivassile(a)redhat.com made a comment on [bug 871933|https://bugzilla.redhat.com/show_bug.cgi?id=871933] The client did not respond to my request [2] and I closed the case [1]. [1] 00736257 (https://c.na7.visual.force.com/apex/Case_View?id=500A000000Bdb0gIAB&sfdc....) [2] Comment #17 on case [1]: >>> I'm reopening the case since the RichFaces developers have raised the following concerns: 1) You have an issue selecting rows in rich:extendedDataTable that is NOT caused by RF-12304 [1]. 2) Disabling PARTIAL_STATE_SAVING fixes your issue. 3) You are expecting that this will be fixed in the next release. Given that at this point we have no idea what is causing the problem, 3) seems unlikely. Without a reproduction of the error, we have no idea what to fix. [1] https://issues.jboss.org/browse/RF-12304 Regards, Ilia <<< > A javascript error is thrown when the number of frozen columns = total number of columns > ---------------------------------------------------------------------------------------- > > Key: RF-12304 > URL: https://issues.jboss.org/browse/RF-12304 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.2.Final > Environment: jetty + tomcat 6 on win 7 > tomcat + Chrome + Linux > Reporter: Britt Abel > Labels: richfaces > Fix For: 4.2.5 > > Attachments: error.png > > > If I place two or more extendedDataTables with selectionType="single" on one a page, it is only possible to make a selection on the first extendedDataTable. It is imposible to select a row on the second table. If I turn around the order of tables or delete the first one, it works fine for the other one. This means, the implementation itself shoul be correct, > Do you have any ideas? Thanks for your help!!! -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12304) A javascript error is thrown when the number of frozen columns = total number of columns

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-12304?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-12304: ---------------------------------------------- Brian Leathem <bleathem(a)redhat.com> made a comment on [bug 871933|https://bugzilla.redhat.com/show_bug.cgi?id=871933] The issue reported by the customer is not caused by the linked jira issue. GSS said they were going to work with the customer on reproducing the issue. I have not heard back from GSS. You can follow up with GSS as to the status of this issue. > A javascript error is thrown when the number of frozen columns = total number of columns > ---------------------------------------------------------------------------------------- > > Key: RF-12304 > URL: https://issues.jboss.org/browse/RF-12304 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.2.Final > Environment: jetty + tomcat 6 on win 7 > tomcat + Chrome + Linux > Reporter: Britt Abel > Labels: richfaces > Fix For: 4.2.5 > > Attachments: error.png > > > If I place two or more extendedDataTables with selectionType="single" on one a page, it is only possible to make a selection on the first extendedDataTable. It is imposible to select a row on the second table. If I turn around the order of tables or delete the first one, it works fine for the other one. This means, the implementation itself shoul be correct, > Do you have any ideas? Thanks for your help!!! -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12698) Rename CDK and Resources plugins to comply conventions: maven-cdk-plugin -> richfaces-cdk-maven-plugin

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12698?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12698: ------------------------------- Fix Version/s: 5.0.0.M1 > Rename CDK and Resources plugins to comply conventions: maven-cdk-plugin -> richfaces-cdk-maven-plugin > ------------------------------------------------------------------------------------------------------ > > Key: RF-12698 > URL: https://issues.jboss.org/browse/RF-12698 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.3.0.CR1 > Reporter: Lukáš Fryč > Fix For: 5.0.0.M1 > > > During CDK build, following warning appears: > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Building RichFaces CDK: Resources Maven Plugin 4.3.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ maven-richfaces-resources-plugin --- > [INFO] Deleting /mnt/workspace/workspaces/richfaces/cdk/maven-resources-plugin/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-java-version) @ maven-richfaces-resources-plugin --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-maven-version) @ maven-richfaces-resources-plugin --- > [INFO] > [INFO] --- maven-plugin-plugin:2.9:descriptor (default-descriptor) @ maven-richfaces-resources-plugin --- > [ERROR] > Artifact Ids of the format maven-___-plugin are reserved for > plugins in the Group Id org.apache.maven.plugins > Please change your artifactId to the format ___-maven-plugin > In the future this error will break the build. > .... > {code} -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2013