August 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13139) popupPanel duplicated if double clicking links for opening popup

by Valiantsin Shukaila (JIRA)

[ https://issues.jboss.org/browse/RF-13139?page=com.atlassian.jira.plugin.s... ] Valiantsin Shukaila commented on RF-13139: ------------------------------------------ Attached example project with source code. Please check this out. > popupPanel duplicated if double clicking links for opening popup > ---------------------------------------------------------------- > > Key: RF-13139 > URL: https://issues.jboss.org/browse/RF-13139 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.1 > Environment: tomcat 7, Richfaces 4.3.1.Final, Spring, JSF Mojarra 2.2.0 > Reporter: Valiantsin Shukaila > Labels: popupPanel, richfaces, waiting_on_user > Attachments: RF-13139.zip > > > If you create a link/button/jsFunction that should render popup panel and open it after that and will try to double click this link the two instances of the same popup panel will appear. And you will be able to close only one of them. The other will remain on the page forever. > I've attached zip with maven and eclipse project that can be used for reproducing the issue. > I tested on Tomcat 7.0.41. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13139) popupPanel duplicated if double clicking links for opening popup

by Valiantsin Shukaila (JIRA)

[ https://issues.jboss.org/browse/RF-13139?page=com.atlassian.jira.plugin.s... ] Valiantsin Shukaila updated RF-13139: ------------------------------------- Description: If you create a link/button/jsFunction that should render popup panel and open it after that and will try to double click this link the two instances of the same popup panel will appear. And you will be able to close only one of them. The other will remain on the page forever. I've attached zip with maven and eclipse project that can be used for reproducing the issue. I tested on Tomcat 7.0.41. was:If you create a link/button/jsFunction that should render popup panel and open it after that and will try to double click this link the two instances of the same popup panel will appear. And you will be able to close only one of them. The other will remain on the page forever. > popupPanel duplicated if double clicking links for opening popup > ---------------------------------------------------------------- > > Key: RF-13139 > URL: https://issues.jboss.org/browse/RF-13139 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.1 > Environment: tomcat 7, Richfaces 4.3.1.Final, Spring, JSF Mojarra 2.2.0 > Reporter: Valiantsin Shukaila > Labels: popupPanel, richfaces, waiting_on_user > Attachments: RF-13139.zip > > > If you create a link/button/jsFunction that should render popup panel and open it after that and will try to double click this link the two instances of the same popup panel will appear. And you will be able to close only one of them. The other will remain on the page forever. > I've attached zip with maven and eclipse project that can be used for reproducing the issue. > I tested on Tomcat 7.0.41. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13139) popupPanel duplicated if double clicking links for opening popup

by Valiantsin Shukaila (JIRA)

[ https://issues.jboss.org/browse/RF-13139?page=com.atlassian.jira.plugin.s... ] Valiantsin Shukaila updated RF-13139: ------------------------------------- Attachment: RF-13139.zip Example maven and eclipse project for reproducing the issue > popupPanel duplicated if double clicking links for opening popup > ---------------------------------------------------------------- > > Key: RF-13139 > URL: https://issues.jboss.org/browse/RF-13139 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.1 > Environment: tomcat 7, Richfaces 4.3.1.Final, Spring, JSF Mojarra 2.2.0 > Reporter: Valiantsin Shukaila > Labels: popupPanel, richfaces, waiting_on_user > Attachments: RF-13139.zip > > > If you create a link/button/jsFunction that should render popup panel and open it after that and will try to double click this link the two instances of the same popup panel will appear. And you will be able to close only one of them. The other will remain on the page forever. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-11469) autocomplete method does not resolve bean if ui:included

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11469?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11469: ------------------------------- Fix Version/s: (was: 5-Tracking) > autocomplete method does not resolve bean if ui:included > -------------------------------------------------------- > > Key: RF-11469 > URL: https://issues.jboss.org/browse/RF-11469 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.0.0.Final > Reporter: u j > Assignee: Lukáš Fryč > Priority: Minor > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > A bean parameter in the autocomplete method is not resolved if the rich:autocomplete is part of a ui:include. > {code} > <ui:include src="/searchlocation.xhtml"> > <ui:param name="bean" value="#{searchBean}" /> > </ui:include> > {code} > searchlocation.xhtml contains: > {code} > <rich:autocomplete id="cityName" mode="ajax" value="#{bean.cityName}" autocompleteMethod="#{bean.suggestCities}" /> > {code} > The value binding works, but the binding in the autocompleteMethod gives: > {code} > 15:26:15,809 SEVERE [org.richfaces.log.Renderkit] (ajp-127.0.0.1-127.0.0.1-8009-1) Target Unreachable, identifier 'bean' resolved to null: javax.el.PropertyNotFoundException: Target Unreachable, identifier 'bean' resolved to null > at org.apache.el.parser.AstValue.getTarget(AstValue.java:75) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.el.parser.AstValue.invoke(AstValue.java:183) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [jbossweb-7.0.1.Final.jar:7.0.1.Final] > at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [weld-core-1.1.2.Final.jar:2011-07-26 15:02] > at org.richfaces.renderkit.AutocompleteRendererBase.getItems(AutocompleteRendererBase.java:105) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > at org.richfaces.renderkit.AutocompleteRendererBase.encodeItems(AutocompleteRendererBase.java:160) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > at org.richfaces.renderkit.AutocompleteRendererBase.encodeMetaComponent(AutocompleteRendererBase.java:271) [richfaces-components-ui-4.0.0-20110322.220419-243.jar:] > {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-10697) Popup Panel - @keepVisualState isn't fully implemented

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-10697?page=com.atlassian.jira.plugin.s... ] Brian Leathem edited comment on RF-10697 at 8/16/13 5:29 PM: ------------------------------------------------------------- Just to clarify - did you hide the attributes in the 4.3.x branch? -- Nevermind, I see you created/resolved RF-13140 in 4.3.4 was (Author: bleathem): Just to clarify - did you hide the attributes in the 4.3.x branch? > Popup Panel - @keepVisualState isn't fully implemented > ------------------------------------------------------ > > Key: RF-10697 > URL: https://issues.jboss.org/browse/RF-10697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.CR1 > Environment: RichFaces 4.0.0.20110227-CR1 r.21967 > Metamer 4.0.0.20110228-CR1 r.21993 > Apache MyFaces JSF-2.0 Core Impl 2.0.4 > JBoss AS 6.0.0.Final > OpenJDK Runtime Environment 1.6.0_20-b20 @Linux > Chrome 9.0.597.107 @ Linux x86_64 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Fix @keepVisualState attribute or remove it from taglib. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13107) ajaxRenderer component are renderer even though they are in non-active switchable panel, causing JSF to fail to update DOM

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13107: ------------------------------------ The generalized API introduced is: VisitChildrenRejectable#shouldVisitChildren() https://github.com/richfaces4/core/blob/master/api/src/main/java/org/rich... > ajaxRenderer component are renderer even though they are in non-active switchable panel, causing JSF to fail to update DOM > -------------------------------------------------------------------------------------------------------------------------- > > Key: RF-13107 > URL: https://issues.jboss.org/browse/RF-13107 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.2 > Reporter: Jonáš Trantina > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > Attachments: bug_reproducer.zip, reproducer_ajax.zip, rf13107ajax.png > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown. > Note that: > 1) switchType must be set to server to ensure the A's rich:message is really not on the page. > 2) button in B must re-render only content of B > This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered). > Please find the enclosed reproducer. > Snipper: > {code:xml} > <h:form> > <rich:tabPanel switchType="server"> > <rich:tab> > <h:inputText id="surname" value="#{richBean.surname}"> > <f:validateLength minimum="10"/> > </h:inputText> > <rich:message for="surname"/> > </rich:tab> > <rich:tab> > <h:panelGroup id="content"> > <h:inputText id="name" value="#{richBean.name}"> > <f:validateLength minimum="6"/> > </h:inputText> > <rich:message for="name"/> > </h:panelGroup> > <a4j:commandButton value="Submit" execute="content" render="content" /> > </rich:tab> > </rich:tabPanel> > </h:form> > {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-10697) Popup Panel - @keepVisualState isn't fully implemented

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-10697?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-10697: ------------------------------------ Just to clarify - did you hide the attributes in the 4.3.x branch? > Popup Panel - @keepVisualState isn't fully implemented > ------------------------------------------------------ > > Key: RF-10697 > URL: https://issues.jboss.org/browse/RF-10697 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.0.0.CR1 > Environment: RichFaces 4.0.0.20110227-CR1 r.21967 > Metamer 4.0.0.20110228-CR1 r.21993 > Apache MyFaces JSF-2.0 Core Impl 2.0.4 > JBoss AS 6.0.0.Final > OpenJDK Runtime Environment 1.6.0_20-b20 @Linux > Chrome 9.0.597.107 @ Linux x86_64 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5-Tracking > > > Fix @keepVisualState attribute or remove it from taglib. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-13081) Facets "disabled" not working for dataScroller

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13081?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13081: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours Fix Version/s: 5.0.0.Alpha3 (was: 5-Tracking) Priority: Major (was: Critical) Assignee: (was: Pavol Pitonak) > Facets "disabled" not working for dataScroller > ---------------------------------------------- > > Key: RF-13081 > URL: https://issues.jboss.org/browse/RF-13081 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Reporter: Laurent Grangier > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > All the facets which end with "disabled" (like "first_disabled", "previous_disabled", etc.) are not working for the component "rich:dataScroller". > According to the [documentation|http://docs.jboss.org/richfaces/latest_4_3_X/Component_Refe...], they should be available. > Example: > {code} > <f:facet name="first_disabled"> > <h:graphicImage value="my-image.png" /> > </f:facet> > {code} -- 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, 7 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 updated RF-12802: ------------------------------- Forum Reference: https://community.jboss.org/thread/230766 > 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 > 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, 7 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 8/16/13 4:39 PM: ------------------------------------------------------------- Is there any progress on this issue? It's blocking RF-12950. --- Nevermind, progress is clearly being demonstrated in the relevant forum thread: https://community.jboss.org/thread/230766 was (Author: bleathem): Is there any progress on this issue? It's blocking RF-12950. > 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 > 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, 7 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 August 2013