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
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
--
BJ Hargrave
Senior Technical Staff Member,
I do not think the Equinox DS implementation correctly supports targeted
pids (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=410361)
Tom
From: Cristiano Gavião cvgav...@gmail.com
To: Equinox development mailing list equinox-dev@eclipse.org
Date: 08/25/2014 08:44 AM
Subject:
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 ?
Thanks Tom...
One doubt. I could see the package org.apache.felix.scr on the
org.eclipse.equinox.ds bundle. what is the relation of the felix
implementation with the equinox one?
regards,
Cristiano
On 25-08-2014 11:52, Thomas Watson wrote:
I do not think the Equinox DS implementation
We just share the same felix scr package for interrogating the DS runtime.
There was no spec'ed way to do this and we did not want to re-invent
something felix had already designed a solution for. In the future R6
specification there is going to be standard DTOs for DS that can be used
