regards,
Thomas
-- Originalnachricht --
Von: "Bruce Jackson"
An: "users@felix.apache.org"
Gesendet: 12.05.2017 09:05:34
Betreff: Lifecycle and Reference
>Hi Everyone
>
>I was wondering if
.org/appnotes/concurrency.html Subsection
> "Guarantees from DS"
>
> for a little more information on this.
>
> Kind regards,
> Thomas
>
> -- Originalnachricht --
> Von: "Bruce Jackson"
> An: &qu
t;bind methods are called.
>You can have a look at
>
>http://enroute.osgi.org/appnotes/concurrency.html Subsection
>"Guarantees from DS"
>
>for a little more information on this.
>
> Kind regards,
>Thomas
>
>-- Originalnach
this.
Kind regards,
Thomas
-- Originalnachricht --
Von: "Bruce Jackson"
An: "users@felix.apache.org"
Gesendet: 12.05.2017 09:05:34
Betreff: Lifecycle and Reference
>Hi Everyone
>
>I was wondering if anyone could provide some advice:
ml Subsection
"Guarantees from DS"
for a little more information on this.
Kind regards,
Thomas
-- Originalnachricht --
Von: "Bruce Jackson"
An: "users@felix.apache.org"
Gesendet: 12.05.2017 09:05:34
Betreff: Lifecycle and Reference
Hi Everyone
I was
Hi Bruce,
The behaviour you described is correct from a DS point of view. Dynamic
references can be bound at any time, from any thread before, during or after
activation. They can even be bound/unbound multiple times during activation.
Therefore you cannot rely on a dynamic reference from your
Hi Everyone
I was wondering if anyone could provide some advice:
I have a component of the form:
@Component(name="Bar")
public class MyComponent {
private MyServiceProcessor processor;
@Activate
public void activate(ComponentContext cc) {
processor = new MyServiceProcessor();
}
@Deactivate
7 matches
Mail list logo