April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12858) rich:calendar dateselect event is fired twice

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12858?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12858: ------------------------------- Sprint: RF 4.3.2 Sprint 2 > rich:calendar dateselect event is fired twice > --------------------------------------------- > > Key: RF-12858 > URL: https://issues.jboss.org/browse/RF-12858 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.1 > Reporter: Michal Petrov > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > <rich:calendar oncurrentdateselect="alert('Date selected')" /> > 1. open the calendar popup > 2. click on the month in the header > 3. select month/year and click "OK" > The alert will pop up twice. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12858) rich:calendar dateselect event is fired twice

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12858?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12858: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > rich:calendar dateselect event is fired twice > --------------------------------------------- > > Key: RF-12858 > URL: https://issues.jboss.org/browse/RF-12858 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.1 > Reporter: Michal Petrov > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > <rich:calendar oncurrentdateselect="alert('Date selected')" /> > 1. open the calendar popup > 2. click on the month in the header > 3. select month/year and click "OK" > The alert will pop up twice. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12812) Autocomplete does not hide popup on tabbing to the next field

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12812?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12812: ------------------------------- Sprint: RF 4.3.2 Sprint 2 > Autocomplete does not hide popup on tabbing to the next field > ------------------------------------------------------------- > > Key: RF-12812 > URL: https://issues.jboss.org/browse/RF-12812 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.Final > Reporter: Timothy Whitehead > Labels: autocomplete > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12812) Autocomplete does not hide popup on tabbing to the next field

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12812?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12812: ------------------------------- Fix Version/s: 4.3.2 (was: 5-Tracking) > Autocomplete does not hide popup on tabbing to the next field > ------------------------------------------------------------- > > Key: RF-12812 > URL: https://issues.jboss.org/browse/RF-12812 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.Final > Reporter: Timothy Whitehead > Labels: autocomplete > Fix For: 4.3.2 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12928) ExtendedDataTable: columnsOrder doesnt work after changing order

by dako ak (JIRA)

[ https://issues.jboss.org/browse/RF-12928?page=com.atlassian.jira.plugin.s... ] dako ak commented on RF-12928: ------------------------------ In Version 4.2.2 the attribute columnsOrder works as expected > ExtendedDataTable: columnsOrder doesnt work after changing order > ---------------------------------------------------------------- > > Key: RF-12928 > URL: https://issues.jboss.org/browse/RF-12928 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.1 > Environment: Tomcat 7, Mojarra 2.1.21 > Reporter: dako ak > Attachments: JSF2-RichFaces-Test.zip > > > According to the resolved bug RF-11776 I've tried the attribute "columnsOrder" in ExtendedDataTable. > I have a simple test case with a data table and an action button. Within the action button method I change the String Array of the attribute columnsOrder but the columns of the data table is rendered in the old order. > I have appended a test project to reproduce it. In this test project I have an a4j ajax button and a simple button, both arent working. > Best regards -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12928) ExtendedDataTable: columnsOrder doesnt work after changing order

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/RF-12928?page=com.atlassian.jira.plugin.s... ] SBS JIRA Integration updated RF-12928: -------------------------------------- Forum Reference: https://community.jboss.org/message/808816#808816 > ExtendedDataTable: columnsOrder doesnt work after changing order > ---------------------------------------------------------------- > > Key: RF-12928 > URL: https://issues.jboss.org/browse/RF-12928 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.1 > Environment: Tomcat 7, Mojarra 2.1.21 > Reporter: dako ak > Attachments: JSF2-RichFaces-Test.zip > > > According to the resolved bug RF-11776 I've tried the attribute "columnsOrder" in ExtendedDataTable. > I have a simple test case with a data table and an action button. Within the action button method I change the String Array of the attribute columnsOrder but the columns of the data table is rendered in the old order. > I have appended a test project to reproduce it. In this test project I have an a4j ajax button and a simple button, both arent working. > Best regards -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12833) richfaces.js conflicts with prototype.js

by J W (JIRA)

