April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12875) AbstractTogglePanel.visitTree() visits all children even with VisitHint.SKIP_UNRENDERED and switchType=ajax

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12875?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12875: ------------------------------- Fix Version/s: 5-Tracking > AbstractTogglePanel.visitTree() visits all children even with VisitHint.SKIP_UNRENDERED and switchType=ajax > ----------------------------------------------------------------------------------------------------------- > > Key: RF-12875 > URL: https://issues.jboss.org/browse/RF-12875 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.0.0.Final > Reporter: Mateusz Stefek > Fix For: 5-Tracking > > > Implementation of visitTree() for tab panels could be improved to check for VisitHint.SKIP_UNRENDERED and switchType != client. In such case the method should only iterate over facets and one active child. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (RF-12875) AbstractTogglePanel.visitTree() visits all children even with VisitHint.SKIP_UNRENDERED and switchType=ajax

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12875?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12875: ------------------------------------ [~mstefek] how would you feel about implementing such an improvement? We'd love to see a pull request implementing a check as you described. https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA > AbstractTogglePanel.visitTree() visits all children even with VisitHint.SKIP_UNRENDERED and switchType=ajax > ----------------------------------------------------------------------------------------------------------- > > Key: RF-12875 > URL: https://issues.jboss.org/browse/RF-12875 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.0.0.Final > Reporter: Mateusz Stefek > > Implementation of visitTree() for tab panels could be improved to check for VisitHint.SKIP_UNRENDERED and switchType != client. In such case the method should only iterate over facets and one active child. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (RF-12865) A4j:commandButton fail to render/update other components with MyFaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12865?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12865: ------------------------------- Labels: waiting_on_user (was: ) > A4j:commandButton fail to render/update other components with MyFaces > --------------------------------------------------------------------- > > 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 > Labels: waiting_on_user > > 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

13 years

1
0
0 / 0

[JBoss JIRA] (RF-12865) A4j:commandButton fail to render/update other components with MyFaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12865?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12865: ------------------------------------ [~blamlam] Is there any indication of what's going on in the server logs, or the browser error console? That may help us pinpoint with which library (RichFaces, OmniFaces, or Mojarra) the problem actually lies. > A4j:commandButton fail to render/update other components with MyFaces > --------------------------------------------------------------------- > > 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 > > 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

13 years

1
0
0 / 0

[JBoss JIRA] (RF-12865) A4j:commandButton fail to render/update other components with MyFaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12865?page=com.atlassian.jira.plugin.s... ] Brian Leathem edited comment on RF-12865 at 4/6/13 2:50 AM: ------------------------------------------------------------ [~blamlam] Is there any indication of what's going on in the server logs, or the browser error console? That may help us pinpoint with which library (RichFaces, OmniFaces, or MyFaces) the problem actually lies. was (Author: bleathem): [~blamlam] Is there any indication of what's going on in the server logs, or the browser error console? That may help us pinpoint with which library (RichFaces, OmniFaces, or Mojarra) the problem actually lies. > A4j:commandButton fail to render/update other components with MyFaces > --------------------------------------------------------------------- > > 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 > > 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

13 years

1
0
0 / 0

