[
https://issues.apache.org/jira/browse/TUSCANY-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram closed TUSCANY-2081.
-----------------------------------
Resolution: Fixed
SCATestCaseRunner now uses TCCL rather than create a new classloader if the
test classloader is not an URL classloader, and is not the current TCCL. When
running under OSGi, TCCL is retained, and when not running under OSGi, a new
classloader is created and installed as the new TCCL as before.
> SCATestCaseRunner assumes test class is loaded by the context classloader
> -------------------------------------------------------------------------
>
> Key: TUSCANY-2081
> URL: https://issues.apache.org/jira/browse/TUSCANY-2081
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Embedded Runtime
> Affects Versions: Java-SCA-1.1
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Fix For: Java-SCA-1.2
>
>
> o.a.t.s.host.embedded.SCATestCaseRunner which is used in many samples creates
> a classloader based on the classloader of the test class and installs it as
> the thread context classloader. There is an implicit assumption here that 3rd
> party libraries which are required on the TCCL are accessible through the
> test classloader. This is not the case when Tuscany is running under OSGi
> since test bundles typically will not have access to the 3rd party
> implementation classes required on the TCCL. Tests using SCATestCaseRunner
> currently fail under OSGi as a result.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
