[
https://issues.apache.org/jira/browse/KARAF-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157201#comment-14157201
]
Andre Lanouette commented on KARAF-3258:
----------------------------------------
It looks like this new comportment comes from the refactoring of the
installFeatures function of FeatureServiceImpl.
Features are now started in separate thread by the doProvisionInThread method
at the end of the installFeatures function. Is this an expected comportment or
is this a potential regression?
> KarService returns immediately after Kar install
> ------------------------------------------------
>
> Key: KARAF-3258
> URL: https://issues.apache.org/jira/browse/KARAF-3258
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core, karaf-kar
> Affects Versions: 3.0.2
> Reporter: Andre Lanouette
> Priority: Blocker
>
> In Karaf 3.0.x (up to 3.0.1), when deploying a KAR archive programatically
> using the KarService.install(URI) method , the KAR archive would get
> installed, its features would get started, and only then the method would
> return. This can be very useful when we want to control precisely a
> particular sequence of kar and service start and registration.
> With the current version of Karaf-3.0.2-SNAPSHOT, the KarService return right
> after the installation of the kar archive. Features do not get started before
> the method returns.
> This currently breaks our production build and tests because our plugin load
> order sequence cannot be guaranteed anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
