Bug 1119655

Summary: runtime-name without suffix (.war) doesn't make the deployment available
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Radim Hatlapatka <rhatlapa>
Component: WebAssignee: Rémy Maucherat <rmaucher>
Status: CLOSED NOTABUG QA Contact: Radim Hatlapatka <rhatlapa>
Severity: low Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.3.0CC: emuckenh, jcechace
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-15 13:33:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Radim Hatlapatka 2014-07-15 08:46:40 UTC
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 

Actual results:
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)

Expected results:
Also in first case the deployment would be available.

Additional info:
If you think this belongs to another component, please update it.

Comment 1 Brian Stansberry 2014-07-15 13:33:16 UTC
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:

deploy web-app.xyz