April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12921) rich:validator: created message is escaped, even if the message component should not be escaped

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12921?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12921: ------------------------------- Fix Version/s: 4.3.2 > rich:validator: created message is escaped, even if the message component should not be escaped > ----------------------------------------------------------------------------------------------- > > Key: RF-12921 > URL: https://issues.jboss.org/browse/RF-12921 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux > Firefox 18.0 @ Linux x86_64 > Reporter: Jiří Štefek > Priority: Minor > Fix For: 4.3.2 > > > The created message is always escaped, even if the message component has its attribute @escape=false. > Message components: rich:message, rich:messages, rich:notifyMessage, rich:notifyMessages. -- 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-12910) Include the built WARs in distribution

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12910?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12910. -------------------------------- Resolution: Won't Fix > Include the built WARs in distribution > -------------------------------------- > > Key: RF-12910 > URL: https://issues.jboss.org/browse/RF-12910 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > > The distribution currently contains just sources of WAR example projects (photoalbum / showcase). > Some users might want just deploy those WARs and do not work with project sources, thus I propose to include built WARs directly. -- 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-12193) rich:extendedDataTable is blank on show

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12193?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12193: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > rich:extendedDataTable is blank on show > --------------------------------------- > > Key: RF-12193 > URL: https://issues.jboss.org/browse/RF-12193 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.1.Final > Environment: Firefox 11, Internet Explorer 8 > Reporter: Nick Dev > Fix For: 4.3.2, 5-Tracking > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > rich:extendedDataTable is blank when shown after it was hidden. > Firefox: complete table is blank. > IE: table header is not displayed. > Table is shown after resizing the window. -- 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 updated RF-12897: ------------------------------- Original Estimate: 4 hours (was: 4 minutes) Remaining Estimate: 4 hours (was: 4 minutes) > 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 Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12897?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12897: ------------------------------- Original Estimate: 4 minutes Remaining Estimate: 4 minutes > 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 minutes > Remaining Estimate: 4 minutes > > 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 Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12897?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12897: ------------------------------- Sprint: RF5 Alpha1 Sprint 4 > 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 > > > 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-12193) rich:extendedDataTable is blank on show

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12193?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12193: ------------------------------- Sprint: RF5 Alpha1 Sprint 4 > rich:extendedDataTable is blank on show > --------------------------------------- > > Key: RF-12193 > URL: https://issues.jboss.org/browse/RF-12193 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.1.Final > Environment: Firefox 11, Internet Explorer 8 > Reporter: Nick Dev > Fix For: 4.3.2, 5-Tracking > > > rich:extendedDataTable is blank when shown after it was hidden. > Firefox: complete table is blank. > IE: table header is not displayed. > Table is shown after resizing the window. -- 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-12849) Showcase - update readme - remove obsolete, add new

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12849?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12849: ------------------------------- Sprint: RF5 Alpha1 Sprint 4, 4.3.2 Sprint 1 (was: 4.3.2 Sprint 1) > Showcase - update readme - remove obsolete, add new > --------------------------------------------------- > > Key: RF-12849 > URL: https://issues.jboss.org/browse/RF-12849 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.3.1 > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 4.3.2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > After rewriting showcase readme to markdown syntax I would update it for example with following: > * reference to showcase online demo > * remove publishing to GAE and put there publishing to Openshift instead > * I would create small clickable TOC in the top of the page > * remove deploying on JBoss AS 6 and maybe add deploying on EAP 6 (it is now available to download) > * Mention JBDS as an option -- 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-12469) Setup continuous integration

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12469?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak resolved RF-12469. -------------------------------- Resolution: Done There are three jobs at the moment: # buildhive which builds after every change in richfaces5 repo (master branch, feature branches, pull requests), runs smoke tests with PhantomJS # richfaces-5.0 job on JBoss Jenkins which builds master branch and deploys artefacts to jboss.org Nexus, runs smoke tests with PhantomJS # richfaces-5.0-ff job on JBoss Jenkins which builds master branch, runs all tests with latest Firefox (now 19) I'll setup Jenkins jobs with other browsers as soon as they are available. Metamer tests are being implemented outside of this JIRA by Juraj. > Setup continuous integration > ---------------------------- > > Key: RF-12469 > URL: https://issues.jboss.org/browse/RF-12469 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: qe > Reporter: Lukáš Fryč > Assignee: Pavol Pitonak > Labels: rf5-build > Fix For: 5.0.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Jenkins + BuildHive -- 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 don't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12839?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12839. -------------------------------- Resolution: Done > Toggle panels: ajax-related attributes don't 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 > 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