Allow the CaffeineCachingProvider to be used with OSGi DS #447
Comments
raducotescu
added a commit
to raducotescu/caffeine
that referenced
this issue
Aug 18, 2020
…OSGi DS * annotated CaffeineCachingProvider to make it an OSGi service * when running in an OSGi container, set the CaffeineCachingProvider's classloader as the Thread context classloader for every API call on the provided CacheManagerImpl - this makes sure that the default config is read from the bundle; the default classloader will do a fallback to the app classloader, allowing to override / define configurations * added an OSGi DS test * made the bnd build reproducible (no extra bundle headers)
raducotescu
added a commit
to raducotescu/caffeine
that referenced
this issue
Aug 18, 2020
…OSGi DS * added Carsten Ziegeler's PGP key for Apache Felix
ben-manes
pushed a commit
that referenced
this issue
Aug 18, 2020
* annotated CaffeineCachingProvider to make it an OSGi service * when running in an OSGi container, set the CaffeineCachingProvider's classloader as the Thread context classloader for every API call on the provided CacheManagerImpl - this makes sure that the default config is read from the bundle; the default classloader will do a fallback to the app classloader, allowing to override / define configurations * added an OSGi DS test * made the bnd build reproducible (no extra bundle headers)
ben-manes
pushed a commit
that referenced
this issue
Aug 18, 2020
* added Carsten Ziegeler's PGP key for Apache Felix
|
Released in 2.8.6 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Although the
jcachemodule is an OSGi bundle, theCaffeineCachingProvidercan only be used directly, by tying the consumer to thecom.github.benmanes.caffeine.jcacheimplementation. If theCaffeineCachingProviderwould be an OSGiComponent, a consumer would only depend on thejavax.cacheAPI and theCaffeineCachingProviderwould be an opaque implementation.Ehcache has a similar approach for their JSR-107 implementation.
The text was updated successfully, but these errors were encountered: