You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2016/05/10 07:40:13 UTC

[jira] [Reopened] (SLING-5452) ClientSideTeleporter should check for web console readiness

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

Bertrand Delacretaz reopened SLING-5452:
----------------------------------------

Good point, I'm reopening this issue to implement this. I'm not sure if it's related to SLING-5715 but makes sense anyway.

> ClientSideTeleporter should check for web console readiness
> -----------------------------------------------------------
>
>                 Key: SLING-5452
>                 URL: https://issues.apache.org/jira/browse/SLING-5452
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: JUnit Tests Teleporter 1.0.6
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: JUnit Tests Teleporter 1.0.8
>
>
> Before installing its test bundle, the {{ClientSideTeleporter}} should (optionally?) check, via HTTP, that the OSGi console is ready to accept it. The customizer could optionally set a longer retry timeout for installing the bundle.
> This is not a problem in our launchpad test suite as the Sling readiness is checked extensively before starting tests, but in smaller test suites it's useful for the teleporter to be self-contained in this respect.



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