Bug 1261514 - Save As Model and Rename Model actions allow duplicities
Summary: Save As Model and Rename Model actions allow duplicities
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Tooling
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Barry LaFond
QA Contact: Matus Makovy
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-09 13:57 UTC by skaleta
Modified: 2015-11-17 18:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-17 18:07:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIIDDES-2642 0 Optional Closed Save As Model and Rename Model actions allow duplicities 2015-11-18 06:58:58 UTC

Description skaleta 2015-09-09 13:57:07 UTC
Description:
I assume that it is not correct to have two models with same name in the project (e.g. designer doesn't let you to create new model (or copy) with name which is already used within the project), but it is possible to achieve it using Save As/Rename (see steps to reproduce).

Additionally, it is possible to add these different models with same name to Teiid VDB, which causes exceptions on deployment.

Steps to Reproduce:
1. double-click model
2. File -> Save as...
3. keep same name of model and for location choose different folder in same project
4. click OK
5. two models with same name will be present in the project

1. right-click the model and select Refactor > Rename...
2. set name equal to name of existing model located in different folder of project
3. two models with same name will be present in the project

Comment 1 JBoss JIRA Server 2015-09-11 14:13:26 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-2642 to Resolved

Comment 2 JBoss JIRA Server 2015-10-01 13:07:21 UTC
Matus Makovy <mmakovy> updated the status of jira TEIIDDES-2642 to Closed


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