February 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12682: ------------------------------- Labels: extendedDataTable render richfaces tabpanel waiting_on_user (was: extendedDataTable render richfaces tabpanel) > extendedDataTable render issue with rich:tabPanel > ------------------------------------------------- > > Key: RF-12682 > URL: https://issues.jboss.org/browse/RF-12682 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1 > Reporter: Kaveh A. > Labels: extendedDataTable, render, richfaces, tabpanel, waiting_on_user > Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip > > > This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time). > In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue. > https://community.jboss.org/message/783787 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12802: ------------------------------- Fix Version/s: 5.0.0.M2 > Move page fragments from repository qa to richfaces5 > ---------------------------------------------------- > > Key: RF-12802 > URL: https://issues.jboss.org/browse/RF-12802 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.M1 > Reporter: Pavol Pitonak > Fix For: 5.0.0.M2 > > > As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework. > We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12798) <a4j:push>: parameter to enable JMS integration

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12798?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12798: ------------------------------- Fix Version/s: 4.3.1 > <a4j:push>: parameter to enable JMS integration > ----------------------------------------------- > > Key: RF-12798 > URL: https://issues.jboss.org/browse/RF-12798 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.Final > Reporter: Roberto Contiero > Priority: Minor > Fix For: 4.3.1 > > > There is an error in the Component Reference documentation for the component <a4j:push>. The parameter to enable JMS isn't: > {code} > <context-param> > <param-name>org.richfaces.push.jms.enable</param-name> > <param-value>true</param-value> > </context-param> > {code} > but > {code} > <context-param> > <param-name>org.richfaces.push.jms.enabled</param-name> > <param-value>true</param-value> > </context-param> > {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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12798) <a4j:push>: parameter to enable JMS integration

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12798?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12798: ------------------------------- Workaround Description: Use this parameter to enable JMS: {code} <context-param> <param-name>org.richfaces.push.jms.enabled</param-name> <param-value>true</param-value> </context-param> {code} was: Use this parameter to enable JMS: <context-param> <param-name>org.richfaces.push.jms.enabled</param-name> <param-value>true</param-value> </context-param> > <a4j:push>: parameter to enable JMS integration > ----------------------------------------------- > > Key: RF-12798 > URL: https://issues.jboss.org/browse/RF-12798 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.Final > Reporter: Roberto Contiero > Priority: Minor > Fix For: 4.3.1 > > > There is an error in the Component Reference documentation for the component <a4j:push>. The parameter to enable JMS isn't: > {code} > <context-param> > <param-name>org.richfaces.push.jms.enable</param-name> > <param-value>true</param-value> > </context-param> > {code} > but > {code} > <context-param> > <param-name>org.richfaces.push.jms.enabled</param-name> > <param-value>true</param-value> > </context-param> > {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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12799) Log: add attribute hotkey

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12799?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12799: ------------------------------- Fix Version/s: 5-Tracking > Log: add attribute hotkey > ------------------------- > > Key: RF-12799 > URL: https://issues.jboss.org/browse/RF-12799 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.Final > Reporter: Pavol Pitonak > Fix For: 5-Tracking > > > a4j:log doesn't work in popup mode in Firefox with installed Firebug because they both use the same keyboard shortcuts (Ctrl+Shift+L). a4j:log in RichFaces 3.3.x had attribute "hotkey" which changed shortcut to Ctrl+Shift+<your_choice>. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12800) Simpleapp archetype: wrong enterprise version

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12800?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12800. -------------------------------- Resolution: Rejected that enterprise version is not yet available. We will do a new archetype release once WFK has been released. > Simpleapp archetype: wrong enterprise version > --------------------------------------------- > > Key: RF-12800 > URL: https://issues.jboss.org/browse/RF-12800 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Jan Papousek > > Thu current enterprise version defined in 4.3.0.Final is 4.2.3.Final-redhat-1 and should be 4.3.0.Final-redhat-1. See https://github.com/richfaces/archetypes/blob/ad801775d2fc89ea719ad4468371... -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12797) rich:editor not rendered when using RichFaces module

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12797?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12797: ------------------------------- Component/s: component-input > rich:editor not rendered when using RichFaces module > ---------------------------------------------------- > > Key: RF-12797 > URL: https://issues.jboss.org/browse/RF-12797 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk, component-input > Affects Versions: 4.3.0.Final > Environment: JBoss 7.1.1 > Reporter: Serge Mürset > Fix For: 5-Tracking > > Attachments: editor-test.zip > > > I want to configure my Webapp to use RichFaces as a JBoss module not a library. To achieve this, I create the module org.richfaces with version 4.3.0 in module directory of JBoss. > As soon as I switch from library to module, the rich:editor is not rendered anymore. In the Browser History i read > [15:07:25.511] GET http://localhost:8080/editor-test/org.richfaces.resources/javax.faces.res... [HTTP/1.1 404 Not Found 1ms] > I validated that the resource lang/de.js is available in classpath though. > 15:01:02,780 INFO [stdout] (MSC service thread 1-5) The following resource(s) are found at location /META-INF/resources/org.richfaces.ckeditor/lang/de.js > 15:01:02,781 INFO [stdout] (MSC service thread 1-5) --- jar:file:/opt/jboss-7.1.1/modules/org/richfaces/main/richfaces-components-ui-4.3.0.Final.jar!/META-INF/resources/org.richfaces.ckeditor/lang/de.js > Weird enough, all other components I checked still work. I followed the instructions of https://issues.jboss.org/browse/RF-12008. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12797) rich:editor not rendered when using RichFaces module

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12797?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12797: ------------------------------- Fix Version/s: 5-Tracking > rich:editor not rendered when using RichFaces module > ---------------------------------------------------- > > Key: RF-12797 > URL: https://issues.jboss.org/browse/RF-12797 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.3.0.Final > Environment: JBoss 7.1.1 > Reporter: Serge Mürset > Fix For: 5-Tracking > > Attachments: editor-test.zip > > > I want to configure my Webapp to use RichFaces as a JBoss module not a library. To achieve this, I create the module org.richfaces with version 4.3.0 in module directory of JBoss. > As soon as I switch from library to module, the rich:editor is not rendered anymore. In the Browser History i read > [15:07:25.511] GET http://localhost:8080/editor-test/org.richfaces.resources/javax.faces.res... [HTTP/1.1 404 Not Found 1ms] > I validated that the resource lang/de.js is available in classpath though. > 15:01:02,780 INFO [stdout] (MSC service thread 1-5) The following resource(s) are found at location /META-INF/resources/org.richfaces.ckeditor/lang/de.js > 15:01:02,781 INFO [stdout] (MSC service thread 1-5) --- jar:file:/opt/jboss-7.1.1/modules/org/richfaces/main/richfaces-components-ui-4.3.0.Final.jar!/META-INF/resources/org.richfaces.ckeditor/lang/de.js > Weird enough, all other components I checked still work. I followed the instructions of https://issues.jboss.org/browse/RF-12008. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12798) <a4j:push>: parameter to enable JMS integration

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12798?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12798: ------------------------------- Description: There is an error in the Component Reference documentation for the component <a4j:push>. The parameter to enable JMS isn't: {code} <context-param> <param-name>org.richfaces.push.jms.enable</param-name> <param-value>true</param-value> </context-param> {code} but {code} <context-param> <param-name>org.richfaces.push.jms.enabled</param-name> <param-value>true</param-value> </context-param> {code} was: There is an error in the Component Reference documentation for the component <a4j:push>. The parameter to enable JMS isn't: <context-param> <param-name>org.richfaces.push.jms.enable</param-name> <param-value>true</param-value> </context-param> but <context-param> <param-name>org.richfaces.push.jms.enabled</param-name> <param-value>true</param-value> </context-param> > <a4j:push>: parameter to enable JMS integration > ----------------------------------------------- > > Key: RF-12798 > URL: https://issues.jboss.org/browse/RF-12798 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.Final > Reporter: Roberto Contiero > Priority: Minor > > There is an error in the Component Reference documentation for the component <a4j:push>. The parameter to enable JMS isn't: > {code} > <context-param> > <param-name>org.richfaces.push.jms.enable</param-name> > <param-value>true</param-value> > </context-param> > {code} > but > {code} > <context-param> > <param-name>org.richfaces.push.jms.enabled</param-name> > <param-value>true</param-value> > </context-param> > {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, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12794) Using the same name for id and name for this tag triggers an error with IE

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12794?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12794: ------------------------------- Fix Version/s: 5-Tracking Workaround Description: Place the a4j:jsFunction inside the h:form. Workaround: Workaround Exists > Using the same name for id and name for this tag triggers an error with IE > -------------------------------------------------------------------------- > > Key: RF-12794 > URL: https://issues.jboss.org/browse/RF-12794 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.0.Final, 4.3.0.Final > Reporter: Jean ANDRE > Fix For: 5-Tracking > > > Using the same name for id and name for this tag triggers an error with IE. > We need to: > # Confirm that this is an issue > # Determine if this is an RF issue, an upstream JSF issue, or purely a IE issue > # Document this _somehwere_ -- 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, 10 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