February 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13278) Add support for a 'header' meta-component to the rich:tabPanel

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-13278. ---------------------------- Verified. Closing. > Add support for a 'header' meta-component to the rich:tabPanel > -------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <!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:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > <h:head> > </h:head> > <h:body> > > <a4j:log hotkey="M" mode="popup" /> > <h:form id="form" prependId="false"> > <rich:tabPanel id="tabPanel"> > <rich:tab header="tab 1"> > <a4j:commandLink value="click me" action="#{testBean.put('clicks',testBean.clicks + 1)}" render="label" execute="@this" /> > </rich:tab> > <rich:tab> > <f:facet name="header"> > <h:outputText id="label" value="#{testBean.clicks} clicks" /> > </f:facet> > </rich:tab> > </rich:tabPanel> > </h:form> > </h:body> > </html> > {code} > testBean is a simple session-scoped HashMap. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13528) Slider and spinner don't work inside tables

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-13528: ---------------------------------- Summary: Slider and spinner don't work inside tables Key: RF-13528 URL: https://issues.jboss.org/browse/RF-13528 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input, regression Affects Versions: 5.0.0.Alpha2, 5.0.0.Alpha3 Environment: RichFaces 5.0.0.Alpha2, 5.0.0.Alpha3 Metamer 5.0.0.20131203-Alpha2 JBoss Application Server: Weld Integration 7.3.0.Final-redhat-14 JBoss AS 7.3.0.Final-redhat-14 Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Chrome 32.0.1700.102 @ Linux x86_64 Reporter: Pavol Pitonak # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/simp... # change value on slider result: * the output below the slider doesn't change * last version known to work in 5.0.0.Alpha1 * it works fine when you use f:ajax instead of r:ajax, see http://localhost:8080/metamer/faces/components/richInputNumberSlider/fAja... -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12865) Correct deferred partial response ending by leveraging PVC wrapper chain

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12865?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12865 at 2/3/14 8:49 AM: --------------------------------------------------------- The proper fix for DIRECT/WRAPPED modes leverages wrapping of both {{PartialViewContext}} and {{(Partial)VisitContext}} and is addressed in RF-13505. Mojarra's fix is needed here, see the associated issue. was (Author: lfryc): The proper fix for DIRECT/WRAPPED modes leverages wrapping of both {{PartialViewContext}} and {{(Partial)VisitContext}} and is addressed in RF-13505. Mojarra's fix is needed here, see the upgrade issue. > Correct deferred partial response ending by leveraging PVC wrapper chain > ------------------------------------------------------------------------ > > Key: RF-12865 > URL: https://issues.jboss.org/browse/RF-12865 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.1 > Environment: weblogic 10.3.4, Myfaces 2.1.10, Richfaces 4.3.1, OmniFaces1.3 > Reporter: blam lam > Assignee: Lukáš Fryč > Labels: jsf, needs-qe > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > After submit from a a4j:commandButton, it fail to re-render / update other component on the page. > This problem only appear in MyFaces. It does not happens in Mojarra. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12865) Correct deferred partial response ending by leveraging PVC wrapper chain

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12865?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12865: --------------------------------- The proper fix for DIRECT/WRAPPED modes leverages wrapping of both {{PartialViewContext}} and {{(Partial)VisitContext}} and is addressed in RF-13505. Mojarra's fix is needed here, see the upgrade issue. > Correct deferred partial response ending by leveraging PVC wrapper chain > ------------------------------------------------------------------------ > > Key: RF-12865 > URL: https://issues.jboss.org/browse/RF-12865 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 4.3.1 > Environment: weblogic 10.3.4, Myfaces 2.1.10, Richfaces 4.3.1, OmniFaces1.3 > Reporter: blam lam > Assignee: Lukáš Fryč > Labels: jsf, needs-qe > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > After submit from a a4j:commandButton, it fail to re-render / update other component on the page. > This problem only appear in MyFaces. It does not happens in Mojarra. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13251 at 2/3/14 8:47 AM: --------------------------------------------------------- Immo, could you please provide the sample code you reproduced the issue with? Without it we can't proceed with a fix. was (Author: lfryc): could you please provide the sample code you reproduced the issue with? Without it we can't proceed with a fix. > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Lukáš Fryč > Priority: Minor > Labels: waiting_on_user > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13251: --------------------------------- could you please provide the sample code you reproduced the issue with? Without it we can't proceed with a fix. > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Lukáš Fryč > Priority: Minor > Labels: waiting_on_user > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13527) File upload: ajax-rendered panel not updated after uploading file

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-13527: ---------------------------------- Summary: File upload: ajax-rendered panel not updated after uploading file Key: RF-13527 URL: https://issues.jboss.org/browse/RF-13527 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input, regression Affects Versions: 5.0.0.Alpha3 Environment: RichFaces 5.0.0-SNAPSHOT, 5.0.0.Alpha3 Metamer 5.0.0-SNAPSHOT Mojarra 2.1.19-jbossorg-1 EAP 6.2 Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Chrome 32.0.1700.102 @ Linux x86_64 Reporter: Pavol Pitonak # deploy Metamer and open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml # notice time in top-right corner above phases list # upload a small file result: * expected: content of outputPanel with ajaxRendered=true should be updated * actual: there is the same time in the panel * it's a regression, it is updated correctly in 5.0.0.Alpha2 -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13454) Upgrade integration tests use of WildFly to 8.0.0.CR1

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13454?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-13454. ---------------------------- Verified. Closing. > Upgrade integration tests use of WildFly to 8.0.0.CR1 > ----------------------------------------------------- > > Key: RF-13454 > URL: https://issues.jboss.org/browse/RF-13454 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha3 > > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13432) Upgrade framework build to JSF 2.2

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13432?page=com.atlassian.jira.plugin.s... ] Juraj Húska closed RF-13432. ---------------------------- Verified. Closing. > Upgrade framework build to JSF 2.2 > ---------------------------------- > > Key: RF-13432 > URL: https://issues.jboss.org/browse/RF-13432 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Affects Versions: 5.0.0.Alpha3 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha3 > > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13526) Update Drone to 1.2.3 and Graphene to 2.0.1

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13526?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-13526. ----------------------------- Resolution: Done > Update Drone to 1.2.3 and Graphene to 2.0.1 > ------------------------------------------- > > Key: RF-13526 > URL: https://issues.jboss.org/browse/RF-13526 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > -- 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

10 years, 9 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 2014