February 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-12768. ----------------------------- Labels: (was: richfaces4) Resolution: Out of Date > Metamer: rich:tabPanel: Tabs are not clickable and can't be removed > ------------------------------------------------------------------- > > Key: RF-12768 > URL: https://issues.jboss.org/browse/RF-12768 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.3.Final > Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1 > Reporter: Petr Mensik > Assignee: Lukáš Fryč > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed. -- 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-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12768: ---------------------------- Fix Version/s: (was: 4.3.1) > Metamer: rich:tabPanel: Tabs are not clickable and can't be removed > ------------------------------------------------------------------- > > Key: RF-12768 > URL: https://issues.jboss.org/browse/RF-12768 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.3.Final > Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1 > Reporter: Petr Mensik > Assignee: Lukáš Fryč > Labels: richfaces4 > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed. -- 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-12759) rich:hotkey doesn't handle Ctrl+A key binding

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12759?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12759: --------------------------------- What browser have you used? > rich:hotkey doesn't handle Ctrl+A key binding > --------------------------------------------- > > Key: RF-12759 > URL: https://issues.jboss.org/browse/RF-12759 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.3.Final > Environment: Linux Fedora 16 x64, NetBeans 7.2, GlassFish 3.1.1, CDI/Weld/CODI, JSF2, RichFaces4.2.3, Hibernate3.2.5, Firebird 2.5.1 > Reporter: Edilmar Alves > Assignee: Lukáš Fryč > Labels: hotkey, waiting_on_user > Attachments: test.java, test.xhtml > > > When I try to use rich:hotkey with a4j:commandButton, it doesn't work. A detailed explanation about this is in the forum. -- 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-12759) rich:hotkey doesn't handle Ctrl+A key binding

by Edilmar Alves (JIRA)

[ https://issues.jboss.org/browse/RF-12759?page=com.atlassian.jira.plugin.s... ] Edilmar Alves commented on RF-12759: ------------------------------------ I think isn't just CTRL+A problem. I inverted CTRL+A and CTRL+B in the two sample codes, CTRL+A worked fine with show operation and CTRL+B didn't work with click operation: <rich:hotKey key="ctrl+b" preventDefault="true" enabledInInput="true"> <rich:componentControl target="buttonPanel" operation="click"/> </rich:hotKey> <rich:hotKey key="ctrl+a" preventDefault="true"> <rich:componentControl target="openPanel" operation="show" /> </rich:hotKey> > rich:hotkey doesn't handle Ctrl+A key binding > --------------------------------------------- > > Key: RF-12759 > URL: https://issues.jboss.org/browse/RF-12759 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.3.Final > Environment: Linux Fedora 16 x64, NetBeans 7.2, GlassFish 3.1.1, CDI/Weld/CODI, JSF2, RichFaces4.2.3, Hibernate3.2.5, Firebird 2.5.1 > Reporter: Edilmar Alves > Assignee: Lukáš Fryč > Labels: hotkey, waiting_on_user > Attachments: test.java, test.xhtml > > > When I try to use rich:hotkey with a4j:commandButton, it doesn't work. A detailed explanation about this is in the forum. -- 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č edited comment on RF-12789 at 2/18/13 10:29 AM: ----------------------------------------------------------- Hey Lutz, could you please attach XHTML and Java code demonstrating the usage? I wouldn't like to misinterpret the issue report. --- Note that in some browsers the <script> tag is not replaced, the code is executed directly instead (see jsf.js). Using JavaScript service for generating tabs defers execution of the Tab-initialization script at the point where the DOM is updated and thus it is available for processing. was (Author: lfryc): Hey Lutz, could you please attach XHTML and Java code demonstrating the usage? I would like to misinterpret the issue report. --- Note that in some browsers the <script> tag is not replaced, the code is executed directly instead (see jsf.js). Using JavaScript service for generating tabs defers execution of the Tab-initialization script at the point where the DOM is updated and thus it is available for processing. > 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, 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č commented on RF-12789: --------------------------------- Lutz, can you see any JavaScript errors? Which browser are you using? Did this solution work for you before? (in RF 4.2.x) > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RF-12801) org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere

by asdf sdf (JIRA)

[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ] asdf sdf commented on RF-12801: ------------------------------- Hi all, we are also experiencing the same issue, RichFaces 4.3.0 Final on Websphere 8.0.0.3, no workaround except disabling it so far. Does anybody have a solution? > org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere > ------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12801 > URL: https://issues.jboss.org/browse/RF-12801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.3.0.Final > Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final > Reporter: Erdem YILMAZ > Labels: ELResolver, optimization, resource, websphere > > when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere. > resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour. > we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it. -- 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-12801) org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere

by Erdem YILMAZ (JIRA)

Erdem YILMAZ created RF-12801: --------------------------------- Summary: org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere Key: RF-12801 URL: https://issues.jboss.org/browse/RF-12801 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: resource handling Affects Versions: 4.3.0.Final Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final Reporter: Erdem YILMAZ when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere. resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour. we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it. -- 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 Lutz Ulrich (JIRA)

[ https://issues.jboss.org/browse/RF-12789?page=com.atlassian.jira.plugin.s... ] Lutz Ulrich edited comment on RF-12789 at 2/18/13 9:56 AM: ----------------------------------------------------------- Here you are: dynamicTab.xhtml contains an initial static rich:tabPanel with an initial rich:tab. Via the binding attribute, the tabPanel UIComponent is bound to my dynamicTabBean's 'staticTabPanel' property. dynamicTabBean is an instance of my Java class test.DynamicTabBean. The commandButton 'Add tab' invokes DynamicTabBean.addTab(). This adds a UITab to the staticTabPanel. The staticTabPanel is re-rendered due to <f:ajax render="staticTabPanel">. The new tab shows up. But the <script> element at the end of <body>, which is supposed to contain RichFaces script code for all tabPanels and tabs is NOT re-rendered. Thus, one cannot switch from the initial static tab to the dynamically added new tab. The commandButton 'Add tabPanel' invokes DynamicTabBean.addTabPanel(). A new tabPanel with 2 tabs is added to the staticTabPanel's parent UIComponent (the HtmlForm). The new tabPanel shows up. But one cannot switch its tabs due to similar problems as with the new single tab above. was (Author: lutzulrich): Here you are: dynamicTab.xhtml contains an initial static rich:tabPanel with an initial rich:tab. Via the binding attribute, the tabPanel UIComponent is bound to my dynamicTabBean's 'staticTabPanel' property. dynamicTabBean is an instance of my Java class test.DynamicTabBean. The commandButton 'Add tab' invokes DynamicTabBean.addTab(). This adds a UITab to the staticTabPanel. The staticTabPanel is re-rendered due to <f:ajax render="staticTabPanel">. The new tab shows up. But the <script> element at the end of <body>, which is supposed to contain RichFaces script code for all tabPanels and tabs is NOT re-rendered. Thus, one cannot switch from the initial static tab to the dynamically added new tab. The commandButton 'Add tabPanel' invokes DynamicTabBean.addTabPanel(). A new tabPanel with 2 tabs is added. The new tabPanel shows up. But one cannot switch its tabs due to similar problems as with the new single tab above. > 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, 7 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 updated RF-12789: ----------------------------- Attachment: dynamicTab.xhtml DynamicTabBean.java > 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, 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