Bug 1035019 - Creating a VDB with XML document model results in error
Summary: Creating a VDB with XML document model results in error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Tooling
Version: 6.0.0
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ER1
: 6.1.0
Assignee: Van Halbert
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-26 21:01 UTC by rareddy
Modified: 2015-11-17 18:07 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-17 18:07:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIIDDES-1945 0 Major Closed Unable to deploy and test a VDB with same name models with different extensions 2014-07-21 16:29:48 UTC

Description rareddy 2013-11-26 21:01:43 UTC

Comment 2 JBoss JIRA Server 2013-11-27 13:52:44 UTC
Barry LaFond <blafond> made a comment on jira TEIIDDES-1945

The Project set contains Employees.xsd and Employees.xmi models.

The vdb.xml model elements strip off the file extension, so it tries to create 2 models with identical *Employees" names and it fails.

Comment 3 JBoss JIRA Server 2013-11-27 13:56:18 UTC
Ramesh Reddy <rareddy> made a comment on jira TEIIDDES-1945

I do not know of any stripping of the extensions, that may exist inside the Designer code. However that reduces the severity of this defect.

Comment 4 JBoss JIRA Server 2013-11-27 14:11:23 UTC
Barry LaFond <blafond> made a comment on jira TEIIDDES-1945

Since we went to the new vdb.xml manifest, it's been assumed that the model *name" represents a "schema" and the file extensions are stripped off the file names and the "type" value is used to distinguish the model type.

Guess all we need to know is can the vdb.xml accept "Employees.xmi" as a valid model *name" value?

Comment 5 JBoss JIRA Server 2013-11-27 14:43:51 UTC
Ramesh Reddy <rareddy> made a comment on jira TEIIDDES-1945

No, I would put in a validation rule that two model names can not be same

Comment 7 JBoss JIRA Server 2014-02-06 20:28:03 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1945 to Resolved

Comment 8 JBoss JIRA Server 2014-04-07 14:54:58 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1945 to Reopened

Comment 9 JBoss JIRA Server 2014-04-07 14:56:26 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1945 to Resolved

Comment 10 JBoss JIRA Server 2014-05-07 21:06:13 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1945 to Closed

Comment 11 JBoss JIRA Server 2014-05-27 13:55:44 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1945 to Reopened

Comment 12 JBoss JIRA Server 2014-05-27 13:56:20 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1945 to Resolved

Comment 13 JBoss JIRA Server 2014-06-10 16:31:27 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1945 to Reopened

Comment 14 JBoss JIRA Server 2014-06-18 18:45:02 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1945 to Resolved

Comment 15 JBoss JIRA Server 2014-06-20 12:14:31 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-1945 to Closed


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