[JBoss JIRA] (RF-12857) Fundamental tests are not run - separate them on the level of JUnit categories

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12857?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12857: ------------------------------------ I thought we did this already? > Fundamental tests are not run - separate them on the level of JUnit categories > ------------------------------------------------------------------------------ > > Key: RF-12857 > URL: https://issues.jboss.org/browse/RF-12857 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Priority: Critical > > After refactoring of Java packages the fundamental tests are not in integration-test-specific packages anymore, which does not allow to filter them effectively: https://github.com/richfaces/richfaces5/blob/659dde9ba1f4e0d9ba912ff3a84d... > That's why most of the fundamental tests are not run anymore. > ---- > I suggest to leave this concept and use JUnit Categories instead: > * categorized tests can be either Smoke, Integration, Failing, etc. > * un-categorized tests are considered to be unit tests and they are run as part of test run > ---- > There is proof of concept how JUnit Categories works and how can be used by RichFaces framework modules: > https://github.com/lfryc/surefire-and-junit-categories > I suggest to move tests in {{src/test/integration}} to {{src/test/java}}. > This will imply two things: > * {{integration-tests}} profile will no longer manage project's dependencies > * there will be cross-module shared interfaces for categories, e.g.: [Smoke|https://github.com/lfryc/surefire-and-junit-categories/blob/master/...] -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (RF-12846) a4j:commandLink accesskey attribute missing

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12846?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12846: ------------------------------- Fix Version/s: 4.3.2 5-Tracking > a4j:commandLink accesskey attribute missing > ------------------------------------------- > > Key: RF-12846 > URL: https://issues.jboss.org/browse/RF-12846 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.1 > Reporter: John Yeary > Priority: Trivial > Fix For: 4.3.2, 5-Tracking > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The a4j:commandLink supported accesskey in 3.3.3.final and the org.richfaces.renderkit.html.CommandLinkRenderer supports the accesskey attribute as a pass-through attribute. However it does not appear in the VDL documentation, and produces an error message in the IDE. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (RF-12845) rich:menuItem does not work as composite component

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12845?page=com.atlassian.jira.plugin.s... ] Brian Leathem edited comment on RF-12845 at 4/6/13 1:16 AM: ------------------------------------------------------------ [~michaelb80] indeed you are correct, the DropDownMenuRenderer only renders children that are of one of the following types: {code} child instanceof AbstractMenuGroup || child instanceof AbstractMenuItem || child instanceof AbstractMenuSeparator {code} See: https://github.com/richfaces/components/blob/master/output/ui/src/main/ja... You could try setting your the componsite component _componentType_ to 'org.richfaces.<package>.UIMenuItem'. Then you won't have to implement a java sclass yourself. was (Author: bleathem): [~michaelb80] indeed you are correct, the DropDownMenuRenderer only renders children that are of one of the following types: {code} child instanceof AbstractMenuGroup || child instanceof AbstractMenuItem || child instanceof AbstractMenuSeparator {code} See: https://github.com/richfaces/components/blob/master/output/ui/src/main/ja... You could try setting your the componsite component _componentType_ to '<org.richfaces.<package>.UIMenuItem'. Then you won't have to implement a java sclass yourself. > rich:menuItem does not work as composite component > -------------------------------------------------- > > Key: RF-12845 > URL: https://issues.jboss.org/browse/RF-12845 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.1 > Environment: Win7 x64, Java 6 x64, Tomcat 7.0.30 x64, RF 4.3.1, IE8 + FF19.0.2 > Reporter: Michael B > Priority: Minor > Labels: richfaces, waiting_on_user > > When creating a composite component that contains a rich:menuItem, the menu item is not showing. => Client side error while identifying the menu items parent via css-selector. > {code:xml|title:menuItem.xhtml} > <?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:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:composite="http://java.sun.com/jsf/composite"> > > <composite:interface> > <composite:attribute name="icon" type="java.lang.String" required="false" /> > <composite:attribute name="label" type="java.lang.String" required="true" /> > <composite:attribute name="menuItem" type="java.lang.String" required="true" /> > <composite:attribute name="menuKey" type="java.lang.String" required="true" /> > <composite:attribute name="value" type="java.lang.String" required="true" /> > </composite:interface> > > <composite:implementation> > <rich:menuItem label="#{cc.attrs.label}" icon="#{cc.attrs.icon}" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( cc.attrs.menuKey, cc.attrs.menuItem )}"> > <f:param name="selectedItem" value="#{cc.attrs.value}" /> > </rich:menuItem> > </composite:implementation> > > </html> > {code} > Including the resulting composite component in a rich:dropDownMenu like > {code:xml} > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > xmlns:xxx="http://java.sun.com/jsf/composite/xxx"> > > <rich:toolbar> > <rich:dropDownMenu> > <f:facet name="label"> > <h:outputText value="Test" /> > </f:facet> > <xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" /> > </rich:dropDownMenu> > </rich:toolbar> > > </ui:composition> > {code} > ... reproduces the problem. Writing the rich:menuItem directly inside the rich:dropDownMenu works. Also wrapping the composite component with rich:menuGroup works. Only the direct child option fails. > See example for comparison - item 2 and 3 are working, while item 1 is not: > {code:xml} > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > xmlns:xxx="http://java.sun.com/jsf/composite/xxx"> > > <rich:toolbar> > <rich:dropDownMenu> > <f:facet name="label"> > <h:outputText value="Test" /> > </f:facet> > <xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" /> > <rich:menuItem label="Item 2" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( 'aaa', 'bbb' )}"> > <f:param name="selectedItem" value="item2" /> > </rich:menuItem> > <rich:menuGroup label="Group"> > <xxx:menuItem label="Item 3" value="item3" menuKey="aaa" menuItem="bbb" /> > </rich:menuGroup> > </rich:dropDownMenu> > </rich:toolbar> > > </ui:composition> > {code} > On a side not: just found out, that the problem might come from the rich:dropDownMenu only allowing for direct children of type rich:menuGroup or rich:menuItem, while a composite component always adds another UIPanel to wrap itself. So if I understand the concept correctly, one would have to write a custom component class that is a menu item and also implements NamingContainer and add it as 'componentType' to the interface. Kinda beats the purpose of being able to easily create an extended markup for components that are expected as direct children though. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (RF-12891) Datatable with ExtendedDataModel ajax call

