[
https://issues.apache.org/jira/browse/FELIX-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-3200.
--------------------------------------
Resolution: Fixed
Fix Version/s: configadmin-1.4.0
Tracking these service.pid changes now by keeping record of service.pid value
after registration and after each registration modification. If a registration
modification causes no changes in the registered service PIDs (we ignore the
order of pids in the array for now) nothing happens. Otherwise the
ManagedService.update or ManagedServiceFactory.update method is called for each
of the new service pid values.
Implemented in Rev. 1197348
> Track PID changes of ManagedService[Factory] services
> -----------------------------------------------------
>
> Key: FELIX-3200
> URL: https://issues.apache.org/jira/browse/FELIX-3200
> Project: Felix
> Issue Type: Task
> Components: Configuration Admin
> Affects Versions: configadmin-1.2.8
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: configadmin-1.4.0
>
>
> Configuration Admin 1.4 requires implementations to track service.pid changes
> of registered ManagedService and ManagedServiceFactory services:
> > The Configuration Admin must track the configuration targets on their actual
> > PID. That is, if the service.pid service property is modied then the
> > Configuration Admin must treat it as if the service was unregistered and
> > then
> > re-registered with the new PID.
> This means we have to track service registration PIDs and compare them
> against any service registration changes and appropriately update the
> services.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
