February 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12689) Upgrade Atmosphere from 1.0.1 to 1.0.9

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12689?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-12689: ------------------------------- Assignee: Lukáš Fryč > Upgrade Atmosphere from 1.0.1 to 1.0.9 > -------------------------------------- > > Key: RF-12689 > URL: https://issues.jboss.org/browse/RF-12689 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution, component-push/poll > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Assignee: Lukáš Fryč > Fix For: 4.3.1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 4.3.0.M3 still uses Atmosphere 1.0.1. However, there is 1.0.7 (or even 1.1.0.beta2) -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12788) org.richfaces.javascript.QUnitTest fails in WFK 2.2

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12788?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-12788: ------------------------------- Assignee: Lukáš Fryč > org.richfaces.javascript.QUnitTest fails in WFK 2.2 > --------------------------------------------------- > > Key: RF-12788 > URL: https://issues.jboss.org/browse/RF-12788 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core, tests - unit > Affects Versions: 4.3.0.Final > Environment: WFK 2.2 > Reporter: Marek Novotny > Assignee: Lukáš Fryč > Fix For: 4.3.1 > > Attachments: org.richfaces.javascript.QUnitTest.txt > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > we can see that CI job reports a few failed tests (8 from > 167) in org.richfaces.javascript.QUnitTest > {code} > Results : > Failed tests: testEvent(org.richfaces.javascript.QUnitTest): Failures:(..) > testPosition(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueRequest(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueGetSize(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueEmpty(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueClear(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueSubmitFirst(org.richfaces.javascript.QUnitTest): Failures:(..) > testBaseComponent(org.richfaces.javascript.QUnitTest): Failures:(..) > Tests run: 167, Failures: 8, Errors: 0, Skipped: 2 > Output from failed build is at > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/WFK/view/WFK-2.2/jo... > {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12769) Select Component with Manual Input uses first option regardless of what is picked

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12769?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12769: ---------------------------- Sprint: 4.3.1 Sprint - Critical + tabs > Select Component with Manual Input uses first option regardless of what is picked > --------------------------------------------------------------------------------- > > Key: RF-12769 > URL: https://issues.jboss.org/browse/RF-12769 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.0.M2, 4.3.0.Final > Reporter: Cody Lerum > Assignee: Lukáš Fryč > Labels: regression > Fix For: 4.3.1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Visible on showcase. > Got to select component with manual input. Type "n" then select "New Jersey" > Nebraska will be selected instead. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12689) Upgrade Atmosphere from 1.0.1 to 1.0.9

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12689?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12689: ---------------------------- Sprint: 4.3.1 Sprint - Critical + tabs > Upgrade Atmosphere from 1.0.1 to 1.0.9 > -------------------------------------- > > Key: RF-12689 > URL: https://issues.jboss.org/browse/RF-12689 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution, component-push/poll > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Fix For: 4.3.1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 4.3.0.M3 still uses Atmosphere 1.0.1. However, there is 1.0.7 (or even 1.1.0.beta2) -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12788) org.richfaces.javascript.QUnitTest fails in WFK 2.2

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12788?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12788: ---------------------------- Sprint: 4.3.1 Sprint - Critical + tabs > org.richfaces.javascript.QUnitTest fails in WFK 2.2 > --------------------------------------------------- > > Key: RF-12788 > URL: https://issues.jboss.org/browse/RF-12788 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core, tests - unit > Affects Versions: 4.3.0.Final > Environment: WFK 2.2 > Reporter: Marek Novotny > Fix For: 4.3.1 > > Attachments: org.richfaces.javascript.QUnitTest.txt > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > we can see that CI job reports a few failed tests (8 from > 167) in org.richfaces.javascript.QUnitTest > {code} > Results : > Failed tests: testEvent(org.richfaces.javascript.QUnitTest): Failures:(..) > testPosition(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueRequest(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueGetSize(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueEmpty(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueClear(org.richfaces.javascript.QUnitTest): Failures:(..) > testQueueSubmitFirst(org.richfaces.javascript.QUnitTest): Failures:(..) > testBaseComponent(org.richfaces.javascript.QUnitTest): Failures:(..) > Tests run: 167, Failures: 8, Errors: 0, Skipped: 2 > Output from failed build is at > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/WFK/view/WFK-2.2/jo... > {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12760) rich:tabPanel does not work after ajax request

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12760?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12760: ---------------------------- Sprint: 4.3.1 Sprint - Critical + tabs > rich:tabPanel does not work after ajax request > ---------------------------------------------- > > Key: RF-12760 > URL: https://issues.jboss.org/browse/RF-12760 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.0.M2, 4.3.0.M3, 4.3.0.CR1, 4.3.0.CR2 > Environment: RichFaces 4.3.0.CR2 > Metamer 4.3.0-SNAPSHOT > Mojarra 2.1.7-jbossorg-2 > JBoss AS 7.1.2.Final-redhat-1 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 24.0.1312.56 @ Linux x86_64 > ----------------------------------------------------------- > Windows 7 - Chrome 24.0.1312.56 / IE 9. > Mojarra 2.1.17 > Richfaces 4.3.0.CR2 > Reporter: Adelmo Erick santos > Assignee: Lukáš Fryč > Labels: regression > Fix For: 4.3.1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > When I submit a ajax request in a h:commandButtom within a tab with f:ajax them the tabPanel don´t switch tabs anymore. The problem is already reported in RF-10112. Sorry i´m from Brazil and my english very bad. > {code} > <!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:rich="http://richfaces.org/rich" > xmlns:a4j="http://richfaces.org/a4j" > > > <h:head> > </h:head> > <h:body> > <h:form> > <rich:tabPanel> > <rich:tab header="cash"> > <h:commandButton value="Enter"> > <f:ajax event="click" render="@form"/> > </h:commandButton> > </rich:tab> > <rich:tab header="creditCard"> > <h:outputText value="Test"/> > </rich:tab> > </rich:tabPanel> > </h:form> > </h:body> > </html> > {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12789) TabPanel error after partial update with new tab

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12789?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12789: ---------------------------- Sprint: 4.3.1 Sprint - Critical + tabs > TabPanel error after partial update with new tab > ------------------------------------------------ > > Key: RF-12789 > URL: https://issues.jboss.org/browse/RF-12789 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.0.CR2 > Environment: Mojarra 2.1.17, Tomcat 7.0.22, Java 1.7, Windows 7 > Reporter: Lutz Ulrich > Labels: Tab, TabPanel, dynamical-add > Fix For: 4.3.1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Adding tabs dynamically (programatically) in partial requests results in errors. > The JavaScript code for all TabPanels and their child Tabs is added to HTML <body> using JavaScriptService.addScript(FacesContext, S), see DivPanelRenderer.writeJavaScript(), TabRenderer.doEncodeItemEnd() and TabRenderer.doEncodeEnd(). > The top-level <script> element in <body> won't be updated if a new Tab is added dynamically in a partial request. Thus, the script, new RichFaces.ui.Tab(...), for the new Tab is missing. > Similar problems arise if a TabPanel is added in a partial request. > All scripts, RichFaces.ui.Tab(...) and RichFaces.ui.TabPanel(...) should be rendered inline for partial update to work with new TabPanels and new Tabs. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12689) Upgrade Atmosphere from 1.0.1 to 1.0.9

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12689?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12689: ---------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Upgrade Atmosphere from 1.0.1 to 1.0.9 > -------------------------------------- > > Key: RF-12689 > URL: https://issues.jboss.org/browse/RF-12689 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution, component-push/poll > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Fix For: 4.3.1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > 4.3.0.M3 still uses Atmosphere 1.0.1. However, there is 1.0.7 (or even 1.1.0.beta2) -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12689) Upgrade Atmosphere from 1.0.1 to 1.0.9

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12689?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12689: ---------------------------- Fix Version/s: 4.3.1 (was: 4.3-Tracking) (was: 5-Tracking) > Upgrade Atmosphere from 1.0.1 to 1.0.9 > -------------------------------------- > > Key: RF-12689 > URL: https://issues.jboss.org/browse/RF-12689 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution, component-push/poll > Affects Versions: 4.3.0.M3 > Reporter: Juergen Zimmermann > Fix For: 4.3.1 > > > 4.3.0.M3 still uses Atmosphere 1.0.1. However, there is 1.0.7 (or even 1.1.0.beta2) -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12543) a4j:push after ajax-rendered does not have its javascript included

