-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
None
CDI complains when deploying a war setting the runtime name without extension.
The following is logged with the attached application:
2015-11-22 21:55:59,830 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "cdi-test-1.0-SNAPSHOT.war" (runtime-name: "cdi-test") 2015-11-22 21:55:59,861 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment cdi-test 2015-11-22 21:55:59,882 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Starting Services for CDI deployment: cdi-test 2015-11-22 21:55:59,888 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0009: Starting weld service for deployment cdi-test 2015-11-22 21:55:59,955 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-000119: Not generating any bean definitions from com.example.BeanTest because of underlying class loading error: Type com.example.BeanTest from [Module "deployment.cdi-test:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error. 2015-11-22 21:56:00,243 INFO [org.jboss.as.server] (XNIO-1 task-2) WFLYSRV0010: Deployed "cdi-test-1.0-SNAPSHOT.war" (runtime-name : "cdi-test")
Application is apparently deployed, but doesn't work. I'm not sure this is a bug in Wildfly or in Weld subsystem or even expected behaviour, since every type of file is allowed to be deployed. Is the extension used to determine the type of deployment?
