Bug 1002647 - Deleting deployed war file does not remove 'Applications' folder and underlying resources under 'Switchyard'
Summary: Deleting deployed war file does not remove 'Applications' folder and underlyi...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- SOA 6
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: JON 3.2.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-29 16:08 UTC by Varun Khurana
Modified: 2013-12-10 23:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 14:05:19 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Varun Khurana 2013-08-29 16:08:40 UTC 
Description of problem:
Deleting deployed war file does not remove 'Applications' folder and underlying resources under 'Switchyard'. Instead some of the underlying resources become unavailable.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. Deploy a sample SOA quickstart SOAP application into JON.
2. Go to EAP under JBossAS7 Standalone Servers. Go to Inventory->Child Resources.
3. Select the war file and click on Delete.

Actual results:
Under 'Switchyard', 'Applications' folder and underlying resources can still be seen, though some of the underlying resources become unavailable.

Expected results:
The 'Applications' folder and underlying resources should be removed.

Additional info:
Comment 1 Libor Zoubek 2013-09-04 12:54:28 UTC 
This is not a plugin bug, but RHQ "feature". RHQ has does not have any reference between regular deployment and switchyard application, thatswhy it cannot know, what should be removed when deployment is removed. There is currently no simple way of soloving it in general.
Note You need to log in before you can comment on or make changes to this bug.