[ 
https://issues.apache.org/jira/browse/SLING-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcel Jolk resolved SLING-6110.
--------------------------------
    Resolution: Fixed

> ServerSideTeleporter can't read the bundle header 
> Sling-Test-WaitForService-Timeout
> -----------------------------------------------------------------------------------
>
>                 Key: SLING-6110
>                 URL: https://issues.apache.org/jira/browse/SLING-6110
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: JUnit Tests Teleporter 1.0.8, JUnit Core 1.0.18
>            Reporter: Marcel Jolk
>             Fix For: JUnit Core 1.0.20
>
>
> The _Sling-Test-WaitForService-Timeout_ bundle header is not properly read by 
> the {{ServerSideTeleporter}}. The method {{getService()}} reads the bundle 
> header using the {{BundleContext}} 
> ({{bundleContext.getBundle().getHeaders()}}). This {{BundleContext}} is set 
> in the {{Activator}} class on start of the bundle 
> {{org.apache.sling.junit.core}}. Therefore {{bundleContext.getBundle()}} 
> resolves to the bundle {{org.apache.sling.junit.core}}. This bundle does not 
> have the proper headers. Instead the bundle headers of the bundle, which is 
> created in the {{ClientSideTeleporter}}, including the class under test, 
> should be used. Thus its {{BundleContext}} is needed.
> I already made the required code changes using {{FrameWorkUtil}} to retrieve 
> the {{BundleContext}} for the class under test. I'll create a pull request, 
> which resolves this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to