[
https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152159#comment-15152159
]
ASF subversion and git services commented on KARAF-4344:
--------------------------------------------------------
Commit 18e8b297d19f1da0ff399576b9e86561aa61d88a in karaf-decanter's branch
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=18e8b29 ]
[KARAF-4344] Migrating to DS
> Migrate decanter to DS
> ----------------------
>
> Key: KARAF-4344
> URL: https://issues.apache.org/jira/browse/KARAF-4344
> Project: Karaf
> Issue Type: Improvement
> Components: decanter
> Affects Versions: decanter-1.0.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: decanter-1.1.0
>
>
> Currently we are using osgi APIs to bind services and configuration.
> This is becoming increasingly complicated and error prone.
> For example for some of the decanter components we need two services and
> multiple configurations (ManagedServiceFactory). This results in two stacked
> service trackers and a ManagedServiceFactoryImpl. It is difficult to make
> sure this code works correctly in all circumstances.
> So I plan to switch to declarative services where all of the above can be
> controlled by annoations. Additionally we can use the new type safe
> configurations that make it a lot easier to work with the configuration both
> as a user and as a developer of a component.
> One important question is the minimum environment we want to support with
> decanter 1.1.0. Older karaf versions do not support scr 2 (and DS spec 1.3)
> which is needed for some interesting DS features like field injection and
> type safe configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
