[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms
by Michael Abele (JIRA)
[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ]
Michael Abele commented on RF-13408:
------------------------------------
The non-configurable approach of simply reducing timeout value from 1000 to e.g. 1 in bodyScrollListener method of extendeddatatable.js looks like a very easy change. Is there any chance to get this into 4.5.x soon? Thanks for any feedback!
> ExtendedDataTable, ajax loading delay of 1000ms
> -----------------------------------------------
>
> Key: RF-13408
> URL: https://issues.jboss.org/browse/RF-13408
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Reporter: Holger Walter
> Fix For: 5-Tracking
>
>
> When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy.
> I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener)
> Is it possible to reduce this timeout, or make it configurable via properties
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13780) Random JavaScript error due to missing attribute 'richfaces.RICH_CONTAINER'
by Michael B (JIRA)
[ https://issues.jboss.org/browse/RF-13780?page=com.atlassian.jira.plugin.s... ]
Michael B edited comment on RF-13780 at 8/18/14 8:03 AM:
---------------------------------------------------------
[~michpetrov], thanks - but we are not using maven in our projects for good reasons! - Just replacing some jars is also fine and not the problem. However getting a complex application to work and re-testing dependencies is.
We will try to see if we get it running, but looking at all the problems we've encountered with JSF until now, I doubt it will be easy ...
was (Author: michaelb80):
[~michpetrov], thanks - but we are not using maven in our projects for good reasons! - Just replacing some jars is also fine and not the problem. However getting a complex application to work and re-testing dependencies is.
We will try to see if we get it running, but looking at all the problems we've encountered wit JSF until now, I doubt it will be easy ...
> Random JavaScript error due to missing attribute 'richfaces.RICH_CONTAINER'
> ---------------------------------------------------------------------------
>
> Key: RF-13780
> URL: https://issues.jboss.org/browse/RF-13780
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component, component-tree
> Affects Versions: 4.3.7
> Environment: RichFaces 4.3.7
> Mojarra 2.1.29
> Java 7 Update 67 (x64)
> Tomcat 7.0.52 (x64)
> Firefox 31
> Reporter: Michael B
>
> First of all: this is a bug report which may be related to RF-13776, since it also originates in the same spot of the JavaScript library of RichFaces.
> Preface:
> The problem is difficult to reproduce systematically, since it only seems to occur in one of n cases of loading one and the same complex xhtml (with exactly the same data from the backing bean).
> The problem is described based on the rich:tree component when clicking on the expand icon of a treeNode which fires a "ToggleEvent".
> Occasionally there is a JavaScript error in the last line of
> {code}
> richfaces.ui.TreeNode.emitToggleEvent = function(nodeId) {
> var node = document.getElementById(nodeId);
> if (!node) {
> return;
> }
> richfaces.$(node).__fireToggleEvent();
> };
> {code}
> When the problem occurs, the expression {code}richfaces.$(node){code} evaluates to 'undefined'.
> Debugging into the function when the problem occurs:
> {code:title=richfaces.$|borderStyle=solid}
> richfaces.$ = function(source) {
> var element = richfaces.getDomElement( source );
> if(element)
> {
> return( element[richfaces.RICH_CONTAINER] || {} )["component"]
> }
> };
> {code}
> While the element is correctly evaluated to the treeNode/treeNodeToggle-source, the expression {code}element[richfaces.RICH_CONTAINER]{code} evaluates to 'undefined'.
> Reloading the page one or more times produces correct results, where the attribute is set.
> To be able to provide a reproducable example of the problem, please provide some information under which circumstances the property may not be set correctly for some components. Please also give us a hint, where to debug into the RF JavaScript code to find the spot where this property is set.
> Although the problem doesn't occur all the time, it happens quite often with the effect of breaking the entire application. So for future versions I would suggest a check if {code}richfaces.$(xyz){code} evalutes to a valid result, before invoking any operations on the result and maybe write a message to the a4j:log in cases where a valid result is expected but not returned.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13780) Random JavaScript error due to missing attribute 'richfaces.RICH_CONTAINER'
by Michael B (JIRA)
[ https://issues.jboss.org/browse/RF-13780?page=com.atlassian.jira.plugin.s... ]
Michael B edited comment on RF-13780 at 8/18/14 7:58 AM:
---------------------------------------------------------
In a quick test we updated the RF version:
| RF | 4.3.7 + dependencies | 4.5.0 Alpha 3 + dependencies |
| Mojarra | 2.1.29 | 2.2.8 |
Less problems than expected, but still there a some (mainly with some CSS being screwed, workarounds to other bugs etc. - didn't re-test the entire application of course...), but at least we can navigate to the page with the problem. Reproducing the steps which lead to the problem in RF 4.3.7 also produce the problem in RF 4.5.0 Alpha 3 ( - although maybe not as frequently.)
was (Author: michaelb80):
In a quick test we updated the RF version:
| RF | 4.3.7 + dependencies | 4.5.0 Alpha 3 + dependencies |
| Mojarra | 2.1.29 | 2.2.8 |
Less problems than expected, but still there a some (mainly with some CSS being screwed, workarounds to other bugs etc. - didn't re-test the entire application of course...), but at least we can navigate to the page with the problem. Reproducing the steps which lead to the problem in RF 4.3.7 does not longer produce the problem in RF 4.5.0 Alpha 3.
So question is, what makes the difference?
On a side note: before someone says "just use 4.5.0 Alpha 3 then"... - that's no solution, because we can't fix the layout, check problems, verify and re-test the entire application in time for the project deadline - besides no customer would accept an Alpha of the key library (and the first productive project release is due long before RF 4.5 gets final and can be adopted).
> Random JavaScript error due to missing attribute 'richfaces.RICH_CONTAINER'
> ---------------------------------------------------------------------------
>
> Key: RF-13780
> URL: https://issues.jboss.org/browse/RF-13780
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component, component-tree
> Affects Versions: 4.3.7
> Environment: RichFaces 4.3.7
> Mojarra 2.1.29
> Java 7 Update 67 (x64)
> Tomcat 7.0.52 (x64)
> Firefox 31
> Reporter: Michael B
>
> First of all: this is a bug report which may be related to RF-13776, since it also originates in the same spot of the JavaScript library of RichFaces.
> Preface:
> The problem is difficult to reproduce systematically, since it only seems to occur in one of n cases of loading one and the same complex xhtml (with exactly the same data from the backing bean).
> The problem is described based on the rich:tree component when clicking on the expand icon of a treeNode which fires a "ToggleEvent".
> Occasionally there is a JavaScript error in the last line of
> {code}
> richfaces.ui.TreeNode.emitToggleEvent = function(nodeId) {
> var node = document.getElementById(nodeId);
> if (!node) {
> return;
> }
> richfaces.$(node).__fireToggleEvent();
> };
> {code}
> When the problem occurs, the expression {code}richfaces.$(node){code} evaluates to 'undefined'.
> Debugging into the function when the problem occurs:
> {code:title=richfaces.$|borderStyle=solid}
> richfaces.$ = function(source) {
> var element = richfaces.getDomElement( source );
> if(element)
> {
> return( element[richfaces.RICH_CONTAINER] || {} )["component"]
> }
> };
> {code}
> While the element is correctly evaluated to the treeNode/treeNodeToggle-source, the expression {code}element[richfaces.RICH_CONTAINER]{code} evaluates to 'undefined'.
> Reloading the page one or more times produces correct results, where the attribute is set.
> To be able to provide a reproducable example of the problem, please provide some information under which circumstances the property may not be set correctly for some components. Please also give us a hint, where to debug into the RF JavaScript code to find the spot where this property is set.
> Although the problem doesn't occur all the time, it happens quite often with the effect of breaking the entire application. So for future versions I would suggest a check if {code}richfaces.$(xyz){code} evalutes to a valid result, before invoking any operations on the result and maybe write a message to the a4j:log in cases where a valid result is expected but not returned.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13780) Random JavaScript error due to missing attribute 'richfaces.RICH_CONTAINER'
by Michael B (JIRA)
[ https://issues.jboss.org/browse/RF-13780?page=com.atlassian.jira.plugin.s... ]
Michael B edited comment on RF-13780 at 8/18/14 7:59 AM:
---------------------------------------------------------
In a quick test we updated the RF version:
| RF | 4.3.7 + dependencies | 4.5.0 Alpha 3 + dependencies |
| Mojarra | 2.1.29 | 2.2.8 |
Less problems than expected, but still there a some (mainly with some CSS being screwed, workarounds to other bugs etc. - didn't re-test the entire application of course...), but at least we can navigate to the page with the problem. Reproducing the steps which lead to the problem in RF 4.3.7 also produces the problem in RF 4.5.0 Alpha 3 ( - although maybe not as frequently.)
was (Author: michaelb80):
In a quick test we updated the RF version:
| RF | 4.3.7 + dependencies | 4.5.0 Alpha 3 + dependencies |
| Mojarra | 2.1.29 | 2.2.8 |
Less problems than expected, but still there a some (mainly with some CSS being screwed, workarounds to other bugs etc. - didn't re-test the entire application of course...), but at least we can navigate to the page with the problem. Reproducing the steps which lead to the problem in RF 4.3.7 also produce the problem in RF 4.5.0 Alpha 3 ( - although maybe not as frequently.)
> Random JavaScript error due to missing attribute 'richfaces.RICH_CONTAINER'
> ---------------------------------------------------------------------------
>
> Key: RF-13780
> URL: https://issues.jboss.org/browse/RF-13780
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component, component-tree
> Affects Versions: 4.3.7
> Environment: RichFaces 4.3.7
> Mojarra 2.1.29
> Java 7 Update 67 (x64)
> Tomcat 7.0.52 (x64)
> Firefox 31
> Reporter: Michael B
>
> First of all: this is a bug report which may be related to RF-13776, since it also originates in the same spot of the JavaScript library of RichFaces.
> Preface:
> The problem is difficult to reproduce systematically, since it only seems to occur in one of n cases of loading one and the same complex xhtml (with exactly the same data from the backing bean).
> The problem is described based on the rich:tree component when clicking on the expand icon of a treeNode which fires a "ToggleEvent".
> Occasionally there is a JavaScript error in the last line of
> {code}
> richfaces.ui.TreeNode.emitToggleEvent = function(nodeId) {
> var node = document.getElementById(nodeId);
> if (!node) {
> return;
> }
> richfaces.$(node).__fireToggleEvent();
> };
> {code}
> When the problem occurs, the expression {code}richfaces.$(node){code} evaluates to 'undefined'.
> Debugging into the function when the problem occurs:
> {code:title=richfaces.$|borderStyle=solid}
> richfaces.$ = function(source) {
> var element = richfaces.getDomElement( source );
> if(element)
> {
> return( element[richfaces.RICH_CONTAINER] || {} )["component"]
> }
> };
> {code}
> While the element is correctly evaluated to the treeNode/treeNodeToggle-source, the expression {code}element[richfaces.RICH_CONTAINER]{code} evaluates to 'undefined'.
> Reloading the page one or more times produces correct results, where the attribute is set.
> To be able to provide a reproducable example of the problem, please provide some information under which circumstances the property may not be set correctly for some components. Please also give us a hint, where to debug into the RF JavaScript code to find the spot where this property is set.
> Although the problem doesn't occur all the time, it happens quite often with the effect of breaking the entire application. So for future versions I would suggest a check if {code}richfaces.$(xyz){code} evalutes to a valid result, before invoking any operations on the result and maybe write a message to the a4j:log in cases where a valid result is expected but not returned.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13780) Random JavaScript error due to missing attribute 'richfaces.RICH_CONTAINER'
by Michael B (JIRA)
[ https://issues.jboss.org/browse/RF-13780?page=com.atlassian.jira.plugin.s... ]
Michael B commented on RF-13780:
--------------------------------
In a quick test we updated the RF version:
| RF | 4.3.7 + dependencies | 4.5.0 Alpha 3 + dependencies |
| Mojarra | 2.1.29 | 2.2.8 |
Less problems than expected, but still there a some (mainly with some CSS being screwed, workarounds to other bugs etc. - didn't re-test the entire application of course...), but at least we can navigate to the page with the problem. Reproducing the steps which lead to the problem in RF 4.3.7 does not longer produce the problem in RF 4.5.0 Alpha 3.
So question is, what makes the difference?
On a side note: before someone says "just use 4.5.0 Alpha 3 then"... - that's no solution, because we can't fix the layout, check problems, verify and re-test the entire application in time for the project deadline - besides no customer would accept an Alpha of the key library (and the first productive project release is due long before RF 4.5 gets final and can be adopted).
> Random JavaScript error due to missing attribute 'richfaces.RICH_CONTAINER'
> ---------------------------------------------------------------------------
>
> Key: RF-13780
> URL: https://issues.jboss.org/browse/RF-13780
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component, component-tree
> Affects Versions: 4.3.7
> Environment: RichFaces 4.3.7
> Mojarra 2.1.29
> Java 7 Update 67 (x64)
> Tomcat 7.0.52 (x64)
> Firefox 31
> Reporter: Michael B
>
> First of all: this is a bug report which may be related to RF-13776, since it also originates in the same spot of the JavaScript library of RichFaces.
> Preface:
> The problem is difficult to reproduce systematically, since it only seems to occur in one of n cases of loading one and the same complex xhtml (with exactly the same data from the backing bean).
> The problem is described based on the rich:tree component when clicking on the expand icon of a treeNode which fires a "ToggleEvent".
> Occasionally there is a JavaScript error in the last line of
> {code}
> richfaces.ui.TreeNode.emitToggleEvent = function(nodeId) {
> var node = document.getElementById(nodeId);
> if (!node) {
> return;
> }
> richfaces.$(node).__fireToggleEvent();
> };
> {code}
> When the problem occurs, the expression {code}richfaces.$(node){code} evaluates to 'undefined'.
> Debugging into the function when the problem occurs:
> {code:title=richfaces.$|borderStyle=solid}
> richfaces.$ = function(source) {
> var element = richfaces.getDomElement( source );
> if(element)
> {
> return( element[richfaces.RICH_CONTAINER] || {} )["component"]
> }
> };
> {code}
> While the element is correctly evaluated to the treeNode/treeNodeToggle-source, the expression {code}element[richfaces.RICH_CONTAINER]{code} evaluates to 'undefined'.
> Reloading the page one or more times produces correct results, where the attribute is set.
> To be able to provide a reproducable example of the problem, please provide some information under which circumstances the property may not be set correctly for some components. Please also give us a hint, where to debug into the RF JavaScript code to find the spot where this property is set.
> Although the problem doesn't occur all the time, it happens quite often with the effect of breaking the entire application. So for future versions I would suggest a check if {code}richfaces.$(xyz){code} evalutes to a valid result, before invoking any operations on the result and maybe write a message to the a4j:log in cases where a valid result is expected but not returned.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13750) Upgrade testing dependencies
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13750?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak resolved RF-13750.
--------------------------------
Resolution: Done
All components except of Arq Tomcat container were upgraded. Created new issue RF-13784 for Tomcat container.
> Upgrade testing dependencies
> ----------------------------
>
> Key: RF-13750
> URL: https://issues.jboss.org/browse/RF-13750
> Project: RichFaces
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Components: tests - functional
> Affects Versions: 4.5.0.Alpha3
> Reporter: Pavol Pitonak
> Assignee: Pavol Pitonak
> Fix For: 4.5.0.Beta1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Upgrade following dependencies in build/pom.xml:
> * Arquillian Core 1.1.4.Final -> 1.1.5.Final
> * Arquillian Drone 1.3.0.Final -> 1.3.1.Final
> * Arquillian Tomcat container 1.0.0.CR6 -> 1.0.0.CR7
> * Selenium 2.41.0 -> 2.42.0
> * Arquillian Graphene 2.0.3.Final -> 2.1.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (RF-13780) Random JavaScript error due to missing attribute 'richfaces.RICH_CONTAINER'
by Michael B (JIRA)
[ https://issues.jboss.org/browse/RF-13780?page=com.atlassian.jira.plugin.s... ]
Michael B commented on RF-13780:
--------------------------------
[~michpetrov], thanks - but we are not using maven in our projects for good reasons! - Just replacing some jars is also fine and not the problem. However getting a complex application to work and re-testing dependencies is.
We will try to see if we get it running, but looking at all the problems we've encountered wit JSF until now, I doubt it will be easy ...
> Random JavaScript error due to missing attribute 'richfaces.RICH_CONTAINER'
> ---------------------------------------------------------------------------
>
> Key: RF-13780
> URL: https://issues.jboss.org/browse/RF-13780
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component, component-tree
> Affects Versions: 4.3.7
> Environment: RichFaces 4.3.7
> Mojarra 2.1.29
> Java 7 Update 67 (x64)
> Tomcat 7.0.52 (x64)
> Firefox 31
> Reporter: Michael B
>
> First of all: this is a bug report which may be related to RF-13776, since it also originates in the same spot of the JavaScript library of RichFaces.
> Preface:
> The problem is difficult to reproduce systematically, since it only seems to occur in one of n cases of loading one and the same complex xhtml (with exactly the same data from the backing bean).
> The problem is described based on the rich:tree component when clicking on the expand icon of a treeNode which fires a "ToggleEvent".
> Occasionally there is a JavaScript error in the last line of
> {code}
> richfaces.ui.TreeNode.emitToggleEvent = function(nodeId) {
> var node = document.getElementById(nodeId);
> if (!node) {
> return;
> }
> richfaces.$(node).__fireToggleEvent();
> };
> {code}
> When the problem occurs, the expression {code}richfaces.$(node){code} evaluates to 'undefined'.
> Debugging into the function when the problem occurs:
> {code:title=richfaces.$|borderStyle=solid}
> richfaces.$ = function(source) {
> var element = richfaces.getDomElement( source );
> if(element)
> {
> return( element[richfaces.RICH_CONTAINER] || {} )["component"]
> }
> };
> {code}
> While the element is correctly evaluated to the treeNode/treeNodeToggle-source, the expression {code}element[richfaces.RICH_CONTAINER]{code} evaluates to 'undefined'.
> Reloading the page one or more times produces correct results, where the attribute is set.
> To be able to provide a reproducable example of the problem, please provide some information under which circumstances the property may not be set correctly for some components. Please also give us a hint, where to debug into the RF JavaScript code to find the spot where this property is set.
> Although the problem doesn't occur all the time, it happens quite often with the effect of breaking the entire application. So for future versions I would suggest a check if {code}richfaces.$(xyz){code} evalutes to a valid result, before invoking any operations on the result and maybe write a message to the a4j:log in cases where a valid result is expected but not returned.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months