Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1260690

Summary:	Copying Model to another Project
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	skaleta <skaleta>
Component:	Tooling	Assignee:	Barry LaFond <blafond>
Status:	CLOSED DEFERRED	QA Contact:	Matus Makovy <mmakovy>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	atangrin, blafond, vhalbert
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:	2016-02-05 10:30:58 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 skaleta 2015-09-07 13:03:39 UTC

Description:
Is it OK, if its possible to create (source, view) model by copying from model in different project? 
I think it does not make sense to copy view model from one project to another.

Steps to Reproduce:
1. right-click on a project and select New > Teiid Metadata Model
2. select Module Builder: Copy from existing model of the same model class (rest is optional) and click Next >
3. browse for models and select a model that is not in right-clicked project
4. new model will be created in right-clicked project

Comment 1 Van Halbert 2015-09-07 13:21:11 UTC

It makes sense in the use case of top-down modeling.   The user is designer their abstraction layer first.   And then will work down to map the views to underlying layers (i.e., Object Layer) or to the actual source model.

Comment 2 Matus Makovy 2015-09-07 13:31:56 UTC

OK, but when you copy a view model that references some source model, TD should at least warn you that the resulting view model will be broken, in my opinion. (or copy referenced source model also)

Comment 3 Barry LaFond 2015-09-10 18:59:51 UTC

Pushing to DV 6.3 Tooling release

Comment 4 Matus Makovy 2016-02-05 10:30:58 UTC

Closing this since we are tracking issues for tooling only in JIRA from now on.