Bug 799163

Summary:	Content deployments for existing exploded applications is done as zipped deployment (EAP4)
Product:	[Other] RHQ Project	Reporter:	Stefan Negrea <snegrea>
Component:	Content	Assignee:	Stefan Negrea <snegrea>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	4.3	CC:	fbrychta, hrupp, lzoubek
Target Milestone:	---
Target Release:	JON 3.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	795851	Environment:
Last Closed:	2013-09-03 15:10:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	795851
Bug Blocks:

Description Stefan Negrea 2012-03-01 23:24:25 UTC

Summary:
New content deployment for existing exploded applications using content system causes deployment to become zipped in EAP4.x.

How reproducible:
Always

Steps to Reproduce:
1. EAP4.3 started in default profile inventoried in JON.
2. Deploy new content for an existing exploded WAR application.
3. Wait for deployment to complete.
4. Assert that deployment is exploded on filesystem (in EAP deploy dir).
5. Assert that new content is reachable on EAP via HTTP.
  
Actual results:
- on file system it is no longer exploded, you'll find archive file (incorrect behaviour)
- modified version of the application becomes available via HTTP (correct behaviour)

Expected results:
- modified version of the application becomes available via HTTP
- on file system, deployment remains exploded

Comment 1 Stefan Negrea 2012-03-01 23:28:38 UTC

Commit to master branch:
http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=55bea2a01bd0b2a2907b16f3e10dbefd5137f313

Comment 2 Stefan Negrea 2012-05-22 12:46:03 UTC

I retested this and the issue has been resolved. 

I also verified that there is no similar problem for the AS5 and Tomcat plugins. The AS5 plugin uses a different deployment model, while Tomcat did not require the fix.

Comment 3 Filip Brychta 2012-05-29 06:36:03 UTC

Verified on jon-server-3.1.0.ER6

Comment 4 Heiko W. Rupp 2013-09-03 15:10:44 UTC

Bulk closing of old issues in VERIFIED state.