[teiid-issues] [JBoss JIRA] (TEIID-4356) Add asort of connection test for "connection definitions" of resource adapters

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-4356:
----------------------------------
    Fix Version/s: 10.x
                       (was: 10.0)


> Add asort of connection test for "connection definitions" of resource adapters
> ------------------------------------------------------------------------------
>
>                 Key: TEIID-4356
>                 URL: https://issues.jboss.org/browse/TEIID-4356
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Misc. Connectors
>            Reporter: Marco Ardito
>            Priority: Minor
>             Fix For: 10.x
>
>
> Could a sort of "connection test" be implemented to verify if a "connection definition" specified for a resource adapter (eg: file, google, etc) is working, and can "connect" to the resource it's supposedly pointing to? 
> Data sources(jdbc) already have this kind of test, and it is quite useful to test if there's any error in their connection definition. 
> With resource adapters, one must define connection definitions, but it is not possible to test them, independently from later requests/queries (eg: reading data from .csv or .xls files, or oauth web services): one has to build all the chain and really try to get data from the source, using the vdb, hoping everything is correctly defined... 
> Recently I am struggling with a custom rest oauth2 RA, and I need to define
> - security domain (with client id/secret, tokens, auth uri)
> - RA using that domain
> - a connection definition for the RA accessing the remote data source
> - a VDB using the connection definition 
> - a client using the VDB to try get data in sql form
> any step could be wrong, but only the last allows to check if the whole chain is working, or not. 
> For any error or failure, regular users (like me) can't do anything else than double check everything... a "test connection" button, for the connection definition, would do wonders to simplify setup debug...
> Marco



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)