November 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13350) pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute

by Juraj Húska (JIRA)

Juraj Húska created RF-13350: -------------------------------- Summary: pickList: styleClass attribute is rendered wrongly as styleclass instead of class attribute Key: RF-13350 URL: https://issues.jboss.org/browse/RF-13350 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 5.0.0.Alpha2 Reporter: Juraj Húska Setting of {{styleClass}} attribute to the {{pickList}} component makes generated markup to contain {{styleclass}} attribute - instead of just adjusted {{class}} attribute. The {{styleClass}} is included just in {{passThrough}} attributes - [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...]. Should not be it done as it is for example [here|https://github.com/richfaces/richfaces/blob/master/framework/src/mai...] in autocomplate render base ? -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-8275) Memory leak with extended data table after repeated rerender

by Chasidy McMaster (JIRA)

[ https://issues.jboss.org/browse/RF-8275?page=com.atlassian.jira.plugin.sy... ] Chasidy McMaster commented on RF-8275: -------------------------------------- >From what I read, RichFaces 4.0 requires JSF 2.0 and we aren't ready to make that leap quite yet. > Memory leak with extended data table after repeated rerender > ------------------------------------------------------------ > > Key: RF-8275 > URL: https://issues.jboss.org/browse/RF-8275 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 3.3.2.SR1 > Environment: Windows xp and AIX, Firefox and Internet Explorer 7 > Reporter: Manuele Piastra > Assignee: Andrey Markhel > Priority: Critical > Labels: extended_datatable, memory_leak, rerender > Fix For: 3.3.3.CR1 > > Attachments: index.xhtml > > > After each rerender of the extended data table the memory allocated to the process iexplorer.exe keeps growing and it is never released. The same test with simple datatable doesn't show this problem. > Snippet code used for the test > <?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"> > <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="1.2" > xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:rich="http://richfaces.org/rich" > xmlns:a4j="http://richfaces.org/a4j"> > <html> > <head> > <title>RichFaces DataTable</title> > </head> > <body> > <f:view> > <h:form> > <a4j:jsFunction name="rerenderTable" reRender="finderList"></a4j:jsFunction> > <rich:dataTable value="#{provaTableBean.list}" var="elem" > id="finderList" width="200px" > > <rich:column id="id" width="50" label="Id"> > <f:facet name="header"> > <h:outputText value="Id" /> > </f:facet> > <h:outputText value="#{elem.id}" /> > </rich:column> > <rich:column id="nome" width="150" label="Nome"> > <f:facet name="header"> > <h:outputText value="Nome" /> > </f:facet> > <h:outputText value="#{elem.nome}" /> > </rich:column> > </rich:dataTable> > </h:form> > </f:view> > <script> > setInterval(rerenderTable, 10000); > </script> > </body> > </html> > </jsp:root> -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13349) a4j:queue must be first child for rich:autocomplete

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13349?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-13349: ------------------------------- Labels: waiting_on_user (was: ) > a4j:queue must be first child for rich:autocomplete > --------------------------------------------------- > > Key: RF-13349 > URL: https://issues.jboss.org/browse/RF-13349 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: alexey plotnikov > Assignee: Pavol Pitonak > Labels: waiting_on_user > > All described here https://community.jboss.org/message/845845 but i'll repeat. > In this example: > {code} > <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}" > minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion" > autofill="false" > onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.legalName}" > required="true"> > <h:column> > <h:outputText style="display:none;" value="#{s.id}"/> > <h:outputText style="display:none;" value="#{s.realName}"/> > </h:column> > <h:column> > <h:outputText value="#{s.name}" escape="false"/> > </h:column> > <a4j:queue requestDelay="500" ignoreDupResponses="true" /> > </rich:autocomplete> > {code} > a4j:queue - is *ignored!* > But here > {code} > <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}" > minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion" > autofill="false" > onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.legalName}" > required="true"> > <a4j:queue requestDelay="500" ignoreDupResponses="true" /> > <h:column> > <h:outputText style="display:none;" value="#{s.id}"/> > <h:outputText style="display:none;" value="#{s.realName}"/> > </h:column> > <h:column> > <h:outputText value="#{s.name}" escape="false"/> > </h:column> > </rich:autocomplete> > {code} > a4j:queue *not ignored*. So a4j:queue must be first child for autocomplete. > For another components a4j:queue can be any child(first or last). > For example this code: > {code} > <h:selectOneMenu value="#{agentMenuMassList.menuProfile}"> > <s:selectItems noSelectionLabel="#{messages['pages.noSelect']}" value="#{agentMenuMassList.menuProfiles}" var="m" label="#{m.name}"/> > <s:convertEntity/> > <a4j:ajax event="change" render="editPanel,menuPanel" listener="#{agentMenuMassList.change}"/> > <a4j:queue requestDelay="5000" /> > </h:selectOneMenu> > {code} > *not* ignoring a4j:queue -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13349) a4j:queue must be first child for rich:autocomplete

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13349?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-13349: ------------------------------------ I could not reproduce with RichFaces 4.3.4.Final. Alexey, could you please provide me more information about your environment, such as OS, browser, JSF version and which app server are you deploying to? > a4j:queue must be first child for rich:autocomplete > --------------------------------------------------- > > Key: RF-13349 > URL: https://issues.jboss.org/browse/RF-13349 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: alexey plotnikov > Assignee: Pavol Pitonak > > All described here https://community.jboss.org/message/845845 but i'll repeat. > In this example: > {code} > <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}" > minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion" > autofill="false" > onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.legalName}" > required="true"> > <h:column> > <h:outputText style="display:none;" value="#{s.id}"/> > <h:outputText style="display:none;" value="#{s.realName}"/> > </h:column> > <h:column> > <h:outputText value="#{s.name}" escape="false"/> > </h:column> > <a4j:queue requestDelay="500" ignoreDupResponses="true" /> > </rich:autocomplete> > {code} > a4j:queue - is *ignored!* > But here > {code} > <rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteLegals}" > minChars="0" var="s" fetchValue="#{s.realName}" id="legal-suggestion" > autofill="false" > onselectitem="autocompleteChangeLegal(event.target)" style="display: inline;" > layout="table" value="#{autocomplete.legalName}" > required="true"> > <a4j:queue requestDelay="500" ignoreDupResponses="true" /> > <h:column> > <h:outputText style="display:none;" value="#{s.id}"/> > <h:outputText style="display:none;" value="#{s.realName}"/> > </h:column> > <h:column> > <h:outputText value="#{s.name}" escape="false"/> > </h:column> > </rich:autocomplete> > {code} > a4j:queue *not ignored*. So a4j:queue must be first child for autocomplete. > For another components a4j:queue can be any child(first or last). > For example this code: > {code} > <h:selectOneMenu value="#{agentMenuMassList.menuProfile}"> > <s:selectItems noSelectionLabel="#{messages['pages.noSelect']}" value="#{agentMenuMassList.menuProfiles}" var="m" label="#{m.name}"/> > <s:convertEntity/> > <a4j:ajax event="change" render="editPanel,menuPanel" listener="#{agentMenuMassList.change}"/> > <a4j:queue requestDelay="5000" /> > </h:selectOneMenu> > {code} > *not* ignoring a4j:queue -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13210) Move RichFaces resources from META-INF/resources/ to org.richfaces library

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13210 at 11/15/13 6:34 AM: ----------------------------------------------------------- No, it's not, we should move RichFaces Core JS resources such as richfaces.js to org.richfaces resource library and re-configure resource packaging. was (Author: lfryc): Note, it's not, we should move RichFaces Core JS resources such as richfaces.js to org.richfaces resource library and re-configure resource packaging. > Move RichFaces resources from META-INF/resources/ to org.richfaces library > -------------------------------------------------------------------------- > > Key: RF-13210 > URL: https://issues.jboss.org/browse/RF-13210 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.3.4, 5.0.0.Alpha1 > 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13210) Move RichFaces resources from META-INF/resources/ to org.richfaces library

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13210?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13210: --------------------------------- Note, it's not, we should move RichFaces Core JS resources such as richfaces.js to org.richfaces resource library and re-configure resource packaging. > Move RichFaces resources from META-INF/resources/ to org.richfaces library > -------------------------------------------------------------------------- > > Key: RF-13210 > URL: https://issues.jboss.org/browse/RF-13210 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.3.4, 5.0.0.Alpha1 > 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13331) Move tests for Chart component from Sandbox to Framework Tests

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13331?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13331: --------------------------------- Lukas, please use / introduce the category FailingOnFirefox alongside the Failing category. We also need to introduce it into richfaces5/pom.xml to integration-tests profile so that tests will be driven by that. Let's open an RFPL (QA component) issue to adress test compatiblity. > Move tests for Chart component from Sandbox to Framework Tests > -------------------------------------------------------------- > > Key: RF-13331 > URL: https://issues.jboss.org/browse/RF-13331 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Assignee: Lukáš Macko > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-13343: ---------------------------------- [~ppitonak] : Afaik and Mr. grep as well think that the only usage is to setup hotkey selector in one test. I have switched it to manual setting in this commit: https://github.com/richfaces/richfaces-qa/commit/06183063b37bc7b71388b810... > Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access > --------------------------------------------------------------------------------------------- > > Key: RF-13343 > URL: https://issues.jboss.org/browse/RF-13343 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: page-fragments, qe > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > > As we have discussed in RF-13335, we have two options available for accessing component options: > * component uses {{BaseComponent}} (RF4 components) > {code} > RichFaces.component("j_idt108").options > {code} > * component uses {{jQuery UI Widget Factory}} (RF5 components) > {code} > $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus") > {code} > We can use WebDriver's {{JavascriptExecutor}} to access widget settings. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13348) pickList - columnClass attribute behaves differently than in RF4

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-13348: ---------------------------------- Created https://community.jboss.org/message/845869#845869 > pickList - columnClass attribute behaves differently than in RF4 > ---------------------------------------------------------------- > > Key: RF-13348 > URL: https://issues.jboss.org/browse/RF-13348 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > > {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*: > Suppose a {{pickList}}, which items consist from _three_ columns. > * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}} > * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected > In *RF4*, it was different though: > * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc: > bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored. > The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ? -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13172) rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values

