Bug 1035480

Summary:	Changing connection profile jar then reset CP on Model does not update the jar
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Van Halbert <vhalbert>
Component:	Tooling	Assignee:	belong
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	atangrin, vhalbert
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When using Teiid Designer, users are finding that changes to the list of driver JARs for a connection profile are not being displayed when the user goes to "View Connection Info" for the model. To workaround this issue, after making changes to the list of driver JARs, perform one of the following options: 1) Restart JBoss Developer Studio 2) Create a new connection profile	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-03 23:41:35 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:

Comment 1 JBoss JIRA Server 2013-12-02 16:31:15 UTC

Mark Drilling <mdrilling> made a comment on jira TEIIDDES-1960

This appears to be a bug with Eclipse Datatools.  I cannot find a way to code around the problem, so it will have to be a known issue for this release.

Problem:
Changing the jarList on a ConnectionProfile's driver does not update the connectionProfile jarList property until eclipse is restarted. 
If the user edits a ConnectionProfile and changes the profile's driver jars after it has been initially created, there are two options to workaround the issue:

1) Re-start JBDS / Designer
2) Create a different Connection Profile after changing the driver jarList

Comment 2 JBoss JIRA Server 2013-12-02 16:35:48 UTC

Mark Drilling <mdrilling> updated the status of jira TEIIDDES-1960 to Resolved

Comment 5 belong 2014-01-10 04:49:49 UTC

This is not flagged as a known issue in Release Notes, because it has been closed. It is flagged as an ongoing issue. Setting to requires_doc_text- accordingly.

Comment 6 JBoss JIRA Server 2014-05-07 21:15:02 UTC

Barry LaFond <blafond> updated the status of jira TEIIDDES-1960 to Closed