[
https://issues.apache.org/jira/browse/SLING-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248131#comment-14248131
]
Konrad Windszus commented on SLING-4249:
----------------------------------------
You could actually issue refreshPackages on the server side before the JUnit
Test is executed. Probably it is a good idea to parameterize that (so one could
prevent refreshPackages from happening).
> 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)
