[SLING-5724] Teleporter: Use o.a.s.testing.clients instead of custom HTTP requests in TeleporterHttpClient

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: JUnit Tests Teleporter 1.0.6
• Component/s: Testing
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 12/May/16 11:39
• Updated: 12/May/16 14:10

Description

Instead of having another client which deals with installing/uninstalling bundles, the ClientSideTeleporter should just leverage the class org.apache.sling.testing.clients.osgi.OsgiConsoleClient and org.apache.sling.testing.clients.osgi.WebconsoleClient for that purpose. That might also help with SLING-5715 as it is using the Apache HTTP Client under the hood, which might be a better choice than just plain HttpUrlConnections which are currently used by TeleporterHttpClient.

Issue Links

• depends upon: SLING-5703 Split sling-testing-tools and improve the http clients and junit tooling
• relates to: SLING-5715 Random NoRouteToHostException in Teleporter Client MultipartAdapter method
• relates to: SLING-5681 Teleporter: Improve mechanism to check if a deployed test bundle can be started