[JBoss JIRA] (RF-13248) Switch RichFaces smoke tests to run on WildFly 8 by default
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13248?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13248:
-------------------------------
Sprint: 5.0.0.Alpha3 - Sprint 1
> Switch RichFaces smoke tests to run on WildFly 8 by default
> -----------------------------------------------------------
>
> Key: RF-13248
> URL: https://issues.jboss.org/browse/RF-13248
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: component
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
>
> With start of WildFly Beta/CR release chain, we can switch our tests consume it, it means:
> * tweaking TravisCI configuration
> Note that tests have problem to pass on WildFly Beta1:
> {code}
> Tests run: 34, Failures: 1, Errors: 16, Skipped: 1
> {code}
> so we need to analyze a cause of the failure first.
--
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, 12 months
[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:
-------------------------------
Labels: jsf22 (was: )
> 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
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
>
> - 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, 12 months
[JBoss JIRA] (RF-13248) Switch RichFaces smoke tests to run on WildFly 8 by default
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13248?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13248:
-------------------------------
Labels: jsf22 (was: )
> Switch RichFaces smoke tests to run on WildFly 8 by default
> -----------------------------------------------------------
>
> Key: RF-13248
> URL: https://issues.jboss.org/browse/RF-13248
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: component
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
>
> With start of WildFly Beta/CR release chain, we can switch our tests consume it, it means:
> * tweaking TravisCI configuration
> Note that tests have problem to pass on WildFly Beta1:
> {code}
> Tests run: 34, Failures: 1, Errors: 16, Skipped: 1
> {code}
> so we need to analyze a cause of the failure first.
--
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, 12 months
[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:
-------------------------------
Sprint: 5.0.0.Alpha3 - Sprint 1
> 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
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> 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, 12 months
[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:
-------------------------------
Sprint: 5.0.0.Alpha3 - Sprint 1
> 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
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> 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, 12 months
[JBoss JIRA] (RF-13307) Support java.util.Set in iteration components
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13307?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13307:
-------------------------------
Sprint: 5.0.0.Alpha3 - Sprint 1
> Support java.util.Set in iteration components
> ---------------------------------------------
>
> Key: RF-13307
> URL: https://issues.jboss.org/browse/RF-13307
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.4, 5.0.0.Alpha1
> Environment: Wildfly-8.0.0.Beta1
> Reporter: Matti Bickel
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
>
> JSF-2.2 now supports iteration over sets as in
> {code:xml}
> <h:dataTable value="#{myBean.mySet}" var="elem">
> <h:column>#{elem.name}</h:column>
> </h:dataTable>
> {code}
> Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
> Would be nice if RF catches up with JSF here.
--
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, 12 months
[JBoss JIRA] (RF-13390) Region fails to render after ajax request
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13390?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13390:
-------------------------------
Sprint: 5.0.0.Alpha3 - Sprint 1
> Region fails to render after ajax request
> -----------------------------------------
>
> Key: RF-13390
> URL: https://issues.jboss.org/browse/RF-13390
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Environment: RF 5 Snapshot: aa130b9c034ceb49814e0d409329828d8b81f0d0
> Wildfly 8.0.0.Beta2-SNAPSHOT
> Mojarra 2.2.4-jbossorg-1 20131017-1524
> Reporter: Cody Lerum
> Labels: jsf22
> Fix For: 4.3.5, 5.0.0.Alpha3
>
>
> When
> {code}
> <r:region>
> <h:inputText>
> <r:ajax execute="@this" render="@region" />
> </h:inputText>
> </r:region>
> {code}
> A partial response seems to be generated with the correct content but the dom is not updated
--
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, 12 months
[JBoss JIRA] (RF-13197) Input with name javax.faces.ViewState is not rendered after submit
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13197?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13197:
-------------------------------
Sprint: 5.0.0.Alpha3 - Sprint 1
> 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
> Labels: jsf22
> Fix For: 5.0.0.Alpha3
>
>
> 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, 12 months