commit | ceb848ab2b14b1422688218afa668b4b4742c857 | [log] [tgz] |
---|---|---|
author | William Lieurance <william.lieurance@namikoda.com> | Mon Feb 11 01:28:49 2019 -0600 |
committer | William Lieurance <william.lieurance@namikoda.com> | Mon Feb 11 01:28:49 2019 -0600 |
tree | 6ae591aea962d77f324ff3e4248950cc88e4d31f | |
parent | c1ab5ecd830dc5f6308061a0e5d0b9ff10116715 [diff] |
TAMAYA-383 Let OSGi skip thread classloader key We use the thread's classloader as a key into a hashmap to find the serviceloader for a given configuration. In OSGi, we have separate classloaders for the CoreConfigurationBuilder, DefaultConfigurationBuilder, and ServiceContextManager. That confusion prevents the simple case from finding a match in the hashmap that can load a particular ServiceContext. Since CoreConfiguation/DefaultConfiguration already uses the static class's classloader during <init>, this PR allows the OSGIActivator to point that classloader at the relevant OSGIServiceContext.
Tamaya is a very powerful yet flexible configuration solution. Its core is built based on a few simple concepts. There are at least two main usage scenarios for Tamaya, which are synergetic:
More information on Tamaya can be found on the homepage of Apache Tamaya.
The Apache Tamaya project is built with Maven 3 and Java 8, so you need JDK >=1.8 and a reasonable version of maven installed on your computer.
Then you can build Tamaya via:
$ export MAVEN_OPTS="-Xmx512m -XX:PermGenSpace=200m" $ mvn
Apart from integration into ASF CI there's a travis build: