You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/11/18 21:21:01 UTC
[jira] [Commented] (TAMAYA-353) Improve support for different
classloaders
[ https://issues.apache.org/jira/browse/TAMAYA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691050#comment-16691050 ]
ASF subversion and git services commented on TAMAYA-353:
--------------------------------------------------------
Commit 36c32fcf347ffffef5498ea177159be0387392e3 in incubator-tamaya-extensions's branch refs/heads/master from [~anatole]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=36c32fc ]
TAMAYA-274 Reduced API footprint by using Java 8 features. Added some lambdas.
TAMAYA-355 Enable mapping of lists and arrays into internal datastructures.
TAMAYA-353 Adding support for different classloaders.
> Improve support for different classloaders
> ------------------------------------------
>
> Key: TAMAYA-353
> URL: https://issues.apache.org/jira/browse/TAMAYA-353
> Project: Tamaya
> Issue Type: Improvement
> Components: API, Core
> Affects Versions: 0.3-incubating
> Reporter: Anatole Tresch
> Assignee: Anatole Tresch
> Priority: Critical
> Fix For: 0.4-incubating
>
>
> As of now now all components are loaded using a _ServiceContext_ abstraction. This has shown to be useful because it gives you an abstraction very useful in OSGI (works different) and testing (allows mocking). In the upcoming standard as well as in Microprofile different configurations that use different classloaders are suported explicitly, whereas in Tamaya this id done implicitly (if at all) using the _ServiceContext_. This improvement proposes the following:
> * Add the target _ClassLoader_ to the _ServiceContext_ (SPI extension)
> * Accessing a _ServiceContext_ from the _ServiceContextManager_ requires a _ClassLoader_ (SPI change)
> * The _ServiceContext_ is passed and used accordingly by subsequent components (SPI/API extension, examples: _PropertyConverterManager, PropertyFilterManager, ConfigurationContext_) and builders (_ConfigurationBuilder_, _ConfigurationContextBuilder_).
> Since this change partially breaks the SPI, we have to discuss, if we must do a major version upgrade.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)