[
https://issues.apache.org/jira/browse/FELIX-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167396#comment-15167396
]
Richard S. Hall commented on FELIX-5198:
----------------------------------------
Of course it will trigger it.
The issue was people wanted one last chance to talk to the service before it
was gone. My position at the time was, "What's the point, the service probably
isn't working anyway." Their position was, "Well, for my components I know they
are working."
It is legitimate that there is no chance to say goodbye unless we allow
retrieval, but whether or not this is useful is totally dependent on the
service implementation.
I can pretty much guarantee that you will cause some people pain if you do
this, but I'm not against it.
> Service should not be available while being unregistered
> --------------------------------------------------------
>
> Key: FELIX-5198
> URL: https://issues.apache.org/jira/browse/FELIX-5198
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: framework-5.4.0
> Reporter: Carsten Ziegeler
> Assignee: David Bosschaert
> Fix For: framework-5.6.0
>
> Attachments: felix-5198.patch
>
>
> Currently it is possible to get a service while it is being unregistered -
> if the service is get during processing of the unregistering event. This is
> the order of events:
> a) a service (factory) is unregistered in the framework
> b) the UNREGISTERING event is sent before the service is actually
> unregistered (this is as defined in the spec)
> c) the above event is handled synchronously, reactivating dependent components
> d) during this reactivation, some component looks up the service that is
> unregistered in a). as this service is still registered and marked as valid,
> it gets it
> According to ServiceRegistration.unregister the service should not be
> available anymore while the events are sent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
