[
https://jira.jboss.org/browse/TEIID-1080?page=com.atlassian.jira.plugin.s...
]
Ramesh Reddy resolved TEIID-1080.
---------------------------------
Resolution: Done
Added the following methods and their implementations to the Admin API
createDataSource - Creates a JDBC local, xa or any JCA based data source
deleteDataSource - Deletes a data source given its deployed name
getDataSourceNames - Provides list a data sources available in the configuration
getDataSourceTemplateNames - Provides template names (a template defines the properties)
for data sources
Also, changed the following method names to better suit the functionality or add more
capabilities
addTranslator --> createTranslator
getTranslatorTemplatePropertyDefinitions --> getTemplatePropertyDefinitions (so that
this can be used to get property definitions for translators and data sources)
Change Admin API, to support the Translation Layer and Connection
layer concepts.
---------------------------------------------------------------------------------
Key: TEIID-1080
URL:
https://jira.jboss.org/browse/TEIID-1080
Project: Teiid
Issue Type: Sub-task
Components: AdminApi
Affects Versions: 7.0
Environment: 7.0 M3
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.0
Now that we have two separate layers to define a connector the Admin API must be modified
to aid in managing the lifecycle of the Translation Layer and Connection Layer. Some
obvious methods will be
- addTranslator(name, properties)
- deleteTranslator(name)
will keep the current data source methods for the connection. The previous names with
"Connection Factory" will be removed/renamed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira