April 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12210) _Lang.byId - reference a reference node or an identifier must be passed

by Jean ANDRE (JIRA)

Jean ANDRE created RF-12210: ------------------------------- Summary: _Lang.byId - reference a reference node or an identifier must be passed Key: RF-12210 URL: https://issues.jboss.org/browse/RF-12210 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: FireFox 12 or 8.0.7601 - GlassFish 3.1.2 - Mojarra 2.1.7 - Windows 7 Reporter: Jean ANDRE We got the following javascript error message under firebug: _Lang.byId: reference un noeud de référence ou un identifiant doit être passé - jsf.js.jsf?ln=javax.faces (ligne 1). Under IE the error message is: Message : Erreur non spécifiée. Ligne : 1 Caractère : 37254 Code : 0 URI : http://localhost:8080/NestedWeb/javax.faces.resource/jsf.js.jsf?ln=javax.... At this code: ){throw this.makeException(new Error(),null,null,this._nameSpace,"byId",this.getMessage("ERR_REF_OR_ID",null,"_Lang.byId","reference")); This error did not appear in previous version of JSF - More over we have also new another error related to <rich:tab id="#{tab.id}" onenter="enterTab('#{tab.id}');" headerClass="tab-header"> The error occurs when we want to close a dynamic tab. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
23
0 / 0

[JBoss JIRA] (RF-11585) mediaOutput doesn't work in CDI @ConversationScoped

by Edilmar Alves (Created) (JIRA)

mediaOutput doesn't work in CDI @ConversationScoped --------------------------------------------------- Key: RF-11585 URL: https://issues.jboss.org/browse/RF-11585 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.0.0.Final Environment: NetBeans7.0.1 + GlassFish 3.1.1 + CDI 1.1 + JSF2.1 + RichFaces4.0.0-Final. Reporter: Edilmar Alves Priority: Critical When using a controller with @ConversationScoped (CDI scope), the following exception arises: GRAVE: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.ConversationScoped -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

5
7
0 / 0

[JBoss JIRA] Created: (RF-4308) rich:pickList: keep sort order of source list after add/remove operations

by Martin Höller (JIRA)

rich:pickList: keep sort order of source list after add/remove operations ------------------------------------------------------------------------- Key: RF-4308 URL: https://jira.jboss.org/jira/browse/RF-4308 Project: RichFaces Issue Type: Feature Request Reporter: Martin Höller When adding items from the source list to the target list and removing this items again, the original order of the source list is not preserved. This makes it hard to find items in a list that is longer than just a fest items. A good example is the second example on the livedemo at http://livedemo.exadel.com/richfaces-demo/richfaces/pickList.jsf. Add the first state (Alabama) and remove it. It can now be found at the very end of the otherwise alphabetical list of states. This can be rather unintuitive for a user. My suggestion is either remember the original sort order of the source list, or add some attribute that enables automatic sorting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
3
0 / 0

[JBoss JIRA] Created: (RF-11175) [rich:extendedDataTable] columns should be automatically resized to fill empty space on right side

by Rene O (JIRA)

[rich:extendedDataTable] columns should be automatically resized to fill empty space on right side -------------------------------------------------------------------------------------------------- Key: RF-11175 URL: https://issues.jboss.org/browse/RF-11175 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Final Reporter: Rene O Attachments: table.PNG As an example: If you have an extendedDataTable with a width of 500px and 3 columns with the default width set. The columns do not fill the entire table width. There is empty space left on the right side of the tabel. It would be good, if the columns would automatically resize to fit the entire table. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
4
0 / 0

[JBoss JIRA] (RF-12049) Richfaces Kitchensink Archetype

by Burr Sutter (JIRA)

Burr Sutter created RF-12049: -------------------------------- Summary: Richfaces Kitchensink Archetype Key: RF-12049 URL: https://issues.jboss.org/browse/RF-12049 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBDS 5 Beta 1 Reporter: Burr Sutter The currently generated RichFaces-based kitchensink project "richfaces-webapp" throws the following exception when Run As JUnit Test is used. 21:36:27,147 ERROR [org.jboss.ejb3.invocation] (http-localhost-127.0.0.1-8080-7) JBAS014134: EJB Invocation failed on component MemberRegistration for method public void org.jboss.tools.examples.controller.MemberRegistration.register() throws java.lang.Exception: javax.ejb.EJBException: org.jboss.weld.exceptions.IllegalProductException: WELD-000052 Cannot return null from a non-dependent producer method: [method] @Produces @RequestScoped public org.jboss.tools.examples.util.Resources.produceFacesContext() at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
18
0 / 0

[JBoss JIRA] (RF-11976) Showcase: BaseDescriptor is using com.sun.faces.ELUtils

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-11976: ------------------------------- Summary: Showcase: BaseDescriptor is using com.sun.faces.ELUtils Key: RF-11976 URL: https://issues.jboss.org/browse/RF-11976 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.2.0.CR1 Reporter: Lukáš Fryč Priority: Minor ELUtils are not on the classpath, when using MyFaces. {{com.sun.faces.el.ELUtils}} should be replaced with {{org.richfaces.el.util.ELUtils}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
7
0 / 0

[JBoss JIRA] (RF-11950) rich:findComponent does not retrieve the component

by Jean ANDRE (JIRA)

