[teiid-issues] [JBoss JIRA] (TEIID-3193) Teiid not removing/setting the correct TCCL before calling getMetadata on translator

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016869#comment-13016869 ] 

Ramesh Reddy commented on TEIID-3193:
-------------------------------------

For metadata, handling in the NativeMetadataRepository should take care it. For capabilities, I am thinking of wrapping the capabilities call in ConnectorManager class.

Resource Adapter is loaded through JCA, since Teiid does not make any direct calls into this API (all through translator), I am thinking it should be OK, if we handle calls like "getConnection" and "close" in the Connector Manager. At worst it will have Translator's class loader as TCCL. Otherwise we would to handle them in each translator. (we could consider this)

I am drawing blank on Authorization, for JAAS we do not have direct access to the LoginModule, but I could set TCCL to null before SessionManager's call to Login method?

> Teiid not removing/setting the correct TCCL before calling getMetadata on translator
> ------------------------------------------------------------------------------------
>
>                 Key: TEIID-3193
>                 URL: https://issues.jboss.org/browse/TEIID-3193
>             Project: Teiid
>          Issue Type: Bug
>          Components: Common
>    Affects Versions: 8.8
>            Reporter: Michael Farwell
>            Assignee: Ramesh Reddy
>             Fix For: 8.9
>
>
> Ramesh helped me debug a class loading issue that I'm experiencing with a custom translator and asked me to open this ticket based on his findings.  The forum link is specified below and contains all of the necessary information.  
> Ramesh's words: "OK, I believe the geoTools is using the TCCL to load the schema, thus the error. However, the error is on the Teiid side not correctly removing/setting the correct TCCL before we call "getMetadata" call on the translator. You can add JIRA for this we will fix it."



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)