June 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13670) Update the "new" labels in the showcase

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13670?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13670. -------------------------------- Resolution: Done > Update the "new" labels in the showcase > --------------------------------------- > > Key: RF-13670 > URL: https://issues.jboss.org/browse/RF-13670 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The only component that should be labelled as "new" in the 4.5.x showcase is the chart component. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13670) Update the "new" labels in the showcase

by Brian Leathem (JIRA)

Brian Leathem created RF-13670: ---------------------------------- Summary: Update the "new" labels in the showcase Key: RF-13670 URL: https://issues.jboss.org/browse/RF-13670 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.5.0.Alpha3 The only component that should be labelled as "new" in the 4.5.x showcase is the chart component. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13636) Add List Impls to the resource serialization whitelist

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13636?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13636: ------------------------------- Fix Version/s: 4.5.0.Alpha3 > Add List Impls to the resource serialization whitelist > ------------------------------------------------------ > > Key: RF-13636 > URL: https://issues.jboss.org/browse/RF-13636 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.6 > Reporter: Cody Lerum > Assignee: Cody Lerum > Fix For: 4.3.8, 4.5.0.Alpha3 > > > Not having these prevents passing data list data to charting components via the mediaoutput component -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13647) File Download throws exception when used with a commandButton of type="button"

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13647?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13647: ------------------------------------ If still relevant despite the fileUpload changes in 4.5, then this fix should be ported to the 4.5 branch. If the port has already been done, please update the _fixVersion_. > File Download throws exception when used with a commandButton of type="button" > ------------------------------------------------------------------------------ > > Key: RF-13647 > URL: https://issues.jboss.org/browse/RF-13647 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.6 > Environment: Richfaces 4.3.6 Final. > Mojarra - 2.1.28 > Weblogic 12.1.2 > Windows 7 > Reporter: santhosh siravuri > Assignee: Michal Petrov > Priority: Critical > Labels: regression > Fix For: 4.3.8 > > Attachments: RF-13647.zip > > > File download action throws below exception. > {code} > ]] Root cause of ServletException. > java.lang.NullPointerException > at org.richfaces.renderkit.AjaxCommandRendererBase.isSubmitted(AjaxCommandRendererBase.java:83) > at org.richfaces.renderkit.AjaxCommandRendererBase.doDecode(AjaxCommandRendererBase.java:59) > at org.richfaces.renderkit.RendererBase.decode(RendererBase.java:80) > at javax.faces.component.UIComponentBase.decode(UIComponentBase.java:789) > at javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:1183) > Truncated. see log file for complete stacktrace > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13615: ------------------------------------ This fix needs to be ported to the 4.5 branch. If the port has already been done, please update the _fixVersion_. > ExtendedDataTable: double ajax request on scrolling > --------------------------------------------------- > > Key: RF-13615 > URL: https://issues.jboss.org/browse/RF-13615 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.6 > Environment: Problem can be tested in richfaces showcase. > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extende... > Reporter: Holger Walter > Assignee: Michal Petrov > Fix For: 4.3.8 > > Attachments: edt.png > > > After changing the width of a column, subsequent scrolling of the table triggers 2 ajax requests instead of the expected single request. > Due to this behavior I get some performance issues, as I have to execute some own javascript after each request. > Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered. > Best regards > wlh -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13615) ExtendedDataTable: double ajax request on scrolling

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13615?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13615: ------------------------------- Description: After changing the width of a column, subsequent scrolling of the table triggers 2 ajax requests instead of the expected single request. Due to this behavior I get some performance issues, as I have to execute some own javascript after each request. Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered. Best regards wlh was: 1. Go to the extendedDataTable showcase 2. Turn on ajax loading. 3. Open the debugger of your browser and watch the network communication 4. Scroll down in the table untli new data has to be fetched. => one POST request is sent. This is fine. 5. Change the width of a column in the table. => one POST request is sent. This is fine. 6. Scroll again in the table untli new data has to be fetched. -> 2 POST requests are sent. WHY? >From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table. Due to this behavior I get some perfromance issues, as I have to execute some own javascript after each request. Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered. Best regards wlh Steps to Reproduce: 1. Go to the extendedDataTable showcase 2. Turn on ajax loading. 3. Open the debugger of your browser and watch the network communication 4. Scroll down in the table untli new data has to be fetched. => one POST request is sent. This is fine. 5. Change the width of a column in the table. => one POST request is sent. This is fine. 6. Scroll again in the table untli new data has to be fetched. -> 2 POST requests are sent. WHY? >From now on, on each scroll, the table always sends 2 requests. This behavior stops only when your relaod the table. > ExtendedDataTable: double ajax request on scrolling > --------------------------------------------------- > > Key: RF-13615 > URL: https://issues.jboss.org/browse/RF-13615 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.6 > Environment: Problem can be tested in richfaces showcase. > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=extende... > Reporter: Holger Walter > Assignee: Michal Petrov > Fix For: 4.3.8 > > Attachments: edt.png > > > After changing the width of a column, subsequent scrolling of the table triggers 2 ajax requests instead of the expected single request. > Due to this behavior I get some performance issues, as I have to execute some own javascript after each request. > Is there a possibility to prevent the 2nd POST request. I would be happy even with a dirty hack, or just a hint showing me from where the 2nd request is triggered. > Best regards > wlh -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13669) Backport the CKEditor 4 upgrade to RichFaces 4.3

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13669?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13669: ------------------------------- Description: the reason for this backport is to address the reported IE 11 problems with the CKeditor in RichFaces <= 4.3.7 The only concern with this backport is the removal of the richfaces-skinning capability of the editor. Skinning the editor in RichFaces 4.5 requires using the CKEditor JS API. was:The only concern with this backport is the removal of the richfaces-skinning capability of the editor. Skinning the editor in RichFaces 4.5 requires using the CKEditor JS API. > Backport the CKEditor 4 upgrade to RichFaces 4.3 > ------------------------------------------------ > > Key: RF-13669 > URL: https://issues.jboss.org/browse/RF-13669 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Fix For: 4.3.8 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > the reason for this backport is to address the reported IE 11 problems with the CKeditor in RichFaces <= 4.3.7 > The only concern with this backport is the removal of the richfaces-skinning capability of the editor. Skinning the editor in RichFaces 4.5 requires using the CKEditor JS API. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13669) Backport the CKEditor 4 upgrade to RichFaces 4.3

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13669?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13669: ---------------------------------- Assignee: Pavol Pitonak QE verification of the IE 11 incompatibility of the 4.3.7 ckeditor would be appreciated to help prioritize this issue. > Backport the CKEditor 4 upgrade to RichFaces 4.3 > ------------------------------------------------ > > Key: RF-13669 > URL: https://issues.jboss.org/browse/RF-13669 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Pavol Pitonak > Fix For: 4.3.8 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > the reason for this backport is to address the reported IE 11 problems with the CKeditor in RichFaces <= 4.3.7 > The only concern with this backport is the removal of the richfaces-skinning capability of the editor. Skinning the editor in RichFaces 4.5 requires using the CKEditor JS API. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13669) Backport the CKEditor 4 upgrade to RichFaces 4.3

