September 2013 - richfaces-issues

[JBoss JIRA] (RF-13159) Add Maven compiler properties and remove Maven plugin from the the quickstart POM files

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13159?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13159: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Add Maven compiler properties and remove Maven plugin from the the quickstart POM files > --------------------------------------------------------------------------------------- > > Key: RF-13159 > URL: https://issues.jboss.org/browse/RF-13159 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: examples > Reporter: Sande Gilda > Fix For: 4.3.4 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > 1. Make sure the following properties are defined in each quickstart POM file: > {code} > <maven.compiler.target>1.6</maven.compiler.target> > <maven.compiler.source>1.6</maven.compiler.source> > {code} > 2. Remove the Maven plugin from each quickstart POM file: > {code} > -  > - <plugin> > - <artifactId>maven-compiler-plugin</artifactId> > - <version>${version.compiler.plugin}</version> > - <configuration> > - <source>${maven.compiler.source}</source> > - <target>${maven.compiler.target}</target> > - </configuration> > - </plugin> > {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

10 years, 9 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 Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13154?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13154: ------------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > 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 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13093) extendedDataTable column resizing and reordering not working on transient (stateless) views

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13093?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13093: ------------------------------- Fix Version/s: 4.3.5 5.0.0.Alpha3 (was: 5.0.0.Alpha2) > extendedDataTable column resizing and reordering not working on transient (stateless) views > ------------------------------------------------------------------------------------------- > > Key: RF-13093 > URL: https://issues.jboss.org/browse/RF-13093 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.2 > Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23 > Reporter: Salvo Isaja > Labels: jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > > When turning on transient (stateless) views in recent Mojarra versions (as per JSF 2.2 specification, to my best understanding), using request scoped backing beans, javax.faces.ViewState becomes the constant "stateless". Column resizing and reordering in extendedDataTable causes an Ajax request to the server, but in this case an invalid response is sent, containing only: > {code:xml} > <?xml version='1.0' encoding='UTF-8'?> > <partial-response></partial-response> > {code} > This causes an exception in {{jsf.js}} because the partial-response element has no children and no further JavaScript processing happens in the view until the page is reloaded. In the non-transient view case, I see a {{change}} element updating only the ViewState is returned, instead. > Other features seem to work pretty well in stateless mode, by the way. > Thanks -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13168: ------------------------------- Fix Version/s: 4.3.5 > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Brian Leathem > Labels: interop, jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13168: ------------------------------- Summary: 3rd party JSF component disappears on RichFaces ajax refresh (was: JSF component disappears on refresh using a4j:poll) > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Brian Leathem > Labels: interop, jsf22 > Fix For: 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13173) Address issues preventing 4.3.x framework/component use with JSF 2.2

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13173?page=com.atlassian.jira.plugin.s... ] Brian Leathem moved RFPL-3033 to RF-13173: ------------------------------------------ Project: RichFaces (was: RichFaces Planning) Key: RF-13173 (was: RFPL-3033) > Address issues preventing 4.3.x framework/component use with JSF 2.2 > -------------------------------------------------------------------- > > Key: RF-13173 > URL: https://issues.jboss.org/browse/RF-13173 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13173) Address issues preventing 4.3.x framework/component use with JSF 2.2

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13173?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13173: ------------------------------- Fix Version/s: 4.3.5 > Address issues preventing 4.3.x framework/component use with JSF 2.2 > -------------------------------------------------------------------- > > Key: RF-13173 > URL: https://issues.jboss.org/browse/RF-13173 > Project: RichFaces > Issue Type: Epic > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Fix For: 4.3.5 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13172) rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13172?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13172: ------------------------------- Fix Version/s: 5-Tracking > rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values > ------------------------------------------------------------------------------------------------------------ > > Key: RF-13172 > URL: https://issues.jboss.org/browse/RF-13172 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.3 > Reporter: Sergey Zubarev > Fix For: 5-Tracking > > > {code} > <rich:toolbar itemSeparator="line" id="repairWorkToolbar"> > <rich:toolbarGroup> > <a4j:commandLink value="btn1"/> > <a4j:commandLink value="btn2"/> > <a4j:commandLink value="btn3" *rendered="false"*/> > </rich:toolbarGroup> > <rich:toolbarGroup location="right"> > <a4j:commandLink value="btn_right"/> > </rich:toolbarGroup> > ... > {code} > In this case location="right" doesn't work : it displayed left. When I remove rendered="false" from btn3 all works fine. > Html debug shows, that code produced one extra element in colgroup tag when using rendered="false". -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13172) rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13172?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13172: ------------------------------- Labels: low_hanging_fruit (was: ) > rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values > ------------------------------------------------------------------------------------------------------------ > > Key: RF-13172 > URL: https://issues.jboss.org/browse/RF-13172 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.3 > Reporter: Sergey Zubarev > Labels: low_hanging_fruit > Fix For: 5-Tracking > > > {code} > <rich:toolbar itemSeparator="line" id="repairWorkToolbar"> > <rich:toolbarGroup> > <a4j:commandLink value="btn1"/> > <a4j:commandLink value="btn2"/> > <a4j:commandLink value="btn3" *rendered="false"*/> > </rich:toolbarGroup> > <rich:toolbarGroup location="right"> > <a4j:commandLink value="btn_right"/> > </rich:toolbarGroup> > ... > {code} > In this case location="right" doesn't work : it displayed left. When I remove rendered="false" from btn3 all works fine. > Html debug shows, that code produced one extra element in colgroup tag when using rendered="false". -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13172) rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13172?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13172: ------------------------------------ The ToolbarGroup Renderer uses the rendered children when rendering: https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav... but the ToolBar Renderer queries the ToolbarGroup for it's size including all children: https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav... A possible fix would involve changing the ToolBar Renderer to cast the component to a ToolbarGroup (after the instanceof check) and call the getRenderedChildren() method instead of the children() method to get the child count. > rich:toolbarGroup location="right" doesn't work if toolbarGroup location="left" contains not rendered values > ------------------------------------------------------------------------------------------------------------ > > Key: RF-13172 > URL: https://issues.jboss.org/browse/RF-13172 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.3 > Reporter: Sergey Zubarev > > {code} > <rich:toolbar itemSeparator="line" id="repairWorkToolbar"> > <rich:toolbarGroup> > <a4j:commandLink value="btn1"/> > <a4j:commandLink value="btn2"/> > <a4j:commandLink value="btn3" *rendered="false"*/> > </rich:toolbarGroup> > <rich:toolbarGroup location="right"> > <a4j:commandLink value="btn_right"/> > </rich:toolbarGroup> > ... > {code} > In this case location="right" doesn't work : it displayed left. When I remove rendered="false" from btn3 all works fine. > Html debug shows, that code produced one extra element in colgroup tag when using rendered="false". -- 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, 9 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