Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333996

Summary:	[osgi][remoteservice] service.pid is not set
Product:	[RT] ECF	Reporter:	Martin Petzold <mpetzold>
Component:	ecf.remoteservices	Assignee:	ecf.core-inbox <ecf.core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	slewis
Version:	3.4.0
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Martin Petzold

2011-01-11 11:06:29 EST

Environment: JmDNS, r-OSGi

The OSGi RS specs 1.0 (cpm, page 8) define a service.pid for every service to be set.

Comment 1 Scott Lewis

2011-01-11 11:28:29 EST

(In reply to comment #0)
> Environment: JmDNS, r-OSGi
> 
> The OSGi RS specs 1.0 (cpm, page 8) define a service.pid for every service to
> be set.

My copy of the spec says:

Services that are exported should have a service.pid property

The use of 'should' indicates that a given provider doesn't have to set this id in order to be compliant.   Further, for some providers there is no such thing as a persistent identifier (persistent in the sense of lasting longer than the service registration itself)...which is (I think) why it says 'should' rather than 'must'.

Comment 2 Martin Petzold

2011-01-11 11:34:07 EST

(In reply to comment #1)
> (In reply to comment #0)
> > Environment: JmDNS, r-OSGi
> > [...]
> The use of 'should' indicates that a given provider doesn't have to set this id
> in order to be compliant.

Closed this Bug, service.pid is not necessary.