[jboss-jira] [JBoss JIRA] (WFLY-5720) CDI deployment problems on web application runtime name not ending in .war

[Guillermo González de Agüero (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132885#comment-13132885 ] 

Guillermo González de Agüero commented on WFLY-5720:
----------------------------------------------------

Ok, thanks for the clarification. I think at least it should be added do the documentation and maybe to the description on the management console. I'll see if I can take it up myself.

As a newcomer, I've find myself in trouble sometimes because of deployed applications that hadn't really been processed because of folder structure errors, or by a missing suffix in the runtime name. Maybe a message could be logged if none of the registered extensions have processed the deployment? It'd be of great help for beginners. Is it worth opening a thread on the mailing list?

Also, is it correct for the Weld subsystem just to process a file that is not a recognized application (ejb/war/rar/etc)?

> CDI deployment problems on web application runtime name not ending in .war
> --------------------------------------------------------------------------
>
>                 Key: WFLY-5720
>                 URL: https://issues.jboss.org/browse/WFLY-5720
>             Project: WildFly
>          Issue Type: Bug
>         Environment: Wildfly 10CR4
>            Reporter: Guillermo González de Agüero
>            Assignee: Jason Greene
>         Attachments: cdi-test.war
>
>
> CDI complains when deploying a war setting the runtime name without extension.
> The following is logged with the attached application:
> {code:java}
> 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")
> {code}
> 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?



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)