[
https://jira.jboss.org/jira/browse/TEIID-505?page=com.atlassian.jira.plug...
]
Ramesh Reddy resolved TEIID-505.
--------------------------------
Resolution: Done
https://jira.jboss.org/jira/browse/TEIIDDES-147 added the native vendor drivers to the
Designer code, and parsing of the URL during the Connector connection is removed from the
code. The addition of the Data Direct drivers to the product will be handled by product
(JBEDSP-1023).
Do not parse the URL, when creating a Data Source or XA DataSource
------------------------------------------------------------------
Key: TEIID-505
URL:
https://jira.jboss.org/jira/browse/TEIID-505
Project: Teiid
Issue Type: Task
Affects Versions: 6.0.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.1.0
Previously Teiid always dependent upon the Data Direct drivers, which were provided in a
unified URL across all the RDBMS, so that Teiid could parse the given URL and extract
serverName, databaseName, portNumber etc.
However, now in order to support with native vendor drivers this assumption is no longer
valid. Teiid can not assume the format of these URL, so there should be no attempt made to
parse these URLs to extract above properties, rather if the URL specified it should be
supplied to the Data Source as like any other property. This requires code change.
- All the Data Direct XA Connector Types needs to be modified, so that do not depend on
the URL property alone
- All vendor XA data sources need to be checked to make sure they all work.
--
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