April 2013 - richfaces-issues - Jboss List Archives

[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 updated RF-12839: ------------------------------- Sprint: 4.3.2 Sprint 1 > 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 > 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

[JBoss JIRA] (RF-12843) Apply unix style line-endings to the entire codebase

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12843?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12843: ------------------------------- Sprint: 4.3.2 Sprint 1 > Apply unix style line-endings to the entire codebase > ---------------------------------------------------- > > Key: RF-12843 > URL: https://issues.jboss.org/browse/RF-12843 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Fix For: 4.3.2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Having only unix-style line-endings in place will ease the backporting of issues from RichFaces 5. -- 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-12848) Error "source is not defined" after richfaces-jsf-event.js merge

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12848?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12848: ------------------------------- Sprint: 4.3.2 Sprint 1 > Error "source is not defined" after richfaces-jsf-event.js merge > ---------------------------------------------------------------- > > Key: RF-12848 > URL: https://issues.jboss.org/browse/RF-12848 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.1 > Reporter: Torben Greiser > Priority: Critical > Labels: regression > Fix For: 4.3.2, 5-Tracking > > Attachments: rf12848_1.xhtml > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Commit 9255380d626227d909bbcd59ea3bc604966ea5bb breaks the following jsf.ajax.request: > {code} > jsf.ajax.request("MyContainer:MySelectionForm", "valueChange", {}); > {code} > In <a4j:log/> the following error is displayed: > {code} > richfaces.queue: ajax submit error: source is not defined > {code} > After inspecting richfaces.js I located the cause of the error: > {code} > var getFormElement = function(sourceElement) { > if ($(sourceElement).is('form')) { > return source; > } else { > return $('form').has(sourceElement).get(0); > } > }; > {code} > First if-statement evaluates to true, returning source, which itself is not defined: > {code} > ReferenceError: source is not defined > {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-12688) Upgrade Guava from 11.02 to 13.0.1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12688?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12688: ------------------------------- Sprint: RF5 Alpha1 Sprint 4, 4.3.2 Sprint 1 (was: RF5 Alpha1 Sprint 4) > Upgrade Guava from 11.02 to 13.0.1 > ---------------------------------- > > Key: RF-12688 > URL: https://issues.jboss.org/browse/RF-12688 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Assignee: Lukáš Fryč > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The Guava version used by RF is 11.0.2. However, there is 13.0.1 (or even 14.0-rc1). -- 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: 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-12784) Showcase readme - update deployment from eclipse part

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12784: ------------------------------- Sprint: 4.3.1 Sprint - Fixes, 4.3.2 Sprint 1 (was: 4.3.1 Sprint - Fixes) > Showcase readme - update deployment from eclipse part > ----------------------------------------------------- > > Key: RF-12784 > URL: https://issues.jboss.org/browse/RF-12784 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.3.0.Final, 5-Tracking > Reporter: Juraj Húska > Assignee: Juraj Húska > Priority: Trivial > Fix For: 4.3.2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The deployment of the showcase from eclipse needs to be written down in in more details, because it is not trivial: > An user needs to be aware of: > * select correct maven profile > * alter the deployment assembly > * be aware of wrong context root load in the eclipse browser > I will send pull request for this one. -- 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-12688) Upgrade Guava from 11.02 to 13.0.1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12688?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12688: ------------------------------- Sprint: RF5 Alpha1 Sprint 4 (was: RF5 Alpha1 Sprint 4, RF5 Alpha1 Sprint 4) > Upgrade Guava from 11.02 to 13.0.1 > ---------------------------------- > > Key: RF-12688 > URL: https://issues.jboss.org/browse/RF-12688 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Assignee: Lukáš Fryč > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The Guava version used by RF is 11.0.2. However, there is 13.0.1 (or even 14.0-rc1). -- 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-12893) Partial response not ended correctly on exception

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12893?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12893: ------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > Partial response not ended correctly on exception > ------------------------------------------------- > > Key: RF-12893 > URL: https://issues.jboss.org/browse/RF-12893 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.1 > Reporter: Bernard Labno > Priority: Critical > Fix For: 4.3.2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When there is an exception during ajax request the DeferredEndingPartialResponseWriter.finallyEndDocument is not called. > This may be a bug of JSF http://grepcode.com/file/repo1.maven.org/maven2/com.sun.faces/jsf-impl/2.... > As there is no finallyEndDocument call. -- 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-12688) Upgrade Guava from 11.02 to 13.0.1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12688?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12688: ------------------------------- Fix Version/s: (was: 5.0.0.Alpha1) > Upgrade Guava from 11.02 to 13.0.1 > ---------------------------------- > > Key: RF-12688 > URL: https://issues.jboss.org/browse/RF-12688 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Assignee: Lukáš Fryč > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The Guava version used by RF is 11.0.2. However, there is 13.0.1 (or even 14.0-rc1). -- 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-12370) Push: Add configuration option for max session's inactive interval

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/RF-12370?page=com.atlassian.jira.plugin.s... ] Cody Lerum commented on RF-12370: --------------------------------- Dropping the following into web.xml appears to be a workaround if you can't move to 4.3.x yet (35 second timeout) {code} <context-param> <param-name>org.atmosphere.cpr.CometSupport.maxInactiveActivity</param-name> <param-value>35000</param-value> </context-param> {code} > Push: Add configuration option for max session's inactive interval > ------------------------------------------------------------------ > > Key: RF-12370 > URL: https://issues.jboss.org/browse/RF-12370 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.2.2.Final > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.0.M1 > > > When investigating RF-12219, I have found, the sessions aren't destroyed when client disconnects properly ({{$_atmosphere.unsubscribe()}} on {{window.unload}}). > We should allow to configure maximum time before the Session gets destroyed automatically. > {code:xml} > <context-param> > <param-name>org.richfaces.push.session.maxInactiveInterval</param-name> >  > <param-value>300000</param-value> > </context-param> > {code} > Further investigations in scope of RF-12219 are needed. -- 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