January 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12690) Upgrade jsf-impl from 2.1.13-jbossorg-1 to 2.1.16-jbossorg-1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12690?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12690: ------------------------------- Fix Version/s: 4.3.0.CR1 > Upgrade jsf-impl from 2.1.13-jbossorg-1 to 2.1.16-jbossorg-1 > ------------------------------------------------------------ > > Key: RF-12690 > URL: https://issues.jboss.org/browse/RF-12690 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Fix For: 4.3.0.CR1 > > > 4.3.0.M3 uses jsf-impl 2.1.13-jbossorg-1. However, there is 2.1.16-jbossorg-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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12690) Upgrade jsf-impl from 2.1.13-jbossorg-1 to 2.1.16-jbossorg-1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12690?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12690: ------------------------------------ This would being us in alignment with that jsf-impl version used by AS7/EAP 6: https://github.com/jbossas/jboss-as/blob/master/pom.xml#L88 > Upgrade jsf-impl from 2.1.13-jbossorg-1 to 2.1.16-jbossorg-1 > ------------------------------------------------------------ > > Key: RF-12690 > URL: https://issues.jboss.org/browse/RF-12690 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Fix For: 4.3.0.CR1 > > > 4.3.0.M3 uses jsf-impl 2.1.13-jbossorg-1. However, there is 2.1.16-jbossorg-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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12688) Upgrade Guava from 11.02 to 13.0.1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12688?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12688. -------------------------------- Resolution: Won't Fix We track the guava version used by AS7/EAP 6 project. https://github.com/jbossas/jboss-as/blob/master/pom.xml#L85 > Upgrade Guava from 11.02 to 13.0.1 > ---------------------------------- > > Key: RF-12688 > URL: https://issues.jboss.org/browse/RF-12688 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > > The Guava version used by RF is 11.0.2. However, there is 13.0.1 (or even 14.0-rc1). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12688) Upgrade Guava from 11.02 to 13.0.1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12688?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12688: ------------------------------- Fix Version/s: (was: 4.3.0.CR1) > Upgrade Guava from 11.02 to 13.0.1 > ---------------------------------- > > Key: RF-12688 > URL: https://issues.jboss.org/browse/RF-12688 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > > The Guava version used by RF is 11.0.2. However, there is 13.0.1 (or even 14.0-rc1). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12688) Upgrade Guava from 11.02 to 13.0.1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12688?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12688: ------------------------------- Fix Version/s: 4.3.0.CR1 > Upgrade Guava from 11.02 to 13.0.1 > ---------------------------------- > > Key: RF-12688 > URL: https://issues.jboss.org/browse/RF-12688 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Fix For: 4.3.0.CR1 > > > The Guava version used by RF is 11.0.2. However, there is 13.0.1 (or even 14.0-rc1). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12647) rich:dataTable rowclick with nested f:param

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12647?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12647: ------------------------------- Labels: waiting_on_user (was: ) > rich:dataTable rowclick with nested f:param > ------------------------------------------- > > Key: RF-12647 > URL: https://issues.jboss.org/browse/RF-12647 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.0.M2 > Environment: Win7, JDK7, Glassfish3, Mojarra 2.1.14, SeamFaces, RF 4.x.x > Reporter: Fab Mars > Labels: waiting_on_user > > During my migration from RF 3.3 I found this: > Before (with RF 3.3.3): > {code:xml|title="RF 3 Sample"} > <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping"> > <a4j:support event="onRowClick" reRender="shippingEditForm"> > <a4j:actionparam name="shippingId" value="#{shipping.id}" assignTo="#{shippingEdit.id}"/> > </a4j:support> > <rich:column> > <f:facet name="header"> > <h:outputText value="Destination"/> > </f:facet> > <h:outputText value="#{shipping.destinationCountry.name}" /> > </rich:column> >  > </rich:dataTable> > {code} > There was nothing really impacting on the migration guide > https://community.jboss.org/wiki/RichFacesMigrationGuide33x-4xMigration-C... > So I logically did that with RF4.x.x: > {code:xml|title="RF 4 Sample 1"} > <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping"> > <a4j:ajax event="rowclick" render="shippingEditForm"> > <a4j:param name="shippingId" value="#{shipping.id}" assignTo="#{shippingEdit.id}"/> > </a4j:ajax> > <rich:column> > <f:facet name="header"> > <h:outputText value="Destination"/> > </f:facet> > <h:outputText value="#{shipping.destinationCountry.name}" /> > </rich:column> >  > </rich:dataTable> > {code} > But the a4j:ajax isn't triggered (not at all, it's NOT a param assignment issue). To start having something that responds, one needs to remove the a4j:param and do it EL-newlook style. > {code:xml|title="RF 4 Sample 2"} > <a4j:ajax event="rowclick" render="shippingEditForm" listener="#{shippingEdit.setId(shipping.id)}"/> > {code} > Anyhow we're close to RF-11446 and whenever that one gets fixed, one should check whether this case here is also solved. > But wait, even that doesn't work: when one clicks on a row with that code, the listener is called but an ArrayIndexOutOfBoundsException is thrown because the clientID that's actually passed into UIDataAdapter#invokeOnRow is the id of the dataTable itself, NOT this of the row/cell. Hence, String rowId = clientId.substring(baseId.length() + 1) ends up tragically. > So...to make it really work, you have to do what's described here: https://community.jboss.org/thread/174063 and not fall into the trap of RF-11446. > Working code (RF 4.2.3+) > {code:xml:xml|title="RF 4 Sample 3"} > <a4j:jsFunction name="shippingListRowClick" render="shippingEditForm"> > <a4j:param name="shippingId" assignTo="#{shippingEdit.id}"/> > </a4j:jsFunction> > <rich:dataTable id="shippingList" value="#{billingLister.allShippings}" var="shipping" onrowclick="shippingListRowClick(#{shipping.id});"> > <rich:column> > <f:facet name="header"> > <h:outputText value="Destination"/> > </f:facet> > <h:outputText value="#{shipping.destinationCountry.name}" /> > </rich:column> >  > </rich:dataTable> > {code} > All that...for that. > Overall that makes quite a difference between RF 3.3 and RF 4.x. I'd say we have a couple of regressions. Or at least that needs an extra clarification in the documentation and migration guide. Thank you. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12687) Cancel button should cancel immediately

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12687?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12687: ------------------------------- Fix Version/s: 5-Tracking > Cancel button should cancel immediately > --------------------------------------- > > Key: RF-12687 > URL: https://issues.jboss.org/browse/RF-12687 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Bindu Priya > Fix For: 5-Tracking > > > Hi, > i m using richface:fileupload control to upload a file > When we are importing a file and in progress stage click on cancel button it should cancel immediately i.e. if it is in 40% uploaded then after clicking on cancel button once again uploading status is starting from 0% to 100% .Is there any way to control upload progress after clicking on cancel button. It should immediately cancel the document uploading progress. It should not start once again uploading status from 0% to 100% after clicking on cancel button > please help how to proceed further. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12691) extendedDataTable: Header facet render problem in RichFaces 4

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12691?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12691: ------------------------------- Fix Version/s: 4.3.0.CR1 > extendedDataTable: Header facet render problem in RichFaces 4 > -------------------------------------------------------------- > > Key: RF-12691 > URL: https://issues.jboss.org/browse/RF-12691 > 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.CR1 > > Attachments: screenshots.zip, testapp.zip > > > extendedDataTable header renders OK if entire table or panel that contains it are rendered. if I render just the header row using render="table@header" format, the header row re-renders, but its format is lost (refer to the attached screenshots). Checkbox in column 1 is the trigger for this issue. > * Header contains 'select all' checkbox, each data row contains row-level checkbox. > * Click on data row will rerender the header row and this is event that causes alignment to go off. > * If I rerender the entire table and/or panel, this does not happen, but causes undesirable performance problems when clicking individual rows in succession due to delays from jsf 2 / richfaces 4 render cycles. > It looks like the header-only render is trying to do a vertical center of header cell contents while the panel/table render is not, causing the cell contents to slide down vertically in the header cell. > This problem occurs in every browser I tested: IE 9, Firefox 16, Firefox 17, and Chrome 23.0 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12691) extendedDataTable: Header facet render problem in RichFaces 4

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12691?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12691: ------------------------------- Description: extendedDataTable header renders OK if entire table or panel that contains it are rendered. if I render just the header row using render="table@header" format, the header row re-renders, but its format is lost (refer to the attached screenshots). Checkbox in column 1 is the trigger for this issue. * Header contains 'select all' checkbox, each data row contains row-level checkbox. * Click on data row will rerender the header row and this is event that causes alignment to go off. * If I rerender the entire table and/or panel, this does not happen, but causes undesirable performance problems when clicking individual rows in succession due to delays from jsf 2 / richfaces 4 render cycles. It looks like the header-only render is trying to do a vertical center of header cell contents while the panel/table render is not, causing the cell contents to slide down vertically in the header cell. This problem occurs in every browser I tested: IE 9, Firefox 16, Firefox 17, and Chrome 23.0 was: extendedDataTable header renders OK if entire table or panel that contains it are rendered. if I render just the header row using render="table@header" format, the header row re-renders, but its format is lost (refer to the attached screenshots). Checkbox in column 1 is the trigger for this issue. Header contains 'select all' checkbox, each data row contains row-level checkbox. Click on data row will rerender the header row and this is event that causes alignment to go off. If I rerender the entire table and/or panel, this does not happen, but causes undesirable performance problems when clicking individual rows in succession due to delays from jsf 2 / richfaces 4 render cycles. It looks like the header-only render is trying to do a vertical center of header cell contents while the panel/table render is not, causing the cell contents to slide down vertically in the header cell. This problem occurs in every browser I tested: IE 9, Firefox 16, Firefox 17, and Chrome 23.0 > extendedDataTable: Header facet render problem in RichFaces 4 > -------------------------------------------------------------- > > Key: RF-12691 > URL: https://issues.jboss.org/browse/RF-12691 > 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 > Attachments: screenshots.zip, testapp.zip > > > extendedDataTable header renders OK if entire table or panel that contains it are rendered. if I render just the header row using render="table@header" format, the header row re-renders, but its format is lost (refer to the attached screenshots). Checkbox in column 1 is the trigger for this issue. > * Header contains 'select all' checkbox, each data row contains row-level checkbox. > * Click on data row will rerender the header row and this is event that causes alignment to go off. > * If I rerender the entire table and/or panel, this does not happen, but causes undesirable performance problems when clicking individual rows in succession due to delays from jsf 2 / richfaces 4 render cycles. > It looks like the header-only render is trying to do a vertical center of header cell contents while the panel/table render is not, causing the cell contents to slide down vertically in the header cell. > This problem occurs in every browser I tested: IE 9, Firefox 16, Firefox 17, and Chrome 23.0 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-11565) Showcase: multiple selections in rich:autocomplete doesn't work when "clicking" is used

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-11565?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-11565: --------------------------------- Thanks for investigation Morten, it really helped to find cause! > Showcase: multiple selections in rich:autocomplete doesn't work when "clicking" is used > --------------------------------------------------------------------------------------- > > Key: RF-11565 > URL: https://issues.jboss.org/browse/RF-11565 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.1.0.Milestone3, 4.2.3.CR1, 4.3.0.M3 > Environment: iPhone 4 (Safari) > Nexus (Android 2.3.6) > Google Chrome 12.0.742.112 > Reporter: Jan Papousek > Assignee: Lukáš Fryč > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > The second a third autocomplete input in Showcase demo http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=autoco... [1] doesn't work properly on the mentioned browsers/devices: > # type "Al" > # select "Alabama" -> input field is containing "Alabama" > # type ", P" > # select "Pennsylvania" with mouse/finger -> input field is containing "Pennsylvania, P" (it should contain "Alabama, Pennsylvania") > The Safari developer's console on iPhone doesn't display any error. > It works properly on: > - Opera 11.50 > - Firefox 6.0 > [1] http://10.0.2.2:8080/showcase/#autocomplete:modes in movile showcase -- 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, 4 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