January 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12714) Showcase and rich:dataTable: sorting in Arrangable demo doesn't work

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12714?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-12714. ----------------------------- Resolution: Done > Showcase and rich:dataTable: sorting in Arrangable demo doesn't work > -------------------------------------------------------------------- > > Key: RF-12714 > URL: https://issues.jboss.org/browse/RF-12714 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: regression > Affects Versions: 4.3.0.CR1 > Environment: JBoss AS 7.1.1, Java 1.7.0_10, Firefox 16.0.2 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12713) Listeners don't work inside panels

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12713?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-12713. ----------------------------- Resolution: Duplicate Issue > Listeners don't work inside panels > ---------------------------------- > > Key: RF-12713 > URL: https://issues.jboss.org/browse/RF-12713 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core, regression > Affects Versions: 4.3.0.CR1 > Environment: RichFaces 4.3.0.CR1 > Metamer 4.3.0.20130109-CR1 > Mojarra 2.0.7 > JBoss AS 7.1.1 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 23.0.1271.97 @ Linux x86_64, Firefox 17 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jActionListener/all.xhtm... > # click "Invoke listener by binding" > result: > * message "Bound listener called" should be displayed but nothing happens > * it is reproducible inside these components: accordion, collapsible subtable, extended data table, collapsible panel, tab panel and popup panel -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12715) richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12715?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12715 at 1/11/13 8:49 AM: ---------------------------------------------------------- The suggested fix is here: https://github.com/richfaces/core/tree/feature/RF-12715b I have verified that it works with all the related issues. was (Author: lfryc): The suggested fix is here: https://github.com/richfaces/core/tree/feature/RF-12715b > richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components > -------------------------------------------------------------------------------------- > > Key: RF-12715 > URL: https://issues.jboss.org/browse/RF-12715 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.CR1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The searchForComponentRootOrReturn function in richfaces.js was created to correct the source element of jsf events to jsf components. However the check of whether an element belongs to a component fails for non JSF components. > A concrete example of this failure can be seen when an event generates from a nested _f:ajax_ tag. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12715) richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12715?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12715: --------------------------------- The suggested fix is here: https://github.com/richfaces/core/tree/feature/RF-12715b > richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components > -------------------------------------------------------------------------------------- > > Key: RF-12715 > URL: https://issues.jboss.org/browse/RF-12715 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.CR1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The searchForComponentRootOrReturn function in richfaces.js was created to correct the source element of jsf events to jsf components. However the check of whether an element belongs to a component fails for non JSF components. > A concrete example of this failure can be seen when an event generates from a nested _f:ajax_ tag. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12707) rich:calendar - setValue(...) method from javascript API doesn't work correctly

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12707?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12707: --------------------------------- Hey Jan, I have tried that and it works fine (I'm testing with Mojarra 2.1.17 on Tomcat 7). > rich:calendar - setValue(...) method from javascript API doesn't work correctly > ------------------------------------------------------------------------------- > > Key: RF-12707 > URL: https://issues.jboss.org/browse/RF-12707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.CR1 > Environment: RichFaces 4.3.0-SNAPSHOT > Metamer 4.3.0-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux > Firefox 16.0 @ Linux x86_64 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12706) packed resources generate more than one css file with the same name

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12706?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-12706: ------------------------------------ Could you please provide more information? I cannot reproduce the issue. Your code sample generates this output: {code:xml} <head> <title>JSF Test</title> <link type="text/css" rel="stylesheet" href="/metamer/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.3.0.20121214-M3/PackedCompressed/blueSky/skinning.css" /> <script type="text/javascript" src="/metamer/faces/javax.faces.resource/jsf.js?ln=javax.faces"></script> <script type="text/javascript" src="/metamer/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.3.0.20121214-M3/PackedCompressed/jquery.js"></script> <script type="text/javascript" src="/metamer/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.3.0.20121214-M3/PackedCompressed/packed/packed.js"></script> <link type="text/css" rel="stylesheet" href="/metamer/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.3.0.20121214-M3/PackedCompressed/blueSky/packed/packed.css" /> </head> {code} > packed resources generate more than one css file with the same name > ------------------------------------------------------------------- > > Key: RF-12706 > URL: https://issues.jboss.org/browse/RF-12706 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.M3 > Environment: Richfaces 4.3.0.M3, myfaces-2.1.10 > Reporter: Rene O > > Simple Testcase: > Use at least two different richfaces-components and you can see, that there appear more than one packed-css resource with the same name, which is not the expected behaviour. > This issue appear within firefox, chrome and ie8 > {code:title=web.xml} > ... > <context-param> > <param-name>org.richfaces.resourceMapping.enabled</param-name> > <param-value>true</param-value> > </context-param> > <context-param> > <param-name>org.richfaces.resourceMapping.packedStages</param-name> > <param-value>All</param-value> > </context-param> > ... > {code} > {code:title=testpage.xhtml} > <!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:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > > > <h:head> > <title>JSF Test</title> > </h:head> > <h:body> > <h:form id="testForm"> > <rich:panel id="testPanel"> > <f:facet name="header"> > Test > </f:facet> > Content > </rich:panel> > > <rich:select id="select" value="none"> > <f:selectItem itemLabel="label" itemValue="test"/> > </rich:select> > </h:form> > </h:body> > </html> > {code} > {code:title=html-output} > <link rel="stylesheet" media="screen" type="text/css" href="/jsftest/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.3.0.20121214-M3/PackedCompressed/DEFAULT/packed/packed.css" /> > <link rel="stylesheet" media="screen" type="text/css" href="/jsftest/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.3.0.20121214-M3/PackedCompressed/DEFAULT/packed/packed.css" /> > {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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12715) richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12715?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12715 at 1/11/13 7:58 AM: ---------------------------------------------------------- Note that we doesn't have to fix JSF component's behavior here - only fix specific for RichFaces components is needed. RichFaces components does infer behaviour-source dynamically, based on the element where the behavior event occurred. This is exactly what {{searchForComponentOrReturn}} do - identify where behavior event occured and if its RichFaces component, it will re-target an event source. was (Author: lfryc): Note that we doesn't have to fix JSF component's behavior here - only fix specific for RichFaces components is needed. RichFaces components does infer behaviour-source dynamically, based on the element where the behavior event occurred. This is exactly what {{searchForComponentOrReturn}} - identify where behavior event occured and if its RichFaces component, it will re-target an event source. > richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components > -------------------------------------------------------------------------------------- > > Key: RF-12715 > URL: https://issues.jboss.org/browse/RF-12715 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.CR1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The searchForComponentRootOrReturn function in richfaces.js was created to correct the source element of jsf events to jsf components. However the check of whether an element belongs to a component fails for non JSF components. > A concrete example of this failure can be seen when an event generates from a nested _f:ajax_ tag. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12715) richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12715?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12715 at 1/11/13 7:58 AM: ---------------------------------------------------------- Note that we doesn't have to fix JSF component's behavior here - only fix specific for RichFaces components is needed. RichFaces components does infer behaviour-source dynamically, based on the element where the behavior event occurred. This is exactly what {{searchForComponentOrReturn}} intents to do - identify where behavior event occured and if its RichFaces component, it will re-target an event source. was (Author: lfryc): Note that we doesn't have to fix JSF component's behavior here - only fix specific for RichFaces components is needed. RichFaces components does infer behaviour-source dynamically, based on the element where the behavior event occurred. This is exactly what {{searchForComponentOrReturn}} do - identify where behavior event occured and if its RichFaces component, it will re-target an event source. > richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components > -------------------------------------------------------------------------------------- > > Key: RF-12715 > URL: https://issues.jboss.org/browse/RF-12715 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.CR1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The searchForComponentRootOrReturn function in richfaces.js was created to correct the source element of jsf events to jsf components. However the check of whether an element belongs to a component fails for non JSF components. > A concrete example of this failure can be seen when an event generates from a nested _f:ajax_ tag. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12707) rich:calendar - setValue(...) method from javascript API doesn't work correctly

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12707?page=com.atlassian.jira.plugin.s... ] Jan Papousek updated RF-12707: ------------------------------ Environment: RichFaces 4.3.0-SNAPSHOT Metamer 4.3.0-SNAPSHOT JBoss Application Server: Weld Integration 7.1.1.Final JBoss AS 7.1.1.Final Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux Firefox 16.0 @ Linux x86_64 was: RichFaces 4.3.0-SNAPSHOT Metamer 4.3.0-SNAPSHOT JBoss Application Server: Weld Integration 7.1.1.Final JBoss AS 7.1.1.Final Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux Firefox 16.0 @ Linux x86_64 > rich:calendar - setValue(...) method from javascript API doesn't work correctly > ------------------------------------------------------------------------------- > > Key: RF-12707 > URL: https://issues.jboss.org/browse/RF-12707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.CR1 > Environment: RichFaces 4.3.0-SNAPSHOT > Metamer 4.3.0-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux > Firefox 16.0 @ Linux x86_64 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12715) richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12715?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12715: --------------------------------- Note that we doesn't have to fix JSF component's behavior here - only fix specific for RichFaces components is needed. RichFaces components does infer behaviour-source dynamically, based on the element where the behavior event occurred. This is exactly what {{searchForComponentOrReturn}} - identify where behavior event occured and if its RichFaces component, it will re-target an event source. > richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components > -------------------------------------------------------------------------------------- > > Key: RF-12715 > URL: https://issues.jboss.org/browse/RF-12715 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.CR1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The searchForComponentRootOrReturn function in richfaces.js was created to correct the source element of jsf events to jsf components. However the check of whether an element belongs to a component fails for non JSF components. > A concrete example of this failure can be seen when an event generates from a nested _f:ajax_ tag. -- 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

13 years, 2 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 January 2013