Jean ANDRE created RF-11950: ------------------------------- Summary: rich:findComponent does not retrieve the component Key: RF-11950 URL: https://issues.jboss.org/browse/RF-11950 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: base functionality Affects Versions: 4.1.0.Final Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Firefox 10.0 - Windows 7 (6.1 sp1) Reporter: Jean ANDRE The rich:findComponent does not retrieve the component - What we want to achieve is to send .click() event on a command button. We got different errors depending the tests we made such as syntax error. The involved code: ------------------    <a4j:commandButton id="#{tab.id}-rcd-cancelCreateCmd" value="#{msg['common.command.cancel']}" onclick="#{rich:findComponent('#{activity.id}-closeCmd')}.click();;return false;" render="#{tab.id}-tabsClient" immediate="true" /> The error we got: ---------------- syntax error - [Stopper sur une erreur] - jsf.js.jsf?ln=javax.faces (ligne 1) .click();return false; The corresponding view source: ------------------------------ <input type="submit" value="Cancel" onclick="jsf.util.chain(this,event,".click();return false;","RichFaces.ajax(\"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )");return false;" name="tabbedForm:TAB_CLIENT-1-rcd-cancelCreateCmd" id="tabbedForm:TAB_CLIENT-1-rcd-cancelCreateCmd"> The generated javaScript under firebug: -------------------------------------- function onclick(event) { jsf.util.chain(this, event, ".click();return false;", "RichFaces.ajax(\"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); return false; } If we hard code the Id instead of the calculated one we got following error: uncaught exception: Syntax error, unrecognized expression: TAB_CLIENT-1-TAB_RCD-closeCmd Line 0 The generated javaScript under firebug: -------------------------------------- function anonymous(event) { rich: findComponent("TAB_CLIENT-1-TAB_RCD-closeCmd").click(); return false; } If we use directly jQuery:    <a4j:commandButton id="#{tab.id}-rcd-cancelCreateCmd" value="#{msg['common.command.cancel']}" onclick="$('##{activity.id}-closeCmd').click();return false;" render="desktopTabPanel" immediate="true" /> missing ; before statement http://localhost:12000/crm/javax.faces.resource/jsf.js.jsf?ln=javax.faces Line 1 If we hardcode an existing static Id, we got the error as shown the screen capture: function onclick(event) { jsf.util.chain(this, event, "org.richfaces.component.UICommandButton(a)39de2ca.click();", "RichFaces.ajax(\"tabbedForm:TAB_CLIENT\\u002D1\\u002Drcd\\u002DcancelCreateCmd\",event,{\"incId\":\"1\"} )"); return false; } <a4j:commandButton id="#{tab.id}-rcd-cancelCreateCmd" value="#{msg['common.command.cancel']}" onclick="#{rich:findComponent('qsearchClient')}.click();" render="#{tab.id}-tabsClient" immediate="true" />  -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

5
19
0 / 0

[JBoss JIRA] (RF-12176) Upgrade to Atmosphere 0.9.x

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12176: ------------------------------- Summary: Upgrade to Atmosphere 0.9.x Key: RF-12176 URL: https://issues.jboss.org/browse/RF-12176 Project: RichFaces Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.2.1.Final Reporter: Lukáš Fryč We need to check first how fluent the upgrade is, but as you can see from this discussion [1], the release contains fixes for RF-11940 (which has been worked around locally) [1] https://groups.google.com/forum/?fromgroups#!topic/atmosphere-framework/h... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
14
0 / 0

[JBoss JIRA] Created: (RF-11417) Tab: investigate why @action does not work

by Lukáš Fryč (JIRA)

Tab: investigate why @action does not work ------------------------------------------ Key: RF-11417 URL: https://issues.jboss.org/browse/RF-11417 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-panels-layout-themes Affects Versions: 4.1.0.Final Reporter: Lukáš Fryč Fix For: 4.1.0.Tracking Determine why rich:tab @action has not been implemented. Verify that its implementation can't affect current applications (and try to find possible workaround). Implement @action and @actionListener. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
5
0 / 0

[JBoss JIRA] (RF-12022) showcase - UAgentInfo is not serialized

by Juraj Huska (JIRA)

Juraj Huska created RF-12022: -------------------------------- Summary: showcase - UAgentInfo is not serialized Key: RF-12022 URL: https://issues.jboss.org/browse/RF-12022 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.2.0.Final Environment: -showcase, -Tomcat 6,7, -arquillian tests Reporter: Juraj Huska Priority: Trivial When running functional tests for showcase with Arquillian on Tomcat 6 or 7, I am encountering following exception during showcase undeploying process: {code} WARNING: Cannot serialize session attribute userAgent for session E4F43AA62674D093726971AC8361F9F8 java.io.NotSerializableException: org.richfaces.demo.ui.UAgentInfo at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) at org.apache.catalina.session.StandardSession.writeObject(StandardSession.java:1585) at org.apache.catalina.session.StandardSession.writeObjectData(StandardSession.java:1015) at org.apache.catalina.session.StandardManager.doUnload(StandardManager.java:528) at org.apache.catalina.session.StandardManager.unload(StandardManager.java:469) at org.apache.catalina.session.StandardManager.stop(StandardManager.java:678) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4882) at org.apache.catalina.manager.ManagerServlet.undeploy(ManagerServlet.java:1390) at org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:382) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:563) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:662) {code} UAgentInfo is used by UserAgentProcessor(session scoped bean) and therefore IMHO should be serialized. When I made it serialize-able, the exception disappeared. I did not notice any broken functionality by this exception, and same for the fixed one showcase, only cleaner test output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2012