2009/3/8 Tatu Saloranta
> On Sat, Mar 7, 2009 at 5:17 PM, Stuart McCulloch
> wrote:
> > 2009/3/8 Tatu Saloranta
> >
> >> I am having a problem trying to build a bundle with Maven. Problem
> >> manifests when doing "mvn install" (or package) with following error
> >> message:
> ...
> >>
On Sat, Mar 7, 2009 at 5:17 PM, Stuart McCulloch wrote:
> 2009/3/8 Tatu Saloranta
>
>> I am having a problem trying to build a bundle with Maven. Problem
>> manifests when doing "mvn install" (or package) with following error
>> message:
...
>>
2009/3/8 Tatu Saloranta
> I am having a problem trying to build a bundle with Maven. Problem
> manifests when doing "mvn install" (or package) with following error
> message:
> ---
> [INFO]task-segment: [install]
> [INFO]
> -
I am having a problem trying to build a bundle with Maven. Problem
manifests when doing "mvn install" (or package) with following error
message:
---
[INFO]task-segment: [install]
[INFO]
[ERROR] BUILD ERROR
[INFO] -
This is exactly the case. Our Declarative Services implementation
maintains a single background thread which is responsible for binding
references and activating components.
So, yes, here you generally will not get a bind or unbind call while in
the activate method.
I chose this implementation to
Yes, sorry with "felix " I was actually meaning "Felix Declarative
Services".
Regards,
Reto
Richard S. Hall said the following on 03/07/2009 05:52 PM:
> I am not sure if this has anything to do with Felix per se, it sounds
> like more of a feature of the SCR implementation. Perhaps SCR queues
> i
I am not sure if this has anything to do with Felix per se, it sounds
like more of a feature of the SCR implementation. Perhaps SCR queues its
work, in which case, the activate would be processed before the bind.
-> richard
On 3/7/09 9:35 AM, Reto Bachmann-Gmür wrote:
experimenting with felix
But as in the scenario of the experiment felix is actually waiting with
enabling (and injecting) the second component till the first one (the
one with the Thread.sleep) finished activating. Why does felix wait half
a minute if not forced by specification?
Regards,
reto
Neil Bartlett said the fol
Indeed, this is NOT guaranteed.
What you will find in small-scale testing is that it's actually quite
hard to force the concurrency to happen, because you can't get the
thread scheduler to switch contexts when you want it to. But the bugs
are only hiding, and are likely to appear when the componen
experimenting with felix I found that dynamic dependencies are not
injected while the acivate method is being executed.
The experiment code
/**
* @scr.component
* @scr.reference name="component" cardinality="0..n" policy="dynamic"
*interface="java.lang.Object" target="(testing=
10 matches
Mail list logo
