Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 333996 - [osgi][remoteservice] service.pid is not set
Summary: [osgi][remoteservice] service.pid is not set
Status: CLOSED WONTFIX
Alias: None
Product: ECF
Classification: RT
Component: ecf.remoteservices (show other bugs)
Version: 3.4.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: ecf.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-11 11:06 EST by Martin Petzold CLA
Modified: 2011-01-11 11:34 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Petzold CLA 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 CLA 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 CLA 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.