Bug 1108578 - ModeShape Tool doesn't unpublish teiid models
Summary: ModeShape Tool doesn't unpublish teiid models
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: ModeShape, Tooling
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Van Halbert
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-12 09:30 UTC by Andrej Podhradsky
Modified: 2014-07-21 15:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-12 13:51:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker MODETOOLS-77 0 Major Resolved ModeShape Tool doesn't unpublish teiid models 2014-07-21 15:44:30 UTC

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!


Note You need to log in before you can comment on or make changes to this bug.