[
https://issues.apache.org/jira/browse/SLING-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JBodkin reopened SLING-4026:
----------------------------
I've noticed that even if you use a target filter with declarative services, if
you update the version and deploy the bundle, the same race condition occurs.
Does the adapter get bound to the old version of the library which is no longer
available?
> Sling Models Race Condition
> ---------------------------
>
> Key: SLING-4026
> URL: https://issues.apache.org/jira/browse/SLING-4026
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Sling Models Implementation 1.1.0
> Reporter: JBodkin
> Labels: models
>
> During initialization of a bundle, it is possible to encounter a race
> condition in which the BundleTrackerCustomizer::addingBundle(Bundle bundle,
> BundleEvent event) is triggered after the bundle has begun initialization of
> a immediate component.
> {code:java}
> @Component(immediate = true)
> @Service
> public class ExampleImpl {
> @Activate
> public void activate(ComponentContext context) {
> Resource resource = ....
> // Race condition possible here... Could be executed before the
> BundleTracker (ModelPackageBundleListener)
> SlingModelExample example = resource.adaptTo(SlingModelExample);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
