Hi Phil,
seems to work now, at least I can see no exceptions anymore. Thanks to the team for the quick fix, Christian ________________________________ Von: P. Ottlinger <pottlin...@apache.org> Gesendet: Montag, 11. Februar 2019 20:23:14 An: dev@tamaya.incubator.apache.org; Niehues, Christian Betreff: Re: Problem with ServiceContext Hi Christian, can you recheck * https://github.com/apache/incubator-tamaya/pull/41 - https://issues.apache.org/jira/browse/TAMAYA-381 * https://github.com/apache/incubator-tamaya/pull/42 - https://issues.apache.org/jira/browse/TAMAYA-383 as all of the PRs were merged now. Thanks for your feedback and patience :-) Phil Am 05.02.19 um 08:31 schrieb Niehues, Christian: > Any feedback on this or should I just create a JIRA ticket for it? > > > Cheers > > Christian > > > ________________________________ > Von: Niehues, Christian > Gesendet: Donnerstag, 22. November 2018 13:34:43 > An: dev@tamaya.incubator.apache.org > Betreff: Problem with ServiceContext > > Hi, > > after a longer period I updated my tamaya sources from master and deployed > them into my existing karaf project. After that the core tamaya-core bundle > fails to start the OSGIActivator because of ConfigException "No > ServiceContext found". > The exception comes from ServiceContextManager::loadDefaultServiceProvider > which always try to get a new(best) Service Provider instead of using the one > got from ServiceContextManager::set method like in older implementations. The > problem is that ServiceLoader.load(ServiceContext.class, classLoader) doesn't > find anything and I ask myself if it shouldn't be a OSGIServiceLoader do find > the service declaration. > > So am I doing anything wrong or are there open issues around that? > > Cheers > Christian >
