September 2013 - richfaces-issues

[JBoss JIRA] (RF-11815) RichFaces version not displayed via EL expression #{a4j} on JBoss AS 7

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11815?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-11815: ------------------------------- Labels: (was: needs-qe) > RichFaces version not displayed via EL expression #{a4j} on JBoss AS 7 > ---------------------------------------------------------------------- > > Key: RF-11815 > URL: https://issues.jboss.org/browse/RF-11815 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core, showcase > Affects Versions: 4.1.0.Final > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.2.0.CR1 > > > The EL expression _#{a4j}_ is defined in _richfaces-core-impl_, and is used to display the RichFaces version on a page. > This is visible on the showcase as the line along the bottom: > {quote} > RichFaces Core Implementation by JBoss, a division of Red Hat, Inc., version v.4.0.1-SNAPSHOT SVN r.unknown > {quote} > This does not work on JBoss AS. It should be re-instated. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13170) Skin="plain' cause http 404 for skinning.css.

by Adrien Adrien (JIRA)

Adrien Adrien created RF-13170: ---------------------------------- Summary: Skin="plain' cause http 404 for skinning.css. Key: RF-13170 URL: https://issues.jboss.org/browse/RF-13170 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: regression Affects Versions: 4.3.3 Environment: Richfaces 4.3.3.Final jboss eap6.1 mojarra 2.1.25 Reporter: Adrien Adrien Set Skin to 'plain', then in firebug check resources donwloaded. =>http 404 skinning.css <context-param> <param-name>org.richfaces.skin</param-name> <param-value>#{prefs.skin}</param-value> </context-param> @SessionScoped public class PreferenceBean implements Serializable { private String skin="plain"; .... } -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-11759) Remove Cellpadding/Cellspacing from EDT, replace with appropriate CSS

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11759?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-11759: ------------------------------- Labels: (was: needs-qe) > Remove Cellpadding/Cellspacing from EDT, replace with appropriate CSS > --------------------------------------------------------------------- > > Key: RF-11759 > URL: https://issues.jboss.org/browse/RF-11759 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.1.0.CR1 > Reporter: Fisheye JIRA Integration > Assignee: Brian Leathem > Priority: Blocker > Fix For: 4.1.0.CR2 > > > Remove the cellpadding/cellspacing attributes introduced with RF-11738, as we want to focus on a CSS based approach to styling the tables. > The attributes were created to allow overriding the HTML cellpadding and cellspacing attributes set by the EDT, and allow developer override. These HTML attributes should be removed from the EDT, and the appropriate CSS styling changes made to compensate. > Created by Brian Leathem from Lukáš Fryč's Crucible comment on ExtendedDataTableRenderer.java line 289 https://source.jboss.org/cru/REV-RF-5#c172 : > {quote} > -Why does EDT need Cellpadding/spacing defined? > {quote} -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-11322) Metamer: rich:pickList: event handler attributes doesn't fire appropriate events

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11322?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-11322: ------------------------------- Labels: ci_issue (was: ci_issue needs-qe) > Metamer: rich:pickList: event handler attributes doesn't fire appropriate events > -------------------------------------------------------------------------------- > > Key: RF-11322 > URL: https://issues.jboss.org/browse/RF-11322 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.1.0.Milestone1 > Environment: RichFaces 4.1.0.20110805-M1 r.10246d45dddd1d2aa2034317d5a832394cc919f9 > Metamer 4.1.0.20110805-M1 r.22604 > Mojarra 2.1.3-FCS > Apache Tomcat 7.0.19 > Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux > Chrome 12.0.742.112 @ Linux i686 > Reporter: Ján Jamrich > Assignee: Brian Leathem > Priority: Critical > Labels: ci_issue > Fix For: 4.1.0.Milestone3 > > > Attributes for handling events such as onkeypress, onkeyup, onclick, onadditem, ontargetclick doesn't fire event, so nothing happens if bind some JS code to this attribute and try to trigger this event (such click, or add|remove item) -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-11552) Upgrade jQuery to latest version (1.6.4)

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11552?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-11552: ------------------------------- Labels: (was: needs-qe) > Upgrade jQuery to latest version (1.6.4) > ---------------------------------------- > > Key: RF-11552 > URL: https://issues.jboss.org/browse/RF-11552 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: third-party > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 4.1.0.Milestone4 > > > We should upgrade jQuery, so we ship with the latest possible version. > Since we already did a jQuery upgrade in M2, involving a minor version increment, this point release upgrade should be straightforward. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-11316) Improve the data model handling in select components

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11316?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-11316: ------------------------------- Labels: (was: needs-qe) > Improve the data model handling in select components > ---------------------------------------------------- > > Key: RF-11316 > URL: https://issues.jboss.org/browse/RF-11316 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.1.0.Milestone1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.1.0.Milestone2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The Pick and Ordering list store their clientSelectItem values in a value attribute of the <tr> or <span> element that lists them. > The Select and InPlaceSelect use the clientSelectItems passed through as a script option, but loop over the list for every loookup. > Consolidate and improve these approaches by using the clientSelectItems script option, but make use of the jQuery#data() method to store the values in the DOM elements during component initialization. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-11205) Add Ordering capabilities to the PickList Component

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11205?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-11205: ------------------------------- Labels: (was: needs-qe) > Add Ordering capabilities to the PickList Component > --------------------------------------------------- > > Key: RF-11205 > URL: https://issues.jboss.org/browse/RF-11205 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.0.0.Milestone1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.1.0.Milestone2 > > > The ListShuttle functionality from RichFaces 3 should be re-created by adding OrderingList capabilities to the target list of the target list of the PickList copmponent. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-11135) Push: make use of JMS configurable

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11135?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-11135: ------------------------------- Labels: (was: needs-qe) > Push: make use of JMS configurable > ---------------------------------- > > Key: RF-11135 > URL: https://issues.jboss.org/browse/RF-11135 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.1.0.Milestone1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.1.0.Milestone1 > > > Since JMS usage is pretty decoupled from Push messaging (it uses internal message queue now), it should be possible to turn it off completely. > *JMS should be enabled by default* because of backward compatibility, but could be turned off by following web.xml snippet: > {code:XML} > <context-param> > <param-name>org.richfaces.push.jms.disable</param-name> > <param-value>true</param-value> > </context-param> > {code} > This is one step closer to RF-11110. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-10882) Upgrade jQuery to latest version

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-10882?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-10882: ------------------------------- Labels: (was: needs-qe) > Upgrade jQuery to latest version > -------------------------------- > > Key: RF-10882 > URL: https://issues.jboss.org/browse/RF-10882 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: client-lib > Affects Versions: 4.0.0.Final > Reporter: George Gastaldi > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.1.0.Milestone2 > > > As for http://jquery.com/, the latest version available is 1.6.2. Consider upgrading jQuery to that version. -- 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

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13154) a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13154?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-13154: ------------------------------------ Atmosphere 1.0.17-SNAPSHOT seems to work fine. > a4j:push fails with CNFE for org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6 > -------------------------------------------------------------------------------------------- > > Key: RF-13154 > URL: https://issues.jboss.org/browse/RF-13154 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.3 > Environment: EAP 6.1.1.ER7 > Reporter: Ken Finnigan > Fix For: 4.3.4 > > > When accessing a4j:push example in showcase on EAP 6.1.1.ER7 the network tab of the developer console in Chrome shows failed network attempts for richfaces push and the following exception in the server logs: > {code} > 15:21:29,295 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[AutoRegisteredPushServlet]] (http-/127.0.0.1:8080-2) JBWEB000236: Servlet.service() for servlet AutoRegisteredPushServlet threw exception: java.lang.ClassNotFoundException: org.apache.coyote.http11.upgrade.UpgradeInbound from [Module "deployment.richfaces-showcase-4.3.3.Final-jbas71.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.2.Final-redhat-1] > at org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293) [atmosphere-runtime-1.0.10.jar:1.0.10] > at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279) [atmosphere-runtime-1.0.10.jar:1.0.10] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172) [rewrite-servlet-1.0.4.Final.jar:1.0.4.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} > Running the exact same showcase example war on EAP 6.1.0.GA works fine. -- 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

10 years, 8 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 September 2013