felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Closed: (FELIX-354) Service.PID not always available in properties
Date Tue, 18 Sep 2007 09:24:44 GMT

     [ https://issues.apache.org/jira/browse/FELIX-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Felix Meschberger closed FELIX-354.
-----------------------------------

    Resolution: Won't Fix

It has been argued, that it is not the task of the SCR to ensure the service.pid property
being set. To still have the
service.pid at any point in time the Maven SCR plugin has been modified to ensure the service.pid
property is defined if not explicitly set.

Therefore, I close this issue as won't fix.

> Service.PID not always available in properties
> ----------------------------------------------
>
>                 Key: FELIX-354
>                 URL: https://issues.apache.org/jira/browse/FELIX-354
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services
>            Reporter: Carsten Ziegeler
>            Assignee: Felix Meschberger
>
> In some cases, the property Constants.SERVICE_PID is null for a service even if it has
a configuration.
> Use case:
> Two services are registered through SCR, service A has a static reference to service
B.
> When the bind method in Service A is called with the ServiceReference to B, the SERVICE_PID
is null in the properties.
> Service B has a configuration and can be configured through the configuration admin (SERVICE_PID
is available there).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message