[teiid-issues] [JBoss JIRA] Created: (TEIID-640) DriverManager usage introduces classloading issues

[Steven Hawkins (JIRA)]

DriverManager usage introduces classloading issues
--------------------------------------------------

                 Key: TEIID-640
                 URL: https://jira.jboss.org/jira/browse/TEIID-640
             Project: Teiid
          Issue Type: Bug
          Components: Embedded
    Affects Versions: 6.0.0
            Reporter: Steven Hawkins
            Assignee: Steven Hawkins
            Priority: Critical
             Fix For: 6.1.0


When using Teiid through the DriverManager - but without the jar in the app classloader (such as is the case with DTP/Hibernate tools) we run into classloading issues.

There are two fixes needed.

1. The EmbeddedDriver creation of the post delegating class loader should use it's classloader rather than context class loader as the parent.  Then there is a consistent classloader for the classes coming from the client jar.

2. The LocalConnectionFactory needs to set the context classloader so that we don't inadvertently use the apps context classloader in our services (such as the transaction service).

-- 
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