by Pavel Slegr (JIRA)

[ https://issues.jboss.org/browse/RF-13172?page=com.atlassian.jira.plugin.s... ] Pavel Slegr commented on RF-13172: ---------------------------------- Brian, your suggestion was basically correct, additionally there is also getCountSeparators method, where the same thing (using rendered child's only) had to be fixed pull request sent ... against RF4/components repo > rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values > ------------------------------------------------------------------------------------------------------------ > > Key: RF-13172 > URL: https://issues.jboss.org/browse/RF-13172 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.3 > Reporter: Sergey Zubarev > Assignee: Pavel Slegr > Labels: low_hanging_fruit > Fix For: 5-Tracking > > > {code} > <rich:toolbar itemSeparator="line" id="repairWorkToolbar"> > <rich:toolbarGroup> > <a4j:commandLink value="btn1"/> > <a4j:commandLink value="btn2"/> > <a4j:commandLink value="btn3" *rendered="false"*/> > </rich:toolbarGroup> > <rich:toolbarGroup location="right"> > <a4j:commandLink value="btn_right"/> > </rich:toolbarGroup> > ... > {code} > In this case location="right" doesn't work : it displayed left. When I remove rendered="false" from btn3 all works fine. > Html debug shows, that code produced one extra element in colgroup tag when using rendered="false". -- 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, 4 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 November 2013