Bug 1108578

Summary: ModeShape Tool doesn't unpublish teiid models
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Andrej Podhradsky <apodhrad>
Component: ModeShape, ToolingAssignee: Van Halbert <vhalbert>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: atangrin, rhauch
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-06-12 13:51:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrej Podhradsky 2014-06-12 09:30:21 UTC 
Description of problem:
After unpublishing teiid models the models still remain in xmi_model view

Version-Release number of selected component (if applicable):
JBDS 7.1.1.GA + JBDS-IS 7.0.2.CR1 + DV 6.0.0.GA

How reproducible:
always

Steps to Reproduce:
1. Publish teiid model
2. Check modeshape view xmi_model
3. Unpublish the teiid model
4. The model is still in xmi_model view

Actual results:
The model is still in xmi_model view

Expected results:
The model should be removed from xmi_model view
Comment 1 Randall Hauch 2014-06-12 13:29:01 UTC 
This is not a bug, but in fact the way it was intended to work. 

When a file is published, it is stored in the repository and asynchronously sequenced (if an appropriate file type that can be sequenced) and the resulting sequenced output is stored in the repository where it can be seen via queries. The sequenced file and the sequenced output are stored in separate locations. When the same file is then unpublished, only the file is removed from the repository; the content previously sequenced from that file is not automatically removed, but can be manually removed if desired.

While there are scenarios where the previously-sequenced content should be removed, there are also scenarios where the previously-sequenced content should not be removed. So our policy is that we don't **automatically** remove content.
Comment 2 JBoss JIRA Server 2014-06-12 13:50:38 UTC 
Andrej Podhradsky <apodhrad> updated the status of jira MODETOOLS-77 to Resolved
Comment 3 Andrej Podhradsky 2014-06-12 13:51:42 UTC 
Randall, thank you for the explanation!