by Marc-Christian Schroeer (JIRA)

[ https://issues.jboss.org/browse/RF-12543?page=com.atlassian.jira.plugin.s... ] Marc-Christian Schroeer commented on RF-12543: ---------------------------------------------- Is there any news on that topic? I am in desperate need of being able to partially re-render a page and get a4j:push working within these new parts. > a4j:push after ajax-rendered does not have its javascript included > ------------------------------------------------------------------ > > Key: RF-12543 > URL: https://issues.jboss.org/browse/RF-12543 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: RichFaces 4.2.2 FINAL > Reporter: nimo stephan > Fix For: 5-Tracking > > > I have a4j:push within my page which should be rendered only if the property "pushIsActivated" is true. When changing the property by a button to true, then I want to make a ajax-rendering which renders the a4j:push. However, the javascript portion is not created within the aj4:push, hence the component does not work! I have to make a full page refresh, then the javascript portion is inserted and a4j:push works as expected. However, I have to do a full page refresh. I guess, it is a bug, because the a4j:push has a rendered-property which can be changed by ajax, hence it has to work after ajax-update. > {code} > <h:form id="my-form" prependId="false" style="display:none;"> > <a4j:push rendered="#{mybean.pushIsActivated}" address=".." onerror=".." ondataavailable=".."> > <a4j:ajax event="dataavailable" render="my-section"/> > </a4j:push> > </h:form> > {code} > If I only render my-form after changing the property, a4j:push does not work: > {code} > <h:form> > <h:commandButton value="Activate Push " action="#{myBean.setActivatePushToTrue}"> > <f:ajax render=":my-form"/> > </h:commandButton> > </h:form> > {code} > I have to do a full page refresh, only then aj4:push works: > {code} > <h:form> > <h:commandButton value="Activate Push " action="#{myBean.setPushActivateToTrue}" onclick="submit();" /> > </h:form> > {code} > Richfaces does insert the needed javascript only after a full page request: > {code} > <script type="text/javascript">RichFaces.Push.setPushResourceUrl.....;</script> > {code} > If I make a ajax-rendering, Richfaces does NOT (!) insert the needed javascript. Hence a4j:push does not work. -- 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

11 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2013