by tehackio teha (JIRA)

tehackio teha created RF-12891: ---------------------------------- Summary: Datatable with ExtendedDataModel ajax call Key: RF-12891 URL: https://issues.jboss.org/browse/RF-12891 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.3.1 Environment: apache-tomcat-7.0.34, servlet-weld 1.1.11. Reporter: tehackio teha Priority: Critical If one ajax call inside column of datatable(org.ajax4jsf.model.ExtendedDataModel) to render outside, method walk is called many times; On org.richfaces.component.UIDataAdaptor.requiresRowIteration(VisitContext context), context.getFacesContext().getAttributes().get("javax.faces.visit.SKIP_ITERATION") returns "null", therefore "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

13 years

1
0
0 / 0

[JBoss JIRA] (RF-12845) rich:menuItem does not work as composite component

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12845?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12845: ------------------------------- Labels: richfaces waiting_on_user (was: richfaces) > rich:menuItem does not work as composite component > -------------------------------------------------- > > Key: RF-12845 > URL: https://issues.jboss.org/browse/RF-12845 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.1 > Environment: Win7 x64, Java 6 x64, Tomcat 7.0.30 x64, RF 4.3.1, IE8 + FF19.0.2 > Reporter: Michael B > Priority: Minor > Labels: richfaces, waiting_on_user > > When creating a composite component that contains a rich:menuItem, the menu item is not showing. => Client side error while identifying the menu items parent via css-selector. > {code:xml|title:menuItem.xhtml} > <?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:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:rich="http://richfaces.org/rich" > xmlns:composite="http://java.sun.com/jsf/composite"> > > <composite:interface> > <composite:attribute name="icon" type="java.lang.String" required="false" /> > <composite:attribute name="label" type="java.lang.String" required="true" /> > <composite:attribute name="menuItem" type="java.lang.String" required="true" /> > <composite:attribute name="menuKey" type="java.lang.String" required="true" /> > <composite:attribute name="value" type="java.lang.String" required="true" /> > </composite:interface> > > <composite:implementation> > <rich:menuItem label="#{cc.attrs.label}" icon="#{cc.attrs.icon}" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( cc.attrs.menuKey, cc.attrs.menuItem )}"> > <f:param name="selectedItem" value="#{cc.attrs.value}" /> > </rich:menuItem> > </composite:implementation> > > </html> > {code} > Including the resulting composite component in a rich:dropDownMenu like > {code:xml} > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > xmlns:xxx="http://java.sun.com/jsf/composite/xxx"> > > <rich:toolbar> > <rich:dropDownMenu> > <f:facet name="label"> > <h:outputText value="Test" /> > </f:facet> > <xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" /> > </rich:dropDownMenu> > </rich:toolbar> > > </ui:composition> > {code} > ... reproduces the problem. Writing the rich:menuItem directly inside the rich:dropDownMenu works. Also wrapping the composite component with rich:menuGroup works. Only the direct child option fails. > See example for comparison - item 2 and 3 are working, while item 1 is not: > {code:xml} > <ui:composition xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:rich="http://richfaces.org/rich" > xmlns:xxx="http://java.sun.com/jsf/composite/xxx"> > > <rich:toolbar> > <rich:dropDownMenu> > <f:facet name="label"> > <h:outputText value="Test" /> > </f:facet> > <xxx:menuItem label="Item 1" value="item1" menuKey="aaa" menuItem="bbb" /> > <rich:menuItem label="Item 2" action="#{menuController.menuItemClicked}" rendered="#{menuController.isMenuItemAccessible( 'aaa', 'bbb' )}"> > <f:param name="selectedItem" value="item2" /> > </rich:menuItem> > <rich:menuGroup label="Group"> > <xxx:menuItem label="Item 3" value="item3" menuKey="aaa" menuItem="bbb" /> > </rich:menuGroup> > </rich:dropDownMenu> > </rich:toolbar> > > </ui:composition> > {code} > On a side not: just found out, that the problem might come from the rich:dropDownMenu only allowing for direct children of type rich:menuGroup or rich:menuItem, while a composite component always adds another UIPanel to wrap itself. So if I understand the concept correctly, one would have to write a custom component class that is a menu item and also implements NamingContainer and add it as 'componentType' to the interface. Kinda beats the purpose of being able to easily create an extended markup for components that are expected as direct children though. -- 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

13 years

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