[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150161#comment-15150161 ] Jean-Baptiste Onofré commented on KARAF-4344: - +1 > 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150162#comment-15150162 ] Jean-Baptiste Onofré commented on KARAF-4344: - I think 1.1.0 can be Karaf 3.x or 4.x min and keep 1.0.x for "old" Karaf versions. > 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150530#comment-15150530 ] Christian Schneider commented on KARAF-4344: So we must only use DS 1.2 which then should run on all karaf versions. > 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150528#comment-15150528 ] ASF subversion and git services commented on KARAF-4344: Commit cc2d1a140519cff8362ca8d42e1c8ad0d8f5661b 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=cc2d1a1 ] [KARAF-4344] Migrate REST collector 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151887#comment-15151887 ] ASF subversion and git services commented on KARAF-4344: Commit 58766d5b5ad45dc2f7eab4c5877045c820e1ab00 in karaf-decanter's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=58766d5 ] KARAF-4344 - decanter-common feature now installs scr (required by decanter-collector-rest feature) in preparation for the switch 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151937#comment-15151937 ] ASF subversion and git services commented on KARAF-4344: Commit 64b9a1757a267413faaf9edc5a0d09c02be22c9f in karaf-decanter's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=64b9a17 ] KARAF-4344 - Use DS in marshaller > 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152160#comment-15152160 ] ASF subversion and git services commented on KARAF-4344: Commit 8c3e004aa16202dfeb9a1aa9ab17555b2ed574ec in karaf-decanter's branch refs/heads/DS-target from [~ch...@die-schneider.net] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=8c3e004 ] [KARAF-4344] Migrating to DS using target feature > 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152503#comment-15152503 ] ASF subversion and git services commented on KARAF-4344: Commit e5992a37fa38aefee19f26a8c573a1f222b2bf2c 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=e5992a3 ] [KARAF-4344] Migrating SLA components 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152506#comment-15152506 ] ASF subversion and git services commented on KARAF-4344: Commit e5992a37fa38aefee19f26a8c573a1f222b2bf2c in karaf-decanter's branch refs/heads/DS-target from [~ch...@die-schneider.net] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=e5992a3 ] [KARAF-4344] Migrating SLA components 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152507#comment-15152507 ] ASF subversion and git services commented on KARAF-4344: Commit 629395e787d8807162f9a74c0c560264787d47bd in karaf-decanter's branch refs/heads/DS-target from [~ch...@die-schneider.net] [ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=629395e ] [KARAF-4344] Migrating to DS using target feature > 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)
[jira] [Commented] (KARAF-4344) Migrate decanter to DS
[ https://issues.apache.org/jira/browse/KARAF-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158647#comment-15158647 ] ASF subversion and git services commented on KARAF-4344: Commit 31098cd7fc88ba2682e92c8315a08ca4213df862 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=31098cd ] [KARAF-4344] Migrating to DS using target feature > 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)
