Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-13006

Seam integration jar name mismatch between WildFly Core and WildFly

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.CR2
    • 7.1.0.CR1
    • None

    Description

      Trying to deploy a simple JBoss Seam 2.3.x application on WildFly 11.0.0.CR1 will fail with:

      09:06:16,492 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."pkg-seamJboss23-notChangedComponentsReinitializedOnce.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "pkg-seamJboss23-notChangedComponentsReinitializedOnce.war"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
	at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:161)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
	... 5 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
	at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:127)
	at org.jboss.as.server.deployment.integration.Seam2Processor.deploy(Seam2Processor.java:158)
	... 6 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0157: No Seam Integration jar present: Module "org.jboss.integration.ext-content" from local module loader @1ae369b7 (finder: local module finder @6fffcba5 (roots: /Users/poolik/app_servers/wildfly-11.0.0.CR1/modules,/Users/poolik/app_servers/wildfly-11.0.0.CR1/modules/system/layers/base))
	at org.jboss.as.server.deployment.integration.Seam2Processor.getSeamIntResourceRoot(Seam2Processor.java:100)
	... 7 more

      The issue is that in WFLY-8660 the Seam Integration jar was renamed to jboss-seam-int-jbossas.jar
      (commit) but Seam2Processor in WildFly Core still expects it to be jboss-seam-int.jar

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-3237 Seam integration jar name mismatch between WildFly Core and WildFly

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-12949 (7.1.0) Upgrade to WildFly Core to 3.0.3.Final-redhat

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              tomazcerar Tomaž Cerar (Inactive)
              poolik Tõnis Pool (Inactive)
              Rostislav Svoboda Rostislav Svoboda
              Rostislav Svoboda Rostislav Svoboda
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: