February 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12809) Richfaces-related examples should use -with-richfaces BOM

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-12809: ---------------------------------------------- Marek Novotny <mnovotny(a)redhat.com> made a comment on [bug 915767|https://bugzilla.redhat.com/show_bug.cgi?id=915767] I am not sure that this applies to kitchensink-rf too, because there are -with-tools and -with-hibernate so replacement with -with-richfaces is useless. > Richfaces-related examples should use -with-richfaces BOM > --------------------------------------------------------- > > Key: RF-12809 > URL: https://issues.jboss.org/browse/RF-12809 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Tomas Repel > > There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation. In case of helloworld-rf it is sufficient the dependencyManagement section to contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed completely. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12765: --------------------------------- Hey [~talik], I still can't reproduce it on Tomcat 6 even with Brian's test. I guess there must be something different in your setup. I can prepare a test to be executed by you as simply as possible - could you verify then with your installation? > Rich:tabPanel not possible to switch tabs when only dynamic tabs are present > ---------------------------------------------------------------------------- > > Key: RF-12765 > URL: https://issues.jboss.org/browse/RF-12765 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.0.M3, 4.3.0.CR2 > Environment: Linux, windows any browser Chrom, Mozilla > Reporter: Tali Han > Assignee: Lukáš Fryč > Fix For: 4.3.1 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Rih:Tab panel functionality is broken. > If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again. > Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour. > richfaces/tabPanel/samples/dynamic-sample.xhtml > {code} > <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}"> > <ui:remove> > <rich:tab header="Static"> > <p>This tab is static one.</p> > > <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p> > </rich:tab> > </ui:remove> > <a4j:repeat value="#{skinBean.skins}" var="skinName"> > > <rich:tab header="#{skinName}" name="#{skinName}"> > <f:facet name="header">#{skinName}</f:facet> > <i> All the controls below are just standard JSF components skinned with RichFaces: </i> > <hr /> > <h:form> > {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, 6 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č resolved RF-12789. ----------------------------- Fix Version/s: (was: 4.3.1) Resolution: Duplicate Issue This issue was resolved with fix of RF-12803. > 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 > Assignee: Lukáš Fryč > Labels: Tab, TabPanel, dynamical-add > Attachments: dynamicTab.xhtml, DynamicTabBean.java > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-11574) Showcase: rich:autocomplete with custom popup layout -> filtering doesn't work

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-11574?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-11574. ----------------------------- Labels: (was: portletbridge) Assignee: Lukáš Fryč (was: Jan Papousek) Fix Version/s: (was: 4.3.1) (was: 5-Tracking) Resolution: Duplicate Issue > Showcase: rich:autocomplete with custom popup layout -> filtering doesn't work > ------------------------------------------------------------------------------ > > Key: RF-11574 > URL: https://issues.jboss.org/browse/RF-11574 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 4.1.0.Milestone3 > Environment: Firefox 6.0 > Google Chrome 12.0.742.112 > Reporter: Jan Papousek > Assignee: Lukáš Fryč > > The Showcase demo containing custom layout for autocomplete popups doesn't work properly. When something is typed into the input field, popup is displated, but the items are not filtered. -- 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, 6 months

1
0
0 / 0

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

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12769?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak closed RF-12769. ------------------------------ > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12774) a4j:commandLink does not set the styleClass when disabled

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12774?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak closed RF-12774. ------------------------------ Can be reproduced in Metamer # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jCommandLink/simple.xhtml # set disabled=true Works fine in 4.3.1-SNAPSHOT > a4j:commandLink does not set the styleClass when disabled > --------------------------------------------------------- > > Key: RF-12774 > URL: https://issues.jboss.org/browse/RF-12774 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.Final > Reporter: Timothy Whitehead > Assignee: Lukáš Fryč > Labels: a4j:commandLink, regression, richfaces, styleClass > Fix For: 4.3.1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > I upgraded to 4.3.0.Final and when I use a disabled a4j:commandLink it renders with class="class org.richfaces.component.UICommandLink" I believe it was working correctly in 4.2.3.Final -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12809) Richfaces-related examples should use -with-richfaces BOM

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated RF-12809: ----------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=915767 > Richfaces-related examples should use -with-richfaces BOM > --------------------------------------------------------- > > Key: RF-12809 > URL: https://issues.jboss.org/browse/RF-12809 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Tomas Repel > > There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation. In case of helloworld-rf it is sufficient the dependencyManagement section to contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed completely. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12809) Richfaces-related examples should use -with-richfaces BOM

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.s... ] Pete Muir moved JDF-223 to RF-12809: ------------------------------------ Project: RichFaces (was: JBoss Developer Framework) Key: RF-12809 (was: JDF-223) Component/s: examples (was: quickstarts) Security: Public > Richfaces-related examples should use -with-richfaces BOM > --------------------------------------------------------- > > Key: RF-12809 > URL: https://issues.jboss.org/browse/RF-12809 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Tomas Repel > > There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation. In case of helloworld-rf it is sufficient the dependencyManagement section to contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed completely. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12809) Richfaces-related examples should use -with-richfaces BOM

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/RF-12809?page=com.atlassian.jira.plugin.s... ] Pete Muir commented on RF-12809: -------------------------------- I moved this to RichFaces, as they supply the quickstarts in JDF for RichFaces :-) > Richfaces-related examples should use -with-richfaces BOM > --------------------------------------------------------- > > Key: RF-12809 > URL: https://issues.jboss.org/browse/RF-12809 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Reporter: Tomas Repel > > There is jboss-javaee-6.0-with-richfaces BOM, I think this should be used instead of richfaces-bom in case that jboss-javaee-6.0 BOM is required as well. This holds for helloworld-rf, kitchensink-rf and richfaces-validation. In case of helloworld-rf it is sufficient the dependencyManagement section to contain only -with-richfaces BOM, the jboss-javaee-6.0 BOM can be removed completely. -- 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, 6 months

1
0
0 / 0

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

by Lutz Ulrich (JIRA)

[ https://issues.jboss.org/browse/RF-12789?page=com.atlassian.jira.plugin.s... ] Lutz Ulrich commented on RF-12789: ---------------------------------- The fix seems to work in my application. I checked dynamically adding Tabs and TabPanels as well as removing them in partial requests. Also, non-partial complete page refreshs of pages with dynamically added Tabs and TabPanels work. Thank you. > 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 > Assignee: Lukáš Fryč > Labels: Tab, TabPanel, dynamical-add > Fix For: 4.3.1 > > Attachments: dynamicTab.xhtml, DynamicTabBean.java > > 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, 6 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