[ https://issues.jboss.org/browse/RF-12833?page=com.atlassian.jira.plugin.s... ] J W commented on RF-12833: -------------------------- I have signed them already last week. The status is saying "Awaiting approval by community lead" > richfaces.js conflicts with prototype.js > ---------------------------------------- > > Key: RF-12833 > URL: https://issues.jboss.org/browse/RF-12833 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.1 > Reporter: Mark Torres > Fix For: 5-Tracking > > Attachments: RF-12833.patch > > > Getting some javascript errors on richfaces.js. > Upon inspection, it is using > {code} > (function(jQuery, richfaces) { > ... > {code} > instead of > {code} > (function($, richfaces) { > ... > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12897) ExtendedPartialViewContextImpl swallows exceptions

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12897?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12897: ---------------------------------- Assignee: Brian Leathem (was: Lukáš Fryč) > ExtendedPartialViewContextImpl swallows exceptions > -------------------------------------------------- > > Key: RF-12897 > URL: https://issues.jboss.org/browse/RF-12897 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.2.Final > Environment: Windows 7, JDK 1.6 > Reporter: Cristian Cerb > Assignee: Brian Leathem > Priority: Critical > Labels: richfaces > Fix For: 4.3.2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Method public VisitResult visit(VisitContext context, UIComponent target) of class ExtendedPartialViewContextImpl swallows exceptions. I think exceptions should be wrapped inside a FaceException and propagated. This class http://java.net/projects/mojarra/sources/svn/content/trunk/jsf-ri/src/mai... seems to have served as a model for the RF one, but the RF class inadvertently chose to swallow exceptions instead of propagating them up. This causes unpredictable behaviour, such as system being stuck in the browser. > I just found an older version of Sun's Mojarra where they had the same issue, but the newer versions seem to have fixed it. See this taken from jsf 2.1.4: > {code} > public VisitResult visit(VisitContext context, UIComponent comp) { > try { > if (curPhase == PhaseId.APPLY_REQUEST_VALUES) { > // RELEASE_PENDING handle immediate request(s) > // If the user requested an immediate request > // Make sure to set the immediate flag here. > comp.processDecodes(ctx); > } else if (curPhase == PhaseId.PROCESS_VALIDATIONS) { > comp.processValidators(ctx); > } else if (curPhase == PhaseId.UPDATE_MODEL_VALUES) { > comp.processUpdates(ctx); > } else if (curPhase == PhaseId.RENDER_RESPONSE) { > PartialResponseWriter writer = ctx.getPartialViewContext().getPartialResponseWriter(); > writer.startUpdate(comp.getClientId(ctx)); > try { > // do the default behavior... > comp.encodeAll(ctx); > } > catch (Exception ce) { > if (LOGGER.isLoggable(Level.SEVERE)) { > LOGGER.severe(ce.toString()); > } > if (LOGGER.isLoggable(Level.FINE)) { > LOGGER.log(Level.FINE, > ce.toString(), > ce); > } > } > writer.endUpdate(); > } > else { > throw new IllegalStateException("I18N: Unexpected " + > "PhaseId passed to " + > " PhaseAwareContextCallback: " + > curPhase.toString()); > } > } > catch (IOException ex) { > ex.printStackTrace(); > } > // Once we visit a component, there is no need to visit > // its children, since processDecodes/Validators/Updates and > // encodeAll() already traverse the subtree. We return > // VisitResult.REJECT to supress the subtree visit. > return VisitResult.REJECT; > } > } > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12897) ExtendedPartialViewContextImpl swallows exceptions

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12897?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12897: --------------------------------- Hey Cristian, I'm available on the channel all the time I work, but since we are closing {{4.2.3}} soon, it would be nice if you'll write your ideas down e.g. here or to the forums. > ExtendedPartialViewContextImpl swallows exceptions > -------------------------------------------------- > > Key: RF-12897 > URL: https://issues.jboss.org/browse/RF-12897 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.2.Final > Environment: Windows 7, JDK 1.6 > Reporter: Cristian Cerb > Assignee: Lukáš Fryč > Priority: Critical > Labels: richfaces > Fix For: 4.3.2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Method public VisitResult visit(VisitContext context, UIComponent target) of class ExtendedPartialViewContextImpl swallows exceptions. I think exceptions should be wrapped inside a FaceException and propagated. This class http://java.net/projects/mojarra/sources/svn/content/trunk/jsf-ri/src/mai... seems to have served as a model for the RF one, but the RF class inadvertently chose to swallow exceptions instead of propagating them up. This causes unpredictable behaviour, such as system being stuck in the browser. > I just found an older version of Sun's Mojarra where they had the same issue, but the newer versions seem to have fixed it. See this taken from jsf 2.1.4: > {code} > public VisitResult visit(VisitContext context, UIComponent comp) { > try { > if (curPhase == PhaseId.APPLY_REQUEST_VALUES) { > // RELEASE_PENDING handle immediate request(s) > // If the user requested an immediate request > // Make sure to set the immediate flag here. > comp.processDecodes(ctx); > } else if (curPhase == PhaseId.PROCESS_VALIDATIONS) { > comp.processValidators(ctx); > } else if (curPhase == PhaseId.UPDATE_MODEL_VALUES) { > comp.processUpdates(ctx); > } else if (curPhase == PhaseId.RENDER_RESPONSE) { > PartialResponseWriter writer = ctx.getPartialViewContext().getPartialResponseWriter(); > writer.startUpdate(comp.getClientId(ctx)); > try { > // do the default behavior... > comp.encodeAll(ctx); > } > catch (Exception ce) { > if (LOGGER.isLoggable(Level.SEVERE)) { > LOGGER.severe(ce.toString()); > } > if (LOGGER.isLoggable(Level.FINE)) { > LOGGER.log(Level.FINE, > ce.toString(), > ce); > } > } > writer.endUpdate(); > } > else { > throw new IllegalStateException("I18N: Unexpected " + > "PhaseId passed to " + > " PhaseAwareContextCallback: " + > curPhase.toString()); > } > } > catch (IOException ex) { > ex.printStackTrace(); > } > // Once we visit a component, there is no need to visit > // its children, since processDecodes/Validators/Updates and > // encodeAll() already traverse the subtree. We return > // VisitResult.REJECT to supress the subtree visit. > return VisitResult.REJECT; > } > } > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12839) Toggle panels: ajax-related attributes do not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12839?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12839: ------------------------------------ Fixed the regression of tab ajax attributes not working for 4.3.2. We should create a new issue for RF 5 to address aligning the ajax attributes of the various togglepanel items. > Toggle panels: ajax-related attributes do not work > -------------------------------------------------- > > Key: RF-12839 > URL: https://issues.jboss.org/browse/RF-12839 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.1 > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 4.3.2-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.3.Final-redhat-4 > JBoss AS 7.1.3.Final-redhat-4 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 25.0.1364.160 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # set oncomplete to "alert('complete')" > # switch to tab 2 and back to tab 1 > result: > * alert should be diplayed but isn't > * tabs are correctly switched > * worked fine in 4.2.3.Final > * several attributes don't work - onbegin, onbeforedomupdate, oncomplete, data, execute, immediate, render, limitRender, status > * affected components: tab, toggle panel item, accordion item -- 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, 11 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 April 2013