Humm, ok.
Seems that I'm in trouble now...
I need to figure out how to deal with duplicated components (and its
configuration objects) if we need to install more than one version
of same bundle in same container.
Target PIDs is the only way to deal with this usecase when using DS,
right ?
regards,
Cristiano
On 25-08-2014 11:49, BJ Hargrave wrote:
I don't believe it
does. Support for target
PIDs is not even in the DS spec yet. It will be added in the
next spec
release via RFC 190 [1].
[1] https://github.com/osgi/design/raw/master/rfcs/rfc0190/rfc-0190-Declarative_Services_Enhancements.pdf
--
From:
Cristiano Gavião
<cvgaviao@xxxxxxxxx>
To:
Equinox development
mailing list <equinox-dev@xxxxxxxxxxx>
Date:
2014/08/25 09:44
Subject:
[equinox-dev]
Declarative Service and support of TargetPID ?
Sent by:
equinox-dev-bounces@xxxxxxxxxxx
Hello,
I'm trying to create a Configuration using a targetPID as
defined in Configuration
Admin Service spec 1.5(cmpn.5.0).
I created a factory config using this targetPID:
servicefactory1|org.c4biz.utils.osgi.itests.samples.bundle|88.0.0
and CM seems have properly created the PID and
properties
are ok too:
servicefactory1|org.c4biz.utils.osgi.itests.samples.bundle|88.0.0-1408970963277-1
Even the configuration being properly created my
declarative
services based component (using configuration-policy = require)
are not
being activated with that configuration. but when I try with
'servicefactory1'
only it works as expected.
So, am I missing something or Equinox DS doesn't support
TargetPID yet
?
thanks,
Cristiano_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev
|