January 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactor (blocked my Mojarra issue)

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13505?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13505: ------------------------------------ We should proceed with a PoC to determine if there are any other as-yet unforseen blockers. We could proceed with the workaround you suggested, or with a patched fork of Mojarra. > Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactor (blocked my Mojarra issue) > ---------------------------------------------------------------------------------------------------------------- > > Key: RF-13505 > URL: https://issues.jboss.org/browse/RF-13505 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lukáš Fryč > > Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 > We will still need to use some: > * resolve values in runtime > * add IDs for execution of AjaxOutput's > * collect list of meta-components to render > * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactor (blocked my Mojarra issue)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13505?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13505 at 1/21/14 12:31 PM: ----------------------------------------------------------- One of the workarounds when Mojarra gets not fixed on timely manner: We are still able to wrap {{VisitContext}} by considering these facts: * {{PartialViewContext}} must call {{UIViewRoot#visitTree(...)}} with parameters {{PartialVisitContext}} and {{PhaseAwareVisitCallback}} * we can wrap {{FacesContext#getViewRoot()}} (we have control over {{FacesContextFactory}} * wrapped {{UIViewRoot}} will have rewritten {{#visitTree}} ** we will use there {{VisitContextWrapper}} to make sure {{PartialViewContext}} is extended by RichFaces ** our wrapper will wrap methods like {{#invokeVisitCallback(...)}}/{{#getHints()}}/{{#getIdsToVisit()}} to do the meta-component rendering was (Author: lfryc): One of the workarounds when Mojarra gets not fixed on timely manner: We are still able to wrap {{VisitContext}} by considering these facts: * {{PartialViewContext}} must call {{UIViewRoot#visitTree(...)}} with parameters {{PartialVisitContext}} and {{PhaseAwareVisitCallback}} * we can wrap {{FacesContext#getViewRoot()}} (we have control over {{FacesContextFactory}} * wrapped {{UIViewRoot}} will have rewritten {{#visitTree}} ** we will use there {{VisitContextWrapper}} to make sure {{PartialViewContext}} is extended by RichFaces ** our wrapper will rewrite methods like {{#invokeVisitCallback}} to do the meta-component rendering > Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactor (blocked my Mojarra issue) > ---------------------------------------------------------------------------------------------------------------- > > Key: RF-13505 > URL: https://issues.jboss.org/browse/RF-13505 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lukáš Fryč > > Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 > We will still need to use some: > * resolve values in runtime > * add IDs for execution of AjaxOutput's > * collect list of meta-components to render > * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactor (blocked my Mojarra issue)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13505?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13505: --------------------------------- One of the workarounds when Mojarra gets not fixed on timely manner: We are still able to wrap {{VisitContext}} by considering these facts: * {{PartialViewContext}} must call {{UIViewRoot#visitTree(...)}} with parameters {{PartialVisitContext}} and {{PhaseAwareVisitCallback}} * we can wrap {{FacesContext#getViewRoot()}} (we have control over {{FacesContextFactory}} * wrapped {{UIViewRoot}} will have rewritten {{#visitTree}} ** we will use there {{VisitContextWrapper}} to make sure {{PartialViewContext}} is extended by RichFaces ** our wrapper will rewrite methods like {{#invokeVisitCallback}} to do the meta-component rendering > Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactor (blocked my Mojarra issue) > ---------------------------------------------------------------------------------------------------------------- > > Key: RF-13505 > URL: https://issues.jboss.org/browse/RF-13505 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Lukáš Fryč > > Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 > We will still need to use some: > * resolve values in runtime > * add IDs for execution of AjaxOutput's > * collect list of meta-components to render > * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13505) Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactor (blocked my Mojarra issue)

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13505: ------------------------------- Summary: Refactor custom tree traversal logic in EPVCI in order to leverage VisitContextFactor (blocked my Mojarra issue) Key: RF-13505 URL: https://issues.jboss.org/browse/RF-13505 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Lukáš Fryč Mojarra issue: https://java.net/jira/browse/JAVASERVERFACES-3151 We will still need to use some: * resolve values in runtime * add IDs for execution of AjaxOutput's * collect list of meta-components to render * wrap PartialResponseWriter#endDocument() for RichFaces extensions and JavascriptService -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13390) Regions don't have any visual representation so they can't be used as a @render target

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13390: --------------------------------- That's right, but I will investigate a little bit more, few things to consider: 1) how RichFaces 3.x uses regions 2) are there any other requests or misunderstandings in forums/stackoverflow/etc.? 3) what docs say about region > Regions don't have any visual representation so they can't be used as a @render target > -------------------------------------------------------------------------------------- > > Key: RF-13390 > URL: https://issues.jboss.org/browse/RF-13390 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-a4j-core > Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 > Wildfly 8.0.0.Beta2-SNAPSHOT > Mojarra 2.2.4-jbossorg-1 20131017-1524 > Reporter: Cody Lerum > Assignee: Lukáš Fryč > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When > {code} > <r:region> > <h:inputText> > <r:ajax execute="@this" render="@region" /> > </h:inputText> > </r:region> > {code} > A partial response seems to be generated with the correct content but the dom is not updated -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13493) Drop down menu rendered on wrong place when page is scrolled

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13493?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-13493: ------------------------------------ Works fine in IE7/8/9 and Firefox 26. Doesn't work in Chrome 32.0.1700.77 > Drop down menu rendered on wrong place when page is scrolled > ------------------------------------------------------------ > > Key: RF-13493 > URL: https://issues.jboss.org/browse/RF-13493 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 3.3.1.SP4 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 3.3.1.SP4 > > Attachments: dropdownmenu.png > > > # build RichFaces demo from branch https://svn.jboss.org/repos/richfaces/branches/enterprise/3.3.1.SP4/sampl... > # deploy to EAP 5.2 > # open page http://localhost:8080/richfaces-demo/richfaces/dropDownMenu.jsf?c=dropDow... > # open drop down menu (correct) > # scroll down the page and open drop down menu again > result: > * menu is rendered on wrong place (higher than expected) > * the more you scroll the page, the further it appears > * see attached screenshot > * reproducible in IE7, IE8 and Chrome 32 -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13504) ExtendedPartialViewContext should write ClientWindow ID updates to a partial response

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13504?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13504: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > ExtendedPartialViewContext should write ClientWindow ID updates to a partial response > ------------------------------------------------------------------------------------- > > Key: RF-13504 > URL: https://issues.jboss.org/browse/RF-13504 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > During code inspection for RF-13317 I have noticed [we are not writing client-window ID|https://github.com/richfaces/richfaces/blob/2d6e657136e409f67d837a7a30...] into the response as [Mojarra does|https://github.com/jboss/mojarra/blob/2.2.4-jbossorg-1/jsf-ri/src/ma...]. > Framework tests are needed to cover this issue. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13390) Regions don't have any visual representation so they can't be used as a @render target

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13390: ---------------------------- Summary: Regions don't have any visual representation so they can't be used as a @render target (was: Region fails to render after ajax request) > Regions don't have any visual representation so they can't be used as a @render target > -------------------------------------------------------------------------------------- > > Key: RF-13390 > URL: https://issues.jboss.org/browse/RF-13390 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 > Wildfly 8.0.0.Beta2-SNAPSHOT > Mojarra 2.2.4-jbossorg-1 20131017-1524 > Reporter: Cody Lerum > Assignee: Lukáš Fryč > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When > {code} > <r:region> > <h:inputText> > <r:ajax execute="@this" render="@region" /> > </h:inputText> > </r:region> > {code} > A partial response seems to be generated with the correct content but the dom is not updated -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13390) Regions don't have any visual representation so they can't be used as a @render target

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13390: ---------------------------- Issue Type: Enhancement (was: Bug) > Regions don't have any visual representation so they can't be used as a @render target > -------------------------------------------------------------------------------------- > > Key: RF-13390 > URL: https://issues.jboss.org/browse/RF-13390 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-a4j-core > Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0 > Wildfly 8.0.0.Beta2-SNAPSHOT > Mojarra 2.2.4-jbossorg-1 20131017-1524 > Reporter: Cody Lerum > Assignee: Lukáš Fryč > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > When > {code} > <r:region> > <h:inputText> > <r:ajax execute="@this" render="@region" /> > </h:inputText> > </r:region> > {code} > A partial response seems to be generated with the correct content but the dom is not updated -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13504) ExtendedPartialViewContext should write ClientWindow ID updates to a partial response

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13504?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13504: ------------------------------- Description: During code inspection for RF-13317 I have noticed [we are not writing client-window ID|https://github.com/richfaces/richfaces/blob/2d6e657136e409f67d837a7a30...] into the response as [Mojarra does|https://github.com/jboss/mojarra/blob/2.2.4-jbossorg-1/jsf-ri/src/ma...]. Framework tests are needed to cover this issue. was: During code inspection for RF-13317 I have noticed [we are not writing client-window ID|https://github.com/richfaces/richfaces/blob/2d6e657136e409f67d837a7a30... into response as [Mojarra does|https://github.com/jboss/mojarra/blob/2.2.4-jbossorg-1/jsf-ri/src/ma...]. Framework tests are needed to cover this issue. > ExtendedPartialViewContext should write ClientWindow ID updates to a partial response > ------------------------------------------------------------------------------------- > > Key: RF-13504 > URL: https://issues.jboss.org/browse/RF-13504 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Labels: jsf22 > > During code inspection for RF-13317 I have noticed [we are not writing client-window ID|https://github.com/richfaces/richfaces/blob/2d6e657136e409f67d837a7a30...] into the response as [Mojarra does|https://github.com/jboss/mojarra/blob/2.2.4-jbossorg-1/jsf-ri/src/ma...]. > Framework tests are needed to cover this issue. -- 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

10 years, 5 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 January 2014