My guess is the current code makes it easier to deal with cases where the
service properties no longer match the specific target filter for the
reference. There was a new event added to org.osgi.framework package
version 1.5 that was supposed to help deal with this:
[
https://issues.apache.org/jira/browse/FELIX-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Watson resolved FELIX-6140.
--
Resolution: Fixed
Assignee: Thomas Watson
> possible deadlock in
[
https://issues.apache.org/jira/browse/FELIX-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnoud Glimmerveen updated FELIX-6161:
--
Attachment: FELIX-6161.patch
> SCR: Method of resolving references limits Service
[
https://issues.apache.org/jira/browse/FELIX-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885627#comment-16885627
]
Arnoud Glimmerveen commented on FELIX-6161:
---
I have made an attempt to address the observed
I have attached a.patch to issue FELIX-6161 that solves the issue in my case,
and hopefully does not break the use case [1] that prompted David to implement
the ServiceListener in the way it was implemented.
Any feedback on and testing of the patch is very much appreciated!
Arnoud.
[1]
[
https://issues.apache.org/jira/browse/FELIX-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885636#comment-16885636
]
David Jencks commented on FELIX-6161:
-
Looking briefly at your patch from the point of view of
[
https://issues.apache.org/jira/browse/FELIX-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16885864#comment-16885864
]
Arnoud Glimmerveen commented on FELIX-6161:
---
Based on the example outlined in FELIX-4964:
bq.
