TBH I'm not sure if we want this refresh per default since it could be
quite "costly" for bundles with lots of work todo. Nevertheless, an
optional parameter at the feature requesting a reload of hot-deployed
might be interesting; something like
...
Independently first of all it might be interest
Hi,
I just had a look at Christian Schneider's code that delays startup of
the console. It just periodically checks the list of installed bundles
and stops when it's startup is finished.
I don't think it can be reused for this purpose.
I think the real problem is that bundles with start-level 80
maybe there is some other way delay deploy folder loading till all
bundles are at least started? Since Christian is after something here
anyhow (he'll need something similar for his startup logic anyhow)
maybe we can reuse parts of this logic? Or is there something
completely different possibly her
Yes, that would be a problem, because fileinstall is the one that grabs all
the configuration from the etc/ directory and that needs to be done early
in the process.
On Wed, Jul 18, 2012 at 6:37 PM, Christoph Gritschenberger <
christoph.gritschenber...@gmail.com> wrote:
> Hi,
>
> We recently star
Hi,
We recently started using Weaving Hooks in our Project (running in
karaf-3.0.0-SNAPSHOT) and ran into a Problem:
When deploying a bundle using the deploy-directory the bundle might get
installed before the weaving hook is active. This causes the bundle to
remain unweaved.
We described the we
