-
Bug
-
Resolution: Done
-
Major
-
2.0.6.Final
-
None
Command deploy --url=http://localhost/test/simple-servlet.war
creates invalid deployment
According to logs everything seems to be fine
15:03:57,505 INFO [org.jboss.as.repository] (management-handler-thread - 2) WFLYDR0001: Content added at location /tmp/jboss-eap-7.0/standalone/data/content/5e/5e5709be9a06a9ed7bcb2100a4143400fea887/content 15:03:57,531 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "/test/simple-servlet.war" (runtime-name: "/test/simple-servlet.war") 15:03:58,238 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Registered web context: //test/simple-servlet 15:03:58,320 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "/test/simple-servlet.war" (runtime-name : "/test/simple-servlet.war")
but web context http://localhost:8080//test/simple-servlet isn't accessible, it returns 404 - Not Found.
(simple-servlet.war doesn't contain jboss-web.xml, so no context root is defined there)
- clones
-
JBEAP-2768 deploy --url command creates invalid deployment
- Closed
- relates to
-
WFLY-367 Expose "upload-deployment-url" operation via the CLI high-level "deploy" command
- Closed