Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-3576

deployment is not accessible in runtime when deployed with runtime-name not using .war extension




      According to the folowing blog-post, when using custom --name or --runtime-name for deployment, the file extension (.war, .jar, .ear,...) need to be included so server can distinguish type of deployment somehow.

      Currently there is no such check - when I try to deploy any .war app using either web-console or CLI with my custom '--runtime-name' and/or '--name' without .war suffix, server does not complain anyhow:

      deploy --runtime-name=alice --name=bob /tmp/eve.war

      Message in server log:

      17:30:48,469 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "bob" (runtime-name: "alice")
      17:30:48,499 INFO  [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0010: Deployed "bob" (runtime-name : "alice")

      Although, when I try to access content of the war app via URL, I get only 404 Not found HTTP response. Also I cannot see any deployment content when browsing via CLI:


      Even when I raise logging level to DEBUG, I can see no suspicious messages that deployed app has not been completely deployed.

      If such suffix is required, we need to inform user about it. We need to update description text for '--name' and '--runtime-name' atributes of deploy command in CLI (see deploy --help). Also when no such suffix is provided (and/or we fail to distinguish type of deployment in a different way) we need to print error message that deploy operation was not completely successful so customer is aware of it right-away.


        Issue Links



              chaowan@redhat.com Chao Wang
              jstourac@redhat.com Jan Stourac
              0 Vote for this issue
              5 Start watching this issue