class) will not be instantiated.
Best regards,
Kai
From: equinox-dev-boun...@eclipse.org
[mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Sameera Jayasoma
Sent: Montag, 4. Mai 2009 04:59
To: Equinox development mailing list
Subject: Re: [equinox-dev] policy=dynamic in Declarative
,
Kai
From: equinox-dev-boun...@eclipse.org
[mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Sameera
Jayasoma
Sent: Montag, 4. Mai 2009 04:59
To: Equinox development mailing list
Subject: Re: [equinox-dev] policy=dynamic in Declarative Services.
Hi,
On Mon, May 4, 2009 at 8:23 AM
] policy=dynamic in Declarative Services.
Hi,
On Mon, May 4, 2009 at 8:23 AM, BlueDavy Lin blued...@gmail.com wrote:
if u want to the component isn't deactivated,u should set the bound
service cardinality to 0..1
Thanks for the quick reply. But my requirement is that the service should
list
Subject: Re: [equinox-dev] policy=dynamic in Declarative Services.
Well, Spring/DM will still work. The issue will be when he tries to
actually send a message to the service, in which case it will throw a
runtime exception.
On May 4, 2009, at 7:31 AM, BJ Hargrave wrote:
This does
:24
Subject:Re: [equinox-dev] policy=dynamic in Declarative Services.
Sent by:equinox-dev-boun...@eclipse.org
There's also Spring/DM, which does I think what you want - i.e. 1..1
cardinality, but not dropping the service is its dependencies
momentarily flicker.
On May 4, 2009
From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org
] On Behalf Of Hal Hildebrand
Sent: Montag, 4. Mai 2009 16:53
To: Equinox development mailing list
Subject: Re: [equinox-dev] policy=dynamic in Declarative Services.
Well, Spring/DM will still work. The issue
list
Subject: Re: [equinox-dev] policy=dynamic in Declarative Services.
Hi,
On Mon, May 4, 2009 at 8:23 AM, BlueDavy Lin blued...@gmail.com wrote:
if u want to the component isn't deactivated,u should set the bound
service cardinality to 0..1
Thanks for the quick reply. But my requirement
Jayasoma
*Sent:* Montag, 4. Mai 2009 04:59
*To:* Equinox development mailing list
*Subject:* Re: [equinox-dev] policy=dynamic in Declarative Services.
Hi,
On Mon, May 4, 2009 at 8:23 AM, BlueDavy Lin blued...@gmail.com wrote:
if u want to the component isn't deactivated,u should set the bound
To:
Equinox development mailing list equinox-dev@eclipse.org
Date:
2009/05/04 10:24
Subject:
Re: [equinox-dev] policy=dynamic in Declarative Services.
Sent by:
equinox-dev-boun...@eclipse.org
There's also Spring/DM, which does I think what you want - i.e. 1..1
cardinality, but not dropping the service
Of *Hal Hildebrand
*Sent:* Montag, 4. Mai 2009 16:53
*To:* Equinox development mailing list
*Subject:* Re: [equinox-dev] policy=dynamic in Declarative Services.
Well, Spring/DM will still work. The issue will be when he tries to
actually send a message to the service, in which case it will throw
Hi devs,
Even though I have used the value dynamic for the policy attribute in
the reference element, the component is deactivated once the bound service
is unregistered. Here is the component.xml I am using.
components xmlns:scr=http://www.osgi.org/xmlns/scr/v1.0.0;
scr:component
if u want to the component isn't deactivated,u should set the bound
service cardinality to 0..1
2009/5/4 Sameera Jayasoma sameera.madus...@gmail.com:
Hi devs,
Even though I have used the value dynamic for the policy attribute in
the reference element, the component is deactivated once the
12 matches
Mail list logo
