[
https://issues.apache.org/jira/browse/SLING-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873298#comment-13873298
]
Konrad Windszus commented on SLING-3320:
----------------------------------------
Probably one has to leverage the PolicyOption greedy (OSGi Compendium 4.3,
$112.3.5), otherwise it depends on the when a specific ValuesProvider becomes
available.
> Execution order of BindingsValuesProvider
> ------------------------------------------
>
> Key: SLING-3320
> URL: https://issues.apache.org/jira/browse/SLING-3320
> Project: Sling
> Issue Type: Bug
> Reporter: Feike Visser
>
> I have implemented two basic BindingsValuesProviders like this.
> {code}
> @Service
> @Component(immediate=true)
> public class MyBindings implements BindingsValuesProvider {
> }
> {code}
> What I want to make sure is that they are *always* executed in the same
> order, first A, then B.
> Because I want to re-use objects that were set in the first
> BindingsValuesProvider.
> Currently I don't have a way to do this.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
