[SLING-6110] ServerSideTeleporter can't read the bundle header Sling-Test-WaitForService-Timeout

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JUnit Tests Teleporter 1.0.8, JUnit Core 1.0.18
• Fix Version/s: JUnit Core 1.0.20
• Component/s: Testing
• Assignee: Stefan Seifert
• Reporter: Marcel Jolk
• Created: 07/Oct/16 08:56
• Updated: 19/Dec/16 13:46
• Resolved: 07/Oct/16 11:40

Description

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.

Issue Links

• relates to: SLING-6031 Teleporter.getService() should wait for required services
• links to: GitHub Pull Request #178