Description of problem:
when deploying web application and specifying runtime-name without .war the deployment is deployed but the context doesn't become available.
How reproducible: always
Steps to Reproduce:
1. Start EAP
2. deploy war with specified runtime-name either via CLI or Web console
* deploy --runtime-name=web-app web-app.war
* deploy --runtime-name=web-app2.war web-app2.war
3. check logs and URL whether the deployment context is available
It is available only in second case, not in the first case => (localhost:8080/web-app is not available and localhost:8080/web-app2 is)
Also in first case the deployment would be available.
If you think this belongs to another component, please update it.
Not a bug. The .war suffix is what triggers the deployment unit processors to recognize that the deployment is relevant. If you didn't use runtime-name and just did a simple deploy of a file with the .war suffix removed or changed you'd get the same behavior: