[JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-13230:
------------------------------------
Ok I can see what you mean now.
I re-used the sample and added a4j:commandButton calling a bean method (setting state to null) and rendering the table.
But try as I might I cannot make this working on 4.3.3.Final where you claim this should work (obviously it does not work on 4.3.x either). I even tried using differently annotated beans (managed, session or view scoped) but with no effect.
Therefore so far, this seems to be a bug but not a regression. If you really got this working on 4.3.3 I wonder if you would have a working sample to show. Until then I am removing the regression label.
Also I will write a test for this issue so we are able to resolve this problem.
> Resetting table state on extendedDataTable does not reset table when using ajax re-render
> -----------------------------------------------------------------------------------------
>
> Key: RF-13230
> URL: https://issues.jboss.org/browse/RF-13230
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.4
> Reporter: Immo Benjes
> Assignee: Matej Novotny
> Labels: regression
> Fix For: 4.3.5
>
>
> On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form.
> To reproduce:
> rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same.
> This used to work on RF 4.3.3
--
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, 4 months
[JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.s... ]
Matej Novotny updated RF-13230:
-------------------------------
Labels: (was: regression)
> Resetting table state on extendedDataTable does not reset table when using ajax re-render
> -----------------------------------------------------------------------------------------
>
> Key: RF-13230
> URL: https://issues.jboss.org/browse/RF-13230
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.4
> Reporter: Immo Benjes
> Assignee: Matej Novotny
> Fix For: 4.3.5
>
>
> On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form.
> To reproduce:
> rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same.
> This used to work on RF 4.3.3
--
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, 4 months
[JBoss JIRA] (RF-13197) Input with name javax.faces.ViewState is not rendered after submit
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13197?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13197:
---------------------------------
Imho this is duplicate of RF-13317
> Input with name javax.faces.ViewState is not rendered after submit
> ------------------------------------------------------------------
>
> Key: RF-13197
> URL: https://issues.jboss.org/browse/RF-13197
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 5.0.0.Alpha1
> Environment: WildFly 8.0.Alpha4 also GlassFish 4
> Mojarra 2.2
> Chrome, Firefox
> Reporter: Juraj Húska
> Assignee: Lukáš Fryč
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> The issue is reproducible with framework test {{ITMultipleFormUpdate.when_form_is_explicitly_listed_in_render_then_its_ViewState_should_be_updated_after_response}}.
> Expected:
> After submitting the form, the {{ViewState}} should be updated.
> Actual:
> Elements with the name {{javax.faces.ViewState}} are not rendered for both of the inputs.
> Please see steps to reproduce.
--
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, 4 months
[JBoss JIRA] (RF-13040) Examples don't work on WildFly
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13040 at 12/12/13 11:11 AM:
------------------------------------------------------------
components-demo work on WildFly Beta2-SNAPSHOT, but it throws {{View /examples/input/calendar.jsf could not be restored.}} for each postback. It is likely caused by WFLY-2638.
was (Author: lfryc):
components-demo work on WildFly Beta2-SNAPSHOT, but it throws {{View /examples/input/calendar.jsf could not be restored.}} for each postback. I think it is related to RF-13197.
The same issue with Showcase.
> 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
> Assignee: Lukáš Fryč
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> - 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
10 years, 4 months
[JBoss JIRA] (RF-13040) Examples don't work on WildFly
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13040:
----------------------------
Environment: WildFly 8.0.0.Beta1 (was: WildFly 8.0.0.Alpha1)
> 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.Beta1
> Reporter: Jan Papousek
> Assignee: Lukáš Fryč
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> - 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
10 years, 4 months
[JBoss JIRA] (RF-13040) Examples don't work on WildFly
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13040?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13040:
----------------------------
Environment: WildFly 8.0.0.Beta2-SNAPSHOT (was: WildFly 8.0.0.Beta1)
> 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.Beta2-SNAPSHOT
> Reporter: Jan Papousek
> Assignee: Lukáš Fryč
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> - 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
10 years, 4 months
[JBoss JIRA] (RF-13437) contextMenu: support hiding by clicking outside only
by Lutz Ulrich (JIRA)
Lutz Ulrich created RF-13437:
--------------------------------
Summary: contextMenu: support hiding by clicking outside only
Key: RF-13437
URL: https://issues.jboss.org/browse/RF-13437
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-menu
Reporter: Lutz Ulrich
Priority: Minor
Currently (until version 4.3.4), context menus always disappear when the mouse cursor is moved outside the menu. It should be possible to restrict hiding the menu when the user clicks somewhere else, like in many other applications, like Windows Explorer.
I was able to achieve this behavior by unbinding the event handler for mouseleave via extra scripting.
{{RichFaces.Event.unbindById(menu.id, 'mouseleave');}}
(Note that the code only prevents hiding the main menu on mouseleave.
Sub-menus / menuGroups are still closed on mouseleave.)
But it would be better if the contextMenu would support an attribute for turning on 'hide by outside click only'.
--
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, 5 months
[JBoss JIRA] (RF-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13317:
---------------------------------
The resolution should try to address RF-12865.
> ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()
> -----------------------------------------------------------------------------------------------
>
> Key: RF-13317
> URL: https://issues.jboss.org/browse/RF-13317
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1
> Reporter: Matti Bickel
> Assignee: Lukáš Fryč
> Priority: Critical
> Labels: jsf22
> Fix For: 4.3.5, 5.0.0.Alpha3
>
>
> I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests:
> When the response comes back, the data is fine but I get a JSF error saying
> bq. During update: javax.faces.ViewState not found
> Following that, no componentData is available to the Autocomplete component and no suggestions get displayed.
> For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/no...] says:
> {quote}
> Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view.
> {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, 5 months
[JBoss JIRA] (RF-13230) Resetting table state on extendedDataTable does not reset table when using ajax re-render
by Immo Benjes (JIRA)
[ https://issues.jboss.org/browse/RF-13230?page=com.atlassian.jira.plugin.s... ]
Immo Benjes commented on RF-13230:
----------------------------------
Sorry I confused the issues here. Two different bugs, the forum is indeed for RF-13226.
You wrote:
{code}
Changing the column ordering - JSON String is correctly passed to the bean and stored.
Setting its value to null using ajax - used a4j:commandButton, set to null, variable was null
Rerender component - nothing happened, table is still modified
{code}
The table should be back to default state when you reset the tableState and that is not happening.
> Resetting table state on extendedDataTable does not reset table when using ajax re-render
> -----------------------------------------------------------------------------------------
>
> Key: RF-13230
> URL: https://issues.jboss.org/browse/RF-13230
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.4
> Reporter: Immo Benjes
> Assignee: Matej Novotny
> Labels: regression
> Fix For: 4.3.5
>
>
> On a extendedDataTable resetting the table state and then re-rendering the table via ajax does not work, the table still shows the custom column ordering and column width. Only when reloading the complete page, the table is displayed in its default form.
> To reproduce:
> rich:extendedDataTable with tableState help in a (e.g. Seam conversation scoped bean). Change the column ordering, now call an ajax method that resets the table state to null or an empty string. Re-render the table after completion. The column ordering stays the same.
> This used to work on RF 4.3.3
--
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, 5 months