[JBoss JIRA] (JBSEAM-5114) Seam applications can't deploy on Wildfly 8.0.0.Alpha1
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5114?page=com.atlassian.jira.plugi... ]
Tomaz Cerar commented on JBSEAM-5114:
-------------------------------------
This problem should be fixed in newer versions of WildFly, it think first public release with fix should be CR1
> Seam applications can't deploy on Wildfly 8.0.0.Alpha1
> ------------------------------------------------------
>
> Key: JBSEAM-5114
> URL: https://issues.jboss.org/browse/JBSEAM-5114
> Project: Seam 2
> Issue Type: Bug
> Components: Platform interoperability
> Affects Versions: 2.3.1.CR1
> Reporter: Ron Šmeral
> Fix For: The future
>
>
> Seam applications currently can't be deployed to WildFly due to errors in deployment scanning.
> {noformat}
> 08:51:55,656 INFO [javax.servlet.ServletContextListener] (MSC service thread 1-10) Welcome to Seam 2.3.1.CR1
> 08:51:55,673 WARN [org.jboss.seam.util.Resources] (MSC service thread 1-10) Unable to determine real path from servlet context for "/WEB-INF/dev" path does not exist.
> 08:51:55,688 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/jboss-seam.jar (No such file or directory)
> at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17]
> at java.util.zip.ZipFile.<init>(ZipFile.java:214) [rt.jar:1.7.0_17]
> at java.util.zip.ZipFile.<init>(ZipFile.java:144) [rt.jar:1.7.0_17]
> at java.util.zip.ZipFile.<init>(ZipFile.java:158) [rt.jar:1.7.0_17]
> at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1]
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907)
> 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]
> 08:51:55,690 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/blog-ejb.jar (No such file or directory)
> at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17]
> at java.util.zip.ZipFile.<init>(ZipFile.java:214) [rt.jar:1.7.0_17]
> at java.util.zip.ZipFile.<init>(ZipFile.java:144) [rt.jar:1.7.0_17]
> at java.util.zip.ZipFile.<init>(ZipFile.java:158) [rt.jar:1.7.0_17]
> at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1]
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907)
> 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]
> 08:51:55,692 WARN [org.jboss.seam.deployment.URLScanner] (MSC service thread 1-10) could not read entries: java.io.FileNotFoundException: /content/seam-blog.ear/blog-web.war/WEB-INF/lib/jboss-seam-ui-2.3.1.CR1.jar (No such file or directory)
> at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_17]
> at java.util.zip.ZipFile.<init>(ZipFile.java:214) [rt.jar:1.7.0_17]
> at java.util.zip.ZipFile.<init>(ZipFile.java:144) [rt.jar:1.7.0_17]
> at java.util.zip.ZipFile.<init>(ZipFile.java:158) [rt.jar:1.7.0_17]
> at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1]
> at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1]
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907)
> 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]
> 08:51:55,694 INFO [org.jboss.seam.init.Initialization] (MSC service thread 1-10) reading /WEB-INF/components.xml
> 08:51:55,727 INFO [org.jboss.seam.init.Initialization] (MSC service thread 1-10) reading properties from: /seam.properties
> 08:51:55,749 INFO [org.jboss.seam.Component] (MSC service thread 1-10) Component: org.jboss.seam.core.init, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.core.Init
> 08:51:55,766 INFO [org.jboss.seam.Component] (MSC service thread 1-10) Component: org.jboss.seam.async.dispatcher, scope: STATELESS, type: STATELESS_SESSION_BEAN, class: org.jboss.seam.async.TimerServiceDispatcher, JNDI: java:app/jboss-seam/TimerServiceDispatcher
> 08:51:55,789 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC000001: Failed to start service jboss.undertow.deployment.default-host./seam-blog: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: 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.NullPointerException
> 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.NullPointerException
> at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:145)
> at org.jboss.seam.init.Initialization.init(Initialization.java:813)
> at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:127)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:172)
> ... 6 more
> 08:51:55,798 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014613: Operation ("deploy") failed - address: ({"deployment" => "seam-blog.ear"}) - failure description: {
> "JBAS014671: Failed services" => {"jboss.undertow.deployment.default-host./seam-blog" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"},
> "JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.deployment.unit.\"seam-blog.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"seam-blog.ear\".\"jboss-seam.jar\".deploymentCompleteService]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]"
> ]
> }
> 08:51:55,810 ERROR [org.jboss.as.server] (management-handler-thread - 1) JBAS015870: Deploy of deployment "seam-blog.ear" was rolled back with the following failure message:
> {
> "JBAS014671: Failed services" => {"jboss.undertow.deployment.default-host./seam-blog" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./seam-blog: Failed to start service
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> Caused by: java.lang.NullPointerException"},
> "JBAS014771: Services with missing/unavailable dependencies" => [
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InAppClientContainer is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.deployment.unit.\"seam-blog.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"seam-blog.ear\".\"jboss-seam.jar\".deploymentCompleteService]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ValidatorFactory is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher.HandleDelegate is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.TimerServiceDispatcher]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.ORB is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.InstanceName is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]",
> "jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations.Validator is missing [jboss.naming.context.java.comp.seam-blog.jboss-seam.EjbSynchronizations]"
> ]
> }
> {noformat}
--
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] (JBSEAM-5002) Components included with ui:include src="#{pageScopedViewId} broken
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5002?page=com.atlassian.jira.plugi... ]
Marek Novotny updated JBSEAM-5002:
----------------------------------
Affects Version/s: 2.3.1.Final
> Components included with ui:include src="#{pageScopedViewId} broken
> -------------------------------------------------------------------
>
> Key: JBSEAM-5002
> URL: https://issues.jboss.org/browse/JBSEAM-5002
> Project: Seam 2
> Issue Type: Bug
> Components: JSF Integration
> Affects Versions: 2.3.0.BETA2, 2.3.0.Final, 2.3.1.Final
> Environment: JBoss AS 7.1.2, Seam 2.3.0.CR1-SNAPSHOT (r14986)
> Reporter: Marek Schmidt
> Assignee: Marek Novotny
> Fix For: 2.3.2.CR1
>
> Attachments: JBSEAM-5002.ear, JBSEAM-5002.tar.gz
>
>
> The following scenario that used to work in AS5/Seam2.2 doesn't work anymore in AS7/Seam2.3 for page-scoped and conversation-scoped "viewId" components:
> index.xhtml:
> {code}
> <h:form>
> <h:commandButton action="#{viewId.component1}" value="Component 1" />
> <h:commandButton action="#{viewId.component2}" value="Component 2" />
> </h:form>
>
> <ui:include src="#{viewId.viewId}"/>
> {code}
> {code}
> @Scope(ScopeType.PAGE)
> @Name("viewId")
> public class ViewIdComponent implements Serializable
> {
> private String viewId = "/component1.xhtml";
>
> public void setViewId(String viewId) {
> this.viewId = viewId;
> }
>
> public String getViewId() {
> return viewId;
> }
>
> public void component1() {
> setViewId("/component1.xhtml");
> }
>
> public void component2() {
> setViewId("/component2.xhtml");
> }
> }
> {code}
> (compoent1 and 2 are redacted, contain a simple form)
> Only the first component works properly, actions in "component2" doesn't seem to be called after switching to "Component 2".
--
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] (JBSEAM-5002) Components included with ui:include src="#{pageScopedViewId} broken
by Marek Novotny (JIRA)
[ https://issues.jboss.org/browse/JBSEAM-5002?page=com.atlassian.jira.plugi... ]
Marek Novotny resolved JBSEAM-5002.
-----------------------------------
Resolution: Done
Works with JSF 2.1.19, upgrade it in JBoss AS 7.1.1.Final or download EAP 6.1.0 free for development purposes - http://www.jboss.org/products/eap
> Components included with ui:include src="#{pageScopedViewId} broken
> -------------------------------------------------------------------
>
> Key: JBSEAM-5002
> URL: https://issues.jboss.org/browse/JBSEAM-5002
> Project: Seam 2
> Issue Type: Bug
> Components: JSF Integration
> Affects Versions: 2.3.0.BETA2, 2.3.0.Final
> Environment: JBoss AS 7.1.2, Seam 2.3.0.CR1-SNAPSHOT (r14986)
> Reporter: Marek Schmidt
> Assignee: Marek Novotny
> Fix For: 2.3.2.CR1
>
> Attachments: JBSEAM-5002.ear, JBSEAM-5002.tar.gz
>
>
> The following scenario that used to work in AS5/Seam2.2 doesn't work anymore in AS7/Seam2.3 for page-scoped and conversation-scoped "viewId" components:
> index.xhtml:
> {code}
> <h:form>
> <h:commandButton action="#{viewId.component1}" value="Component 1" />
> <h:commandButton action="#{viewId.component2}" value="Component 2" />
> </h:form>
>
> <ui:include src="#{viewId.viewId}"/>
> {code}
> {code}
> @Scope(ScopeType.PAGE)
> @Name("viewId")
> public class ViewIdComponent implements Serializable
> {
> private String viewId = "/component1.xhtml";
>
> public void setViewId(String viewId) {
> this.viewId = viewId;
> }
>
> public String getViewId() {
> return viewId;
> }
>
> public void component1() {
> setViewId("/component1.xhtml");
> }
>
> public void component2() {
> setViewId("/component2.xhtml");
> }
> }
> {code}
> (compoent1 and 2 are redacted, contain a simple form)
> Only the first component works properly, actions in "component2" doesn't seem to be called after switching to "Component 2".
--
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