July 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13716) Charts 4.5 Showcase/Metamer a4j:ajax re-render

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13716?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13716: ---------------------------------- Assignee: Brian Leathem > Charts 4.5 Showcase/Metamer a4j:ajax re-render > ---------------------------------------------- > > Key: RF-13716 > URL: https://issues.jboss.org/browse/RF-13716 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, showcase > Affects Versions: 4.5.0.Alpha3 > Environment: Latest FF/Chrome > Wildfly 8.1 > Reporter: Matej Novotny > Assignee: Brian Leathem > Priority: Blocker > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The chart component in [Showcase|https://github.com/richfaces/richfaces/blob/4.5.x/examples/showc...] (and in [Metamer|https://github.com/richfaces/richfaces-qa/blob/4.5.x/metamer/appl...] as well) uses a4j:ajax to rerender output with server-side message. It always looks something like this: > {code} > <h:form id='frm'> > <rich:chart id="chart" > //some attribute settings > <a4j:ajax event="plotclick" render="msg" execute="msg" /> > // axis settings... > </rich:chart> > <h:outputText id="msg" value="#{chartBean.msg}" /> > </h:form> > {code} > With [this|https://github.com/richfaces/richfaces/commit/ba9dcfacd8aa67348924d8...] commit, ajax re-rendering stopped working (in both, Metamer and Showcase) so it might be connected to fixes in RF-13706 in general. > Although I tried Metamer tests for a4j:ajax and they all pass successfully I do not think this issue is related to charts. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13716) Charts 4.5 Showcase/Metamer a4j:ajax re-render

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13716?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13716: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours Sprint: 4.5.0.Alpha3 - Sprint 5 > Charts 4.5 Showcase/Metamer a4j:ajax re-render > ---------------------------------------------- > > Key: RF-13716 > URL: https://issues.jboss.org/browse/RF-13716 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, showcase > Affects Versions: 4.5.0.Alpha3 > Environment: Latest FF/Chrome > Wildfly 8.1 > Reporter: Matej Novotny > Priority: Blocker > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The chart component in [Showcase|https://github.com/richfaces/richfaces/blob/4.5.x/examples/showc...] (and in [Metamer|https://github.com/richfaces/richfaces-qa/blob/4.5.x/metamer/appl...] as well) uses a4j:ajax to rerender output with server-side message. It always looks something like this: > {code} > <h:form id='frm'> > <rich:chart id="chart" > //some attribute settings > <a4j:ajax event="plotclick" render="msg" execute="msg" /> > // axis settings... > </rich:chart> > <h:outputText id="msg" value="#{chartBean.msg}" /> > </h:form> > {code} > With [this|https://github.com/richfaces/richfaces/commit/ba9dcfacd8aa67348924d8...] commit, ajax re-rendering stopped working (in both, Metamer and Showcase) so it might be connected to fixes in RF-13706 in general. > Although I tried Metamer tests for a4j:ajax and they all pass successfully I do not think this issue is related to charts. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13711) a4j:ajax status does not work as expected

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13711?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13711: ------------------------------- Fix Version/s: 4.5-Tracking > a4j:ajax status does not work as expected > ----------------------------------------- > > Key: RF-13711 > URL: https://issues.jboss.org/browse/RF-13711 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.7, 4.3.8 > Environment: IE8, Mozilla Firefox 30 > Reporter: Evgeny Mironenko > Assignee: Matej Novotny > Fix For: 4.5-Tracking > > > Status attribute for {{a4j:ajax}} does not work as expected. > I tried to create simple project with content: > {code:title=index.xhtml} > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > <h:head> > </h:head> > <h:body> > <a4j:status id="progress" onstart="console.log('start')" > onstop="console.log('stop')"/> > <div id="content"> > <h:form> > <h:commandButton value="Click"> > <a4j:ajax event="click" status="progress" listener="#{testBean.invoke}"/> > </h:commandButton> > </h:form> > </div> > </h:body> > </html> > {code} > It did not work for me. I do not see any log messages in the console. > As workaround I can use the {{render}} attribute instead of {{status}}, but we use it for another goals, am I right? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13706) dequeued Ajax request not processed correctly if its source element has been updated

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13706?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13706: ------------------------------------ Great, thanks [~ppitonak]. That makes sense and explains the current situation. > dequeued Ajax request not processed correctly if its source element has been updated > ------------------------------------------------------------------------------------ > > Key: RF-13706 > URL: https://issues.jboss.org/browse/RF-13706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.7 > Reporter: Marcel Kolsteren > Assignee: Marcel Kolsteren > Fix For: 4.3.8, 4.5.0.Alpha3 > > Attachments: queuetest-javaee6.zip, queuetest.zip, richfaces-core-4.3.8-SNAPSHOT.patch.zip > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I found a problem in the RichFaces Ajax queuing mechanism, which can cause all JavaScript execution to stop, leaving the end user with an unresponsive page. > The problem occurs when a request in the queue rerenders an area that includes the source element of the next request in the queue, but does not include the form of that source element. When the next request is fetched from the queue, JSF tries to find the correct form by climbing the DOM tree, starting at the source element of the event. However, because the source element has been rerendered, the path to its form is broken, and in that case JSF falls back to the first form of the page (see JavaScript function getForm that is called by jsf.ajax.request in jsf.js). If that form is not the form belonging to the rerendered version of the element, nasty things will happen. > To illustrate this, I created a very simple Java EE 7 web application (see attached Maven project) and deployed it in WildFly 8.1.0.Final. It contains a page with one clickable link that rerenders itself when clicked: > {noformat} > <!DOCTYPE html> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="http://richfaces.org/a4j"> > <h:head/> > <h:body> > <form action="http://www.meandi.nl"/> > <h:form> > <a4j:commandLink action="#{richBean.waitThreeSeconds}" value="Click Me" render="@this"/> > </h:form> > </h:body> > </html> > {noformat} > The method "waitThreeSeconds" does nothing but waiting for three seconds. When the link is double clicked, you'll observe that the first click is handled correctly, but that the second click results in an Ajax request posted to the URL of the first form, leading to access denied errors (because of cross domain scripting). The used RichFaces version is 4.3.7. > The problem can be fixed by changing the RichFaces JavaScript code, so that after completion of an Ajax request, stale elements are removed from the queue. I created a patch for RichFaces 4.3.7, and verified that it works (see attachment). Another solution strategy would be to try to find the new DOM element that corresponds to the stale source of the event, and fetch the form from that element. My thought was that removing the stale request would be better, because (1) it is kind of dangerous to process a user action on an element that has already been replaced and (2) the element might have been removed from the DOM tree by the previous rerender. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13687?page=com.atlassian.jira.plugin.s... ] Brian Leathem reopened RF-13687: -------------------------------- Assignee: Brian Leathem (was: Juraj Húska) > TabPanel header is not updated after switching of tabs > ------------------------------------------------------ > > Key: RF-13687 > URL: https://issues.jboss.org/browse/RF-13687 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3, 5.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13687?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-13687: ---------------------------------- Former test visible in [this|https://github.com/richfaces/richfaces/commit/0c3e9ff2fc3ceaa6087b4c...] comment is reproducing the issue I am talking about above. > TabPanel header is not updated after switching of tabs > ------------------------------------------------------ > > Key: RF-13687 > URL: https://issues.jboss.org/browse/RF-13687 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3, 5.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Juraj Húska > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13687?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-13687: ---------------------------------- I have tried to test new implementation of {{tabPanel}}. I have found one difference between new and old implementation: * action method bound to {{rich:tab}} via its {{action}} attribute is executed only when was previously inactive, and is activated. In previous implementation one can click on the active header many times, and the action method was invoked nevertheless. Is this a bug ? It is at least change of behavior which can affect some users. Reopening. > TabPanel header is not updated after switching of tabs > ------------------------------------------------------ > > Key: RF-13687 > URL: https://issues.jboss.org/browse/RF-13687 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3, 5.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Juraj Húska > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13707) Photoalbum: incorrect account details shown after creating a new one

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13707?page=com.atlassian.jira.plugin.s... ] Michal Petrov reassigned RF-13707: ---------------------------------- Assignee: Michal Petrov > Photoalbum: incorrect account details shown after creating a new one > -------------------------------------------------------------------- > > Key: RF-13707 > URL: https://issues.jboss.org/browse/RF-13707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.8 > Reporter: Juraj Húska > Assignee: Michal Petrov > Labels: photoalbum > Fix For: 4.3.8, 4.5-Tracking > > > When user create a new account in Photoalbum application there are shown account details, which are incorrect: > * missing login, first name, surname > * wrong sex value (there is always female - I tried other than my photos as avatars, so the problem will be somewhere else :) ) > * missing Birthday and email -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13707) Photoalbum: incorrect account details shown after creating a new one

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13707?page=com.atlassian.jira.plugin.s... ] Michal Petrov resolved RF-13707. -------------------------------- Fix Version/s: 4.3.8 Resolution: Done > Photoalbum: incorrect account details shown after creating a new one > -------------------------------------------------------------------- > > Key: RF-13707 > URL: https://issues.jboss.org/browse/RF-13707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.8 > Reporter: Juraj Húska > Labels: photoalbum > Fix For: 4.3.8, 4.5-Tracking > > > When user create a new account in Photoalbum application there are shown account details, which are incorrect: > * missing login, first name, surname > * wrong sex value (there is always female - I tried other than my photos as avatars, so the problem will be somewhere else :) ) > * missing Birthday and email -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13716) Charts 4.5 Showcase/Metamer a4j:ajax re-render

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13716?page=com.atlassian.jira.plugin.s... ] Matej Novotny updated RF-13716: ------------------------------- Priority: Blocker (was: Major) > Charts 4.5 Showcase/Metamer a4j:ajax re-render > ---------------------------------------------- > > Key: RF-13716 > URL: https://issues.jboss.org/browse/RF-13716 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, showcase > Affects Versions: 4.5.0.Alpha3 > Environment: Latest FF/Chrome > Wildfly 8.1 > Reporter: Matej Novotny > Priority: Blocker > Fix For: 4.5.0.Alpha3 > > > The chart component in [Showcase|https://github.com/richfaces/richfaces/blob/4.5.x/examples/showc...] (and in [Metamer|https://github.com/richfaces/richfaces-qa/blob/4.5.x/metamer/appl...] as well) uses a4j:ajax to rerender output with server-side message. It always looks something like this: > {code} > <h:form id='frm'> > <rich:chart id="chart" > //some attribute settings > <a4j:ajax event="plotclick" render="msg" execute="msg" /> > // axis settings... > </rich:chart> > <h:outputText id="msg" value="#{chartBean.msg}" /> > </h:form> > {code} > With [this|https://github.com/richfaces/richfaces/commit/ba9dcfacd8aa67348924d8...] commit, ajax re-rendering stopped working (in both, Metamer and Showcase) so it might be connected to fixes in RF-13706 in general. > Although I tried Metamer tests for a4j:ajax and they all pass successfully I do not think this issue is related to charts. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 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 July 2014