by Brian Leathem (JIRA)

Brian Leathem created RF-13669: ---------------------------------- Summary: Backport the CKEditor 4 upgrade to RichFaces 4.3 Key: RF-13669 URL: https://issues.jboss.org/browse/RF-13669 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-input Reporter: Brian Leathem Fix For: 4.3.8 The only concern with this backport is the removal of the richfaces-skinning capability of the editor. Skinning the editor in RichFaces 4.5 requires using the CKEditor JS API. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13665) RichFaces 4.5 should fail fast when used with un-pached Mojarra

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13665?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13665: ------------------------------------ QE I tested this in EAP 6.2.0 (where it correctly fails) and Wildfly 8.1.0.Final (where it correctly succeeds). Can you please test this in other containers with configurations that are expected to both pass and fail? > RichFaces 4.5 should fail fast when used with un-pached Mojarra > --------------------------------------------------------------- > > Key: RF-13665 > URL: https://issues.jboss.org/browse/RF-13665 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.5.0.Alpha3 > Reporter: Juraj Húska > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > > [~bleathem] wrote [in this comment|https://issues.jboss.org/browse/RF-13658?focusedCommentId=1297546...] for RF-13658: > ??There is a Mojarra bug that breaks the new EPVC ([JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]). This issue was patched in the mojarra impl that shipped with WildFly 8.0.0.Final, and in the Mojarra impl that shipped with EAP was also patched?? > ??We should have some code in place to fail fast if RichFaces 4.5 is used with an unpatched Mojarra. This can be achieved with reflection, looking for the method added in [JAVASERVERFACES-3151|https://java.net/jira/browse/JAVASERVERFACES-3151]?? > And we are not failing fast. I would say that when application is about to use unpached Mojarra, the fail fast would be a runtime exception during deployment ? > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 June 2014