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

Bug 1199401

Summary:	Set connection profile action uses wrong driver info.
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Juraj Duráni <jdurani>
Component:	Tooling	Assignee:	Barry LaFond <blafond>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	atangrin, dlesage, mmakovy, vhalbert
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	If a new connection profile is imported and its driver is changed afterward, the Set Connection Profile action will use the wrong driver information.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-05 09:07:09 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 Juraj Duráni 2015-03-06 06:55:37 UTC

Description:
If a new connection profile is imported (Database Development > Data Source explorer > Import) and its driver is changed afterward (jar list), then Set Connection Profile action sets connection profile to a source model with old jar-list-paths.

Steps to reproduce:
Import a new connection profile and change jar list
 - select Database Development perspective > Data Source Explorer > Import
 - right click to new profile > properties
 - click "Edit Driver Definition"
 - select JAR list and change the path

Set connection profile
 - create a new Teiid Model Project
 - create a new Teiid Metadata Model
 - select Relational and Source Model
 - right click to the new source model and select Modeling > Set Connection Profile (select newly created connection profile)

Check the driver info
 - right click to the source model
 - select Modeling > View Connection Profile Info
 - the jarList property contains old JAR path

Comment 1 Barry LaFond 2015-03-25 20:48:00 UTC

After investigation in Designer, it seems it's more likely a Data Tools issue.

So recommending keeping as a known issue for now.

Comment 2 Matus Makovy 2016-02-05 09:07:09 UTC

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