Hi, we already found some problems with checking for the PID in our code recently, but actually the problem is slightly worse.
Now, short story is : don't rely on the service PID. It's really an implementation detail and it's not guaranteed to exist. Unfortunately so far it worked for us as we're mostly using DS for our components with the maven-scr-plugin and that plugin has a bug from the first version on (FELIX-5304) which always adds a PID property to every component. However this property should never be set by the component, it's managed by DS and is only set if there is really a configuration used for the component. We really have to fix our code and get rid of most of the usage of PIDs Of course there are some valid cases but they are really rare. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
