June 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13053) Showcase: push doesn't work on EAP 6.1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13053?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13053: ------------------------------- Fix Version/s: 4.3.3 5-Tracking > Showcase: push doesn't work on EAP 6.1 > -------------------------------------- > > Key: RF-13053 > URL: https://issues.jboss.org/browse/RF-13053 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.2 > Reporter: Pavol Pitonak > Fix For: 4.3.3, 5-Tracking > > > EAP 6.1 has more strict conditions for user passwords so we need to update JMS password in both web.xml and readme.md. It has to contain one number and one special character. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13041) Metamer: demos throw NullPointerException

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13041?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13041: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > Metamer: demos throw NullPointerException > ----------------------------------------- > > Key: RF-13041 > URL: https://issues.jboss.org/browse/RF-13041 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > WildFly: Weld Integration 8.0.0.Alpha1 > JBoss AS 8.0.0.Alpha1 > Java(TM) SE Runtime Environment 1.7.0_17-b02 @ Linux > Chrome 26.0.1410.63 @ Linux x86_64 > Reporter: Jan Papousek > Fix For: 5.0.0.Alpha2 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13044) Inplace select: JS error inside extended data table

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13044?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13044: ---------------------------------- Assignee: Pavol Pitonak > Inplace select: JS error inside extended data table > --------------------------------------------------- > > Key: RF-13044 > URL: https://issues.jboss.org/browse/RF-13044 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, component-tables > Affects Versions: 4.3.2, 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Mojarra 2.1.13 > EAP 6.0.1 > Java(TM) SE Runtime Environment 1.6.0_32-b05 @ Linux > Chrome 27.0.1453.93 @ Linux x86_64 > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceSelect/csv.xhtm... > # open browser console > # click "set wrong value" button next to "custom" inplace input > result: > * value "rich faces" is set as expected but it is not submitted like in used case without EDT and inplace select stays open > * works fine in all other templates -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13040) Examples don't work on WildFly

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13040: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > Examples don't work on WildFly > ------------------------------ > > Key: RF-13040 > URL: https://issues.jboss.org/browse/RF-13040 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha1 > Reporter: Jan Papousek > Fix For: 5.0.0.Alpha2 > > > - components-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > - showcase (jbas71 classifier): can't deploy, the following error appears (standalone-full.xml): > {code} > 16:22:01,672 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.deployment.default-host./showcase: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./showcase: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:194) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) > ... 6 more > Caused by: java.lang.RuntimeException: Capability org.richfaces.demo.push.JMSInitializer was not correctly initialized > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:66) > at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) > at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) > at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) > at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:303) > at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:288) > at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:685) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) > ... 8 more > Caused by: java.lang.RuntimeException: Unable to create topic 'pushJms' (JNDI: /topic/pushJms) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:86) > at org.richfaces.demo.push.JMSInitializer.initializeJMS(JMSInitializer.java:75) > at org.richfaces.demo.push.JMSInitializer.initializeCapability(JMSInitializer.java:63) > at org.richfaces.demo.push.AbstractCapabilityInitializer.processEvent(AbstractCapabilityInitializer.java:63) > ... 15 more > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81) > at org.richfaces.demo.push.provider.AS7MessagingProviderManagement.createTopic(AS7MessagingProviderManagement.java:83) > at org.richfaces.demo.push.JMSInitializer.createTopic(JMSInitializer.java:84) > ... 18 more > Caused by: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:148) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:90) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 21 more > {code} > - irc-client: can't deploy (standalone-full.xml) > {code} > 16:35:39,805 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./irc-client.UndertowDeploymentInfoService: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:587) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:200) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > Caused by: java.lang.ClassNotFoundException: org.richfaces.webapp.PushFilter from [Module "deployment.irc-client.war:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:266) [rt.jar:1.7.0_17] > at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:426) > ... 6 mor > {code} > - jpa-demo: with standalone-jbossweb.xml OK, with standalone-full.xml deployable, but doesn't work > ... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13027) Warning when deploying showcase - using a private modules which can be removed in the future

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13027?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13027: ------------------------------- Fix Version/s: 5-Tracking > Warning when deploying showcase - using a private modules which can be removed in the future > -------------------------------------------------------------------------------------------- > > Key: RF-13027 > URL: https://issues.jboss.org/browse/RF-13027 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 5.0.0.Alpha1 > Environment: JBoss AS 7.1.1.Final > Reporter: Juraj Húska > Priority: Trivial > Fix For: 5-Tracking > > > There is following warning when deploying showcase: > {code} > 11:54:39,865 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.richfaces-showcase-5.0.0.Alpha1-jbas71.war" is using a private module ("com.google.guava:main") which may be changed or removed in future versions without notice. > 11:54:39,867 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.richfaces-showcase-5.0.0.Alpha1-jbas71.war" is using a private module ("org.jboss.as.protocol:main") which may be changed or removed in future versions without notice. > 11:54:39,868 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.richfaces-showcase-5.0.0.Alpha1-jbas71.war" is using a private module ("org.jboss.marshalling.river:main") which may be changed or removed in future versions without notice. > {code} > This was present in RF 4 as well and I guess that we are aware of this, but are we OK with 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13031) Rebrand all RichFaces 4 to RichFaces 5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13031?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13031: ---------------------------------- Assignee: Lukáš Fryč This is a little vague, can you elaborate what you are getting at in the description field? > Rebrand all RichFaces 4 to RichFaces 5 > -------------------------------------- > > Key: RF-13031 > URL: https://issues.jboss.org/browse/RF-13031 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Minor > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13007) CDK Tests fail during build on Windows 8

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13007?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13007: ------------------------------- Fix Version/s: 5-Tracking > CDK Tests fail during build on Windows 8 > ---------------------------------------- > > Key: RF-13007 > URL: https://issues.jboss.org/browse/RF-13007 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Environment: Win 8 x64 > Oracle Java 7u21 x64 > Reporter: Cody Lerum > Fix For: 5-Tracking > > > https://gist.github.com/codylerum/5628835 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13011) Run Resource Plugin for Showcase to reduce number of requests

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13011?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13011: ------------------------------- Fix Version/s: 5-Tracking > Run Resource Plugin for Showcase to reduce number of requests > ------------------------------------------------------------- > > Key: RF-13011 > URL: https://issues.jboss.org/browse/RF-13011 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.2, 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Fix For: 5-Tracking > > > Showcase loads # of resources for arbitrary requests. > We can run resource plugin on Showcase to pack them into single package. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13026) Warning when deploying showcase - libraries do not point to a valid jar for a Class-Path reference

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13026?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13026: ------------------------------- Fix Version/s: 5-Tracking > Warning when deploying showcase - libraries do not point to a valid jar for a Class-Path reference > -------------------------------------------------------------------------------------------------- > > Key: RF-13026 > URL: https://issues.jboss.org/browse/RF-13026 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: regression, showcase > Affects Versions: 5.0.0.Alpha1 > Environment: JBoss AS 7.1.1.Final > Reporter: Juraj Húska > Priority: Minor > Fix For: 5-Tracking > > > When deploying showcase these WARNINGs are presenting: > {code} > 11:54:39,307 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry xml-apis.jar in "/content/richfaces-showcase-5.0.0.Alpha1-jbas71.war/WEB-INF/lib/serializer-2.7.1.jar" does not point to a valid jar for a Class-Path reference. > 11:54:39,309 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry xercesImpl.jar in "/content/richfaces-showcase-5.0.0.Alpha1-jbas71.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference. > 11:54:39,309 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry xml-apis.jar in "/content/richfaces-showcase-5.0.0.Alpha1-jbas71.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference. > 11:54:39,310 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry serializer.jar in "/content/richfaces-showcase-5.0.0.Alpha1-jbas71.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference. > {code} > According [this|https://community.jboss.org/thread/198349] thread we can ignore these WARNINGS. > Are you OK with them ? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13006) Rename SessionTopicListener2 to SessionTopicListener

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13006?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13006: ---------------------------------- Assignee: Lukáš Fryč WDYT? > Rename SessionTopicListener2 to SessionTopicListener > ---------------------------------------------------- > > Key: RF-13006 > URL: https://issues.jboss.org/browse/RF-13006 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Priority: Trivial > > After deleting the old {{SessionTopicListener}} the {{SessionTopicListener2}} can be renamed back to {{SessionTopicListener}}. > However, in this comment it is noted that you wanted to left the 2 in the name. > https://issues.jboss.org/browse/RF-12745?focusedCommentId=12765159&page=c... > Is it still correct ? -- 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, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues June 2013