[JBoss JIRA] (RF-13732) RichList with scroll bar doesn't work correctly inside uiRepeat
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13732?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13732:
-------------------------------
Labels: uiRepeat#setIndex (was: )
> RichList with scroll bar doesn't work correctly inside uiRepeat
> ---------------------------------------------------------------
>
> Key: RF-13732
> URL: https://issues.jboss.org/browse/RF-13732
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-ScrollableDataTable
> Affects Versions: 4.5.0.Alpha3
> Environment: WildFly 8.1.
> Reporter: Martin Tomasek
> Labels: uiRepeat#setIndex
>
> RichList with scroller doesn't work correctly if component is inside uiRepeat component.
> Scroller is visible and display data correctly but if user navigate to second page and then to first page, scroller stuck on second page but displayed data are from first page.
> The next page icon ( >> ) doesn't work correctly inside ui:Repeat. It still stuck on second page.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13732) RichList with scroll bar doesn't work correctly inside uiRepeat
by Martin Tomasek (JIRA)
Martin Tomasek created RF-13732:
-----------------------------------
Summary: RichList with scroll bar doesn't work correctly inside uiRepeat
Key: RF-13732
URL: https://issues.jboss.org/browse/RF-13732
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-ScrollableDataTable
Affects Versions: 4.5.0.Alpha3
Environment: WildFly 8.1.
Reporter: Martin Tomasek
RichList with scroller doesn't work correctly if component is inside uiRepeat component.
Scroller is visible and display data correctly but if user navigate to second page and then to first page, scroller stuck on second page but displayed data are from first page.
The next page icon ( >> ) doesn't work correctly inside ui:Repeat. It still stuck on second page.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-11093) UIDataAdaptor context variable backup broken (reentrance problem)
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-11093?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-11093.
----------------------------
> UIDataAdaptor context variable backup broken (reentrance problem)
> -----------------------------------------------------------------
>
> Key: RF-11093
> URL: https://issues.jboss.org/browse/RF-11093
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final
> Environment: Windows XP, Java 6, Tomcat 6.0.24, Mojarra 2.0.2.
> Reporter: Yannick Valot
> Assignee: Yannick Valot
> Fix For: 4.5.0.Alpha3
>
> Attachments: UIDataAdaptor.java.patch
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I am encountering a reentrance problem with org.richfaces.component.UIDataAdaptor (using it as a dataTable).
> I need to perform a visit of the component tree while executing an action on a command link in one row of the same table.
> {code}
> <rich:dataTable value="#{listOfItems}" var="myItem" >
> ... some stuff here ...
> <commandLink here>
> ... some stuff here ...
> </rich:dataTable>
> {code}
> After the action on the command link has visited the component tree, myItem is no longer available in context.
> When the UIDataAdaptor sets or resets the "myItem" context variable, it backs up any previous value by calling captureOrigValue(FacesContext), and later restores it by calling restoreOrigValue(FacesContext), but it looks as if the visit backs the variable up twice (in a nested fashion), and it erases myItem between the two backups :
> - backup variable (old value is correctly backed up) (in visitTree(VisitContext visitContext, VisitCallback callback))
> - erase variable (setRowKey(facesContext, null) in same function)
> - erase variable (doVisitChildren(VisitContext context, boolean visitRows))
> - erase variable (visitTree(VisitContext visitContext, VisitCallback callback))
> - backup variable (erases backed up value) (walk(FacesContext faces, DataVisitor visitor, Object argument))
> - ...
> - restore value (restores null) (walk(FacesContext faces, DataVisitor visitor, Object argument))
> - restore value (restores null) (in visitTree(VisitContext visitContext, VisitCallback callback))
> etc.
> The problem can be solved by *stacking* backed up variables, instead of storing them in a simple attribute, to allow for any kind of reentrance.
> (I do not say that this is the best possible patch, but it has solved the problem for me).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-11093) UIDataAdaptor context variable backup broken (reentrance problem)
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-11093?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-11093:
----------------------------------
Verified on this branch:
https://github.com/richfaces/richfaces-qa/tree/RF-11093
* [facelet|https://github.com/richfaces/richfaces-qa/blob/RF-11093/metamer/a...]
* [bean|https://github.com/richfaces/richfaces-qa/blob/RF-11093/metamer/appl...]
With the older versions of RF the {{var}} value is {{null}}, with {{4.5.Alpha3}} correct value is logged.
Verified. Closing.
> UIDataAdaptor context variable backup broken (reentrance problem)
> -----------------------------------------------------------------
>
> Key: RF-11093
> URL: https://issues.jboss.org/browse/RF-11093
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final
> Environment: Windows XP, Java 6, Tomcat 6.0.24, Mojarra 2.0.2.
> Reporter: Yannick Valot
> Assignee: Juraj Húska
> Fix For: 4.5.0.Alpha3
>
> Attachments: UIDataAdaptor.java.patch
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I am encountering a reentrance problem with org.richfaces.component.UIDataAdaptor (using it as a dataTable).
> I need to perform a visit of the component tree while executing an action on a command link in one row of the same table.
> {code}
> <rich:dataTable value="#{listOfItems}" var="myItem" >
> ... some stuff here ...
> <commandLink here>
> ... some stuff here ...
> </rich:dataTable>
> {code}
> After the action on the command link has visited the component tree, myItem is no longer available in context.
> When the UIDataAdaptor sets or resets the "myItem" context variable, it backs up any previous value by calling captureOrigValue(FacesContext), and later restores it by calling restoreOrigValue(FacesContext), but it looks as if the visit backs the variable up twice (in a nested fashion), and it erases myItem between the two backups :
> - backup variable (old value is correctly backed up) (in visitTree(VisitContext visitContext, VisitCallback callback))
> - erase variable (setRowKey(facesContext, null) in same function)
> - erase variable (doVisitChildren(VisitContext context, boolean visitRows))
> - erase variable (visitTree(VisitContext visitContext, VisitCallback callback))
> - backup variable (erases backed up value) (walk(FacesContext faces, DataVisitor visitor, Object argument))
> - ...
> - restore value (restores null) (walk(FacesContext faces, DataVisitor visitor, Object argument))
> - restore value (restores null) (in visitTree(VisitContext visitContext, VisitCallback callback))
> etc.
> The problem can be solved by *stacking* backed up variables, instead of storing them in a simple attribute, to allow for any kind of reentrance.
> (I do not say that this is the best possible patch, but it has solved the problem for me).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-11093) UIDataAdaptor context variable backup broken (reentrance problem)
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-11093?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-11093:
-----------------------------
Assignee: Yannick Valot (was: Juraj Húska)
> UIDataAdaptor context variable backup broken (reentrance problem)
> -----------------------------------------------------------------
>
> Key: RF-11093
> URL: https://issues.jboss.org/browse/RF-11093
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final
> Environment: Windows XP, Java 6, Tomcat 6.0.24, Mojarra 2.0.2.
> Reporter: Yannick Valot
> Assignee: Yannick Valot
> Fix For: 4.5.0.Alpha3
>
> Attachments: UIDataAdaptor.java.patch
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I am encountering a reentrance problem with org.richfaces.component.UIDataAdaptor (using it as a dataTable).
> I need to perform a visit of the component tree while executing an action on a command link in one row of the same table.
> {code}
> <rich:dataTable value="#{listOfItems}" var="myItem" >
> ... some stuff here ...
> <commandLink here>
> ... some stuff here ...
> </rich:dataTable>
> {code}
> After the action on the command link has visited the component tree, myItem is no longer available in context.
> When the UIDataAdaptor sets or resets the "myItem" context variable, it backs up any previous value by calling captureOrigValue(FacesContext), and later restores it by calling restoreOrigValue(FacesContext), but it looks as if the visit backs the variable up twice (in a nested fashion), and it erases myItem between the two backups :
> - backup variable (old value is correctly backed up) (in visitTree(VisitContext visitContext, VisitCallback callback))
> - erase variable (setRowKey(facesContext, null) in same function)
> - erase variable (doVisitChildren(VisitContext context, boolean visitRows))
> - erase variable (visitTree(VisitContext visitContext, VisitCallback callback))
> - backup variable (erases backed up value) (walk(FacesContext faces, DataVisitor visitor, Object argument))
> - ...
> - restore value (restores null) (walk(FacesContext faces, DataVisitor visitor, Object argument))
> - restore value (restores null) (in visitTree(VisitContext visitContext, VisitCallback callback))
> etc.
> The problem can be solved by *stacking* backed up variables, instead of storing them in a simple attribute, to allow for any kind of reentrance.
> (I do not say that this is the best possible patch, but it has solved the problem for me).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13711) a4j:ajax status does not work as expected
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13711?page=com.atlassian.jira.plugin.s... ]
Matej Novotny edited comment on RF-13711 at 7/17/14 8:19 AM:
-------------------------------------------------------------
I refactored and moved the reproducer to correct section in Metamer (in the a4jStatus instead of a4jAjax).
There is also and automated test I created. It is marked as Future and IssueTracking until we address this issue. Both changes should be in all necessary branches.
Steps to reproduce have been updated accordingly.
was (Author: manovotn):
I refactored and moved the reproducer to correct section in Metamer (in the a4jStatus instead of a4jAjax).
There is also and automated test I created. It is marked as Future and IssueTracking until we address this issue.
Both changes should be in all necessary branches.
> 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)
10 years, 4 months
[JBoss JIRA] (RF-13711) a4j:ajax status does not work as expected
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13711?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-13711:
------------------------------------
I refactored and moved the reproducer to correct section in Metamer (in the a4jStatus instead of a4jAjax).
There is also and automated test I created. It is marked as Future and IssueTracking until we address this issue.
Both changes should be in all necessary branches.
> 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)
10 years, 4 months
[JBoss JIRA] (RF-13711) a4j:ajax status does not work as expected
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13711?page=com.atlassian.jira.plugin.s... ]
Matej Novotny updated RF-13711:
-------------------------------
Steps to Reproduce:
For verification with automated test:
* Start Wildfly
* Run [Metamer test|https://github.com/richfaces/richfaces-qa/blob/4.5.x/metamer/ftest/s...]
** {{mvn clean verify -Pwildfly-remote-8-1 -Dtest=TestRF13711}}
* See the results
Alternatively you can reproduce it manually:
* Start Wildfly
* Deploy Metamer
* Go to [this page|http://localhost:8080/metamer/faces/components/a4jStatus/rf-13711.xhtml]
* Follow the instructions on that page to reproduce this
was:
* Start Wildfly
* Deploy Metamer
* Go to [this page|http://localhost:8080/metamer/faces/components/a4jAjax/rf-13711.xhtml]
* Open browser console
* Click the button
** Expected: Three lines appear in the console:
*** {{start}} //triggered by a4j:status
*** {{POST...}} //request itself
*** {{stop}} //triggered by a4j:status
** Actual: Only request itself is displayed in console
> 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)
10 years, 4 months
[JBoss JIRA] (RF-13719) rich.fileUpload breaks form action in portal
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/RF-13719?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration updated RF-13719:
-----------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1120627
> rich.fileUpload breaks form action in portal
> --------------------------------------------
>
> Key: RF-13719
> URL: https://issues.jboss.org/browse/RF-13719
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.5
> Environment: JBoss Portal 6.1.1
> Reporter: Jonáš Trantina
> Labels: gss
> Attachments: reproducer.zip, reproducer2.zip
>
>
> When a rich:fileUpload si submitted (i.e. files are uploaded) action of the form is not preserved well.
> In fileupload.js __submit method there is the following code:
> {code:JavaScript}
> var encodedURLInputs = this.form.children("input[name='javax.faces.encodedURL']");
> var originalAction = encodedURLInputs.length > 0 ? encodedURLInputs.val() : this.form.attr("action");
> {code}
> the var "originalAction" is then used to revert to the original action url of the form. However, encodedURLInputs and form action prop does not contain the same url. Because encodedURLInputs has bigger priority URL from that input is restored into the form and not the original form action. This breaks the form as the next submission fails.
> In portal the solution is
> {code:JavaScript}
> var originalFormAction =this.form.attr("action");
> {code}
> and then restore "originalFormAction" instead of "originalAction", but I am not sure if this doesn't break anything in other environments.
> Is this a bug in richfaces or is the content of input[name='javax.faces.encodedURL'] set badly?
> To reproduce you can use the reproducer attached.
> Example URLs:
> form action
> {code}
> /portal/classic/home/uploadform?portal:componentId=834fa198-ff3d-4a5c-a1c7-33c85e8a410d&interactionstate=JBPNS_rO0ABXcsABBfanNmQnJpZGdlVmlld0lkAAAAAQALL2hvbWUueGh0bWwAB19fRU9GX18*&portal:type=action
> {code}
> input[name='javax.faces.encodedURL']
> {code}
> /portal/classic/home/uploadform?portal:windowState=normal&portal:componentId=834fa198-ff3d-4a5c-a1c7-33c85e8a410d&portal:cacheLevel=PAGE&resourcestate=JBPNS_rO0ABXdAABBfanNmQnJpZGdlVmlld0lkAAAAAQALL2hvbWUueGh0bWwACF9wYnJBamF4AAAAAQAEdHJ1ZQAHX19FT0ZfXw**&portal:type=resource&portal:portletMode=view
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13712) FileUpload does not work on Wildfly 8.0 and Wildfly 8.1
by Byambaa MD (JIRA)
[ https://issues.jboss.org/browse/RF-13712?page=com.atlassian.jira.plugin.s... ]
Byambaa MD commented on RF-13712:
---------------------------------
Okey. i will test only richfaces environment.
> FileUpload does not work on Wildfly 8.0 and Wildfly 8.1
> -------------------------------------------------------
>
> Key: RF-13712
> URL: https://issues.jboss.org/browse/RF-13712
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.7
> Environment: 4.3.7 FileUpload does not work on wildfly
> Reporter: Byambaa MD
> Labels: waiting_on_user
> Attachments: AS error log.png, can't Render.png, chrome js error log.png, file upload done !.png, fileupload error on wildfly.png, Render code.png, Web application libraries and main page structure.png
>
>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months