On Thu, Sep 29, 2016 at 2:34 AM, David Jencks
wrote:
> Neither this nor restarting the framework should cause problems.
>
> Can you come up with a self contained demonstration of this (no components)
> behavior? I vaguely recall someone having a similar problem
Neither this nor restarting the framework should cause problems.
Can you come up with a self contained demonstration of this (no components)
behavior? I vaguely recall someone having a similar problem that I couldn’t
reproduce.
thanks
david jencks
> On Sep 28, 2016, at 8:50 AM, Benson
On Wed, Sep 28, 2016 at 11:50 AM, Benson Margulies wrote:
> On Wed, Sep 28, 2016 at 11:43 AM, David Jencks
> wrote:
>> It should work in any order.
The only other thing I can think of is this: in the application I'm
working with, the code
On Wed, Sep 28, 2016 at 11:43 AM, David Jencks
wrote:
> It should work in any order.
OK, then I've got some other problem on my hands. Does the last of
these three messages indicate a problem?
177 [FelixStartLevel] INFO org.apache.felix.scr.2.0.6 - Starting
It should work in any order.
david jencks
> On Sep 28, 2016, at 8:28 AM, Benson Margulies wrote:
>
> I'm trying to retrofit SCR/DS into a very dumb application that loads
> some bundles and starts the framework. Everything is at the same start
> level, and no @Components
I'm trying to retrofit SCR/DS into a very dumb application that loads
some bundles and starts the framework. Everything is at the same start
level, and no @Components are ever activated.
I have logging working; I see
191 [FelixStartLevel] INFO org.apache.felix.scr.2.0.6 - Starting
with
6 matches
Mail list logo