[
https://issues.apache.org/jira/browse/SLING-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248150#comment-14248150
]
Stefan Seifert commented on SLING-4249:
---------------------------------------
yes, this is correct. seems to applied to all REST actions. this delay is
hard-coded.
is this enough for refreshPackages for all bundles to complete? perhaps it's
faster to do it only on the newly installed packages, thus picking up your
proposal to pass it together with the install action. this is not 100% clean
either, but we can apply it and see how well it is working.
this 800ms delay is since 2010 in the felix webconsole code, so it seem to be a
value that is working for most (rev. 933542).
> Testing Tools: Refresh Packages should be called after installing or
> uninstalling bundles
> -----------------------------------------------------------------------------------------
>
> Key: SLING-4249
> URL: https://issues.apache.org/jira/browse/SLING-4249
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: org.apache.sling.testing.tools 1.0.8
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Fix For: org.apache.sling.testing.tools 1.0.10
>
>
> for integration tests additional bundles can be installed using the
> WebconsoleClient in sling testing tools project. if bundles already exists
> they are uninstalled before new bundles are installed.
> but in this case it may happen that depending are still wired to the old
> uninstalled bundle. thus always a "refreshPackages" command should be called
> when all bundles are installed/uninstalled.
> see also
> http://felix.apache.org/documentation/tutorials-examples-and-presentations/apache-felix-osgi-faq.html#when-i-update-my-bundle-why-are-my-bundles-old-classes-still-being-used
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
