Your quote is about what happens if a ManagedService or ManagedServiceFactory (or DS component etc) registers for configuration with a PID containing "|". Don't do it :-). Someone has to escape the "|" found in the actual PID.
I can't understand your example because I can't distinguish pipe from lowercase L. Could you specify the segments of the targeted PID separately? (and don't use confusing pids containing pipes) You can definitely use targeted pids to provide different configurations for the "same" PID consumer registered from different bundles, including different versions of the "same" (same symbolic name) bundles. Although formal support for this in DS is only in the next R6 spec, currently it works in felix DS. thanks david jencks On Jan 21, 2014, at 4:14 AM, bokie <[email protected]> wrote: > Hi David, > > Thanks for the pointer, bringing up the subject wasn't far fetched after > all. > > I'm not sure if I understand the following completly: > /If a registered target service has a PID that contains a vertical line (’|’ > \u007c) | then the value must > be taken as is and must not be interpreted as a targeted PID. > / > > Lets consider the following: > > > The way I understand it and for the bundle above, one proper way to interact > with the ConfigAdmin Service wouild be: > getConfiguration("a.b|c|bundle|A|1.0.0|file://bundle.a.jar", null) > > Is my assumption correct - I'll also try it later on? > > Thanks again. > > > > -- > View this message in context: > http://apache-felix.18485.x6.nabble.com/PID-and-symantic-versioning-tp5006869p5006886.html > Sent from the Apache Felix - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
