October 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13168: ------------------------------- Sprint: (was: 5.0.0.Alpha2 - Sprint 2) > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Brian Leathem > Labels: interop, jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13093) extendedDataTable column resizing and reordering not working on transient (stateless) views

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13093?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13093: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 3 > extendedDataTable column resizing and reordering not working on transient (stateless) views > ------------------------------------------------------------------------------------------- > > Key: RF-13093 > URL: https://issues.jboss.org/browse/RF-13093 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.2 > Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23 > Reporter: Salvo Isaja > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When turning on transient (stateless) views in recent Mojarra versions (as per JSF 2.2 specification, to my best understanding), using request scoped backing beans, javax.faces.ViewState becomes the constant "stateless". Column resizing and reordering in extendedDataTable causes an Ajax request to the server, but in this case an invalid response is sent, containing only: > {code:xml} > <?xml version='1.0' encoding='UTF-8'?> > <partial-response></partial-response> > {code} > This causes an exception in {{jsf.js}} because the partial-response element has no children and no further JavaScript processing happens in the view until the page is reloaded. In the non-transient view case, I see a {{change}} element updating only the ViewState is returned, instead. > Other features seem to work pretty well in stateless mode, by the way. > Thanks -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13093) extendedDataTable column resizing and reordering not working on transient (stateless) views

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13093?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13093: ------------------------------- Sprint: (was: 5.0.0.Alpha2 - Sprint 2) > extendedDataTable column resizing and reordering not working on transient (stateless) views > ------------------------------------------------------------------------------------------- > > Key: RF-13093 > URL: https://issues.jboss.org/browse/RF-13093 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.2 > Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23 > Reporter: Salvo Isaja > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When turning on transient (stateless) views in recent Mojarra versions (as per JSF 2.2 specification, to my best understanding), using request scoped backing beans, javax.faces.ViewState becomes the constant "stateless". Column resizing and reordering in extendedDataTable causes an Ajax request to the server, but in this case an invalid response is sent, containing only: > {code:xml} > <?xml version='1.0' encoding='UTF-8'?> > <partial-response></partial-response> > {code} > This causes an exception in {{jsf.js}} because the partial-response element has no children and no further JavaScript processing happens in the view until the page is reloaded. In the non-transient view case, I see a {{change}} element updating only the ViewState is returned, instead. > Other features seem to work pretty well in stateless mode, by the way. > Thanks -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12675: ------------------------------- Fix Version/s: (was: 5-Tracking) > Drag and drop doesn't work with MyFaces > --------------------------------------- > > Key: RF-12675 > URL: https://issues.jboss.org/browse/RF-12675 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop > Affects Versions: 4.2.3.Final > Environment: tomcat6 > Reporter: Anton Zukovskij > Assignee: Brian Leathem > Labels: Drag, drop, myfaces, waiting_on_user > Attachments: dragAndDrop.zip, dragdrop-test.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event: > Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)). > This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12675: ------------------------------- Sprint: RichFaces 4.3.4 Sprint 1, 5.0.0.Alpha2 - Sprint 3 (was: RichFaces 4.3.4 Sprint 1) > Drag and drop doesn't work with MyFaces > --------------------------------------- > > Key: RF-12675 > URL: https://issues.jboss.org/browse/RF-12675 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop > Affects Versions: 4.2.3.Final > Environment: tomcat6 > Reporter: Anton Zukovskij > Assignee: Brian Leathem > Labels: Drag, drop, myfaces, waiting_on_user > Fix For: 5-Tracking > > Attachments: dragAndDrop.zip, dragdrop-test.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event: > Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)). > This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12675: ------------------------------- Sprint: RichFaces 4.3.4 Sprint 1 (was: RichFaces 4.3.4 Sprint 1, 5.0.0.Alpha2 - Sprint 2) > Drag and drop doesn't work with MyFaces > --------------------------------------- > > Key: RF-12675 > URL: https://issues.jboss.org/browse/RF-12675 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop > Affects Versions: 4.2.3.Final > Environment: tomcat6 > Reporter: Anton Zukovskij > Assignee: Brian Leathem > Labels: Drag, drop, myfaces, waiting_on_user > Fix For: 5-Tracking > > Attachments: dragAndDrop.zip, dragdrop-test.zip > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event: > Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)). > This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12802: ------------------------------------ Looking at the first showcase class: https://github.com/richfaces/richfaces-qa/blob/master/page-fragments/src/... I can't find the _TheFirstAccordion_ class referenced (at least github can't find it for me). Where is it? > Move page fragments from repository qa to richfaces5 > ---------------------------------------------------- > > Key: RF-12802 > URL: https://issues.jboss.org/browse/RF-12802 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > > As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework. > We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ] Brian Leathem edited comment on RF-12802 at 10/3/13 4:59 PM: ------------------------------------------------------------- A link to the commit that introduces a "showcase" of how to use the Page Fragments: https://github.com/richfaces/richfaces-qa/commit/6e8f58cac501848c6143285d... ---- I see now that [~jhuska] linked to this in his comment calling for a review. I missed it. was (Author: bleathem): A link to the commit that introduces a "showcase" of how to use the Page Fragments: https://github.com/richfaces/richfaces-qa/commit/6e8f58cac501848c6143285d... > Move page fragments from repository qa to richfaces5 > ---------------------------------------------------- > > Key: RF-12802 > URL: https://issues.jboss.org/browse/RF-12802 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > > As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework. > We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12802: ------------------------------------ A link to the commit that introduces a "showcase" of how to use the Page Fragments: https://github.com/richfaces/richfaces-qa/commit/6e8f58cac501848c6143285d... > Move page fragments from repository qa to richfaces5 > ---------------------------------------------------- > > Key: RF-12802 > URL: https://issues.jboss.org/browse/RF-12802 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > > As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework. > We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13219) Document cloning of richfaces git repository together with its submodules

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13219?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13219: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 2 > Document cloning of richfaces git repository together with its submodules > ------------------------------------------------------------------------- > > Key: RF-13219 > URL: https://issues.jboss.org/browse/RF-13219 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Priority: Minor > Fix For: 5.0.0.Alpha2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > To successfully build a RichFaces repository, one needs to clone in with its submodules, issuing: > {{git clone --recursive https://github.com/richfaces/richfaces.git}} > Repository submodules are not cloned if that parameter is not passed. > Could we update the doc to contain this information ? E.g. the {{README.md}} of repository, and the Developer Guide ? -- 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

12 years, 3 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 October 2013