The map file has been updated for the following Bug changes:
+ Bug 274156. Add x86_64 to osgi test bundles (FIXED)
The following projects have changed:
org.eclipse.osgi.tests
Tom
___
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.
Thanks guys for your feedback. I really understands the problem here now.
Thanks
Sameera
On Mon, May 4, 2009 at 8:28 PM, Hal Hildebrand wrote:
> Yes, I see the point. He wants the service to become available before the
> dependency arrives.
> Sry for the confusion.
>
> On May 4, 2009, at 7:55 A
This does not sound like a "flicker" problem. DS can handle that also for
a dynamic 1..1 reference. The new service would be passed to bind before
the old service is passed to unbind. So the component is never without a
dependent service.
I think the issue here is that there is no replacement s
Yes, I see the point. He wants the service to become available before
the dependency arrives.
Sry for the confusion.
On May 4, 2009, at 7:55 AM, Toedter, Kai wrote:
@Hal, but DM will always create the service component eagerly since
it does not support lazy instantiation, right?
Kai
Fro
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 not sound like a "flicker" problem. DS can handle that
also for a dynamic 1
@Hal, but DM will always create the service component eagerly since it
does not support lazy instantiation, right?
Kai
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 l
You cannot directly do this, because mandatory reference is mandatory
at all times. However, you could make the reference optional and
perform some kind of internal activation/deactivation in the
bind/unbind methods.
However, if that still doesn't work for you then you're trying to do
something ou
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, at 6:53 AM, Neil Bartlett wrote:
You cannot directly do this, because mandatory reference is mandatory
at all times. Howeve
>From equinox realization,I think no way to do this.
Because equinox use reference policy & cardinality & interface etc. to
decide the component satisfication condition,if component become
unsatisfied,then equinox ds will dispose the component instance,and if
component become satisfied,equinox ds
Hi Kai,
On Mon, May 4, 2009 at 11:55 AM, Toedter, Kai wrote:
> HI Sameera,
>
>
>
> I think Equinox’ behavior is correct here. If you have a mandatory service
> reference that is not valid anymore, the referring component has to be
> deactivated even if the policy is dynamic.
>
I agree with you
10 matches
Mail list logo
