[
https://jira.jboss.org/jira/browse/TEIIDDES-161?page=com.atlassian.jira.p...
]
Barry LaFond resolved TEIIDDES-161.
-----------------------------------
Resolution: Done
Removed logic in ConfigurationManagerImpl.removeBinding(ConnectorBinding binding) that
deleted unused jars. Reviewed by Dan.
Importing Connector (.cdk) with over existing connector deletes
driver jar
--------------------------------------------------------------------------
Key: TEIIDDES-161
URL:
https://jira.jboss.org/jira/browse/TEIIDDES-161
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 6.0.0
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Critical
Fix For: 6.0.0
In new workspace....
1) Import Model from JDBC (connector is created and bound to source)
2) Preview table and see data
3) Select new connector in Connectors View and "Export Connector" to file
system
4) Import that same connector back into Designer
5) Results in deleted jar
6) Preview fails
This is because when replacing a connector (overwriting) we first "Delete" the
connector and auto-delete unused connector jars. In this case the "Importer"
indicated the jar already existed and would not be imported. But it was too late, the next
step in the process deleted the jar that was supposed to remain.
Fix is to change our philosophy and NOT auto-delete jars when they are NOT used.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira