[
https://issues.apache.org/jira/browse/TIKA-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072319#comment-18072319
]
Hudson commented on TIKA-4700:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk17 #1299 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1299/])
TIKA-4700 -- this adds a few more components to the activator and service
loader for osgi. (#2751) (github:
[https://github.com/apache/tika/commit/9b211c5e110782357e5b0b84ceda274c7e1919ac])
* (edit) tika-core/src/main/java/org/apache/tika/config/TikaActivator.java
* (edit) tika-core/src/main/java/org/apache/tika/config/ServiceLoader.java
> Support OSGi Service Loader Mediator Spec
> -----------------------------------------
>
> Key: TIKA-4700
> URL: https://issues.apache.org/jira/browse/TIKA-4700
> Project: Tika
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Priority: Major
>
> The [Java Service
> Loader|https://docs.oracle.com/javase/8/docs/api/java/util/ServiceLoader.html]
> is not properly supported in OSGi cross bundle boundaries due to Classloader
> visibility restrictions. In order to circumvent this limitation the [OSGi
> Service Loader Mediator
> Specification|https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.loader.html]
> defines certain {{Capabilities}} which are used to set up a registry where
> all bundles have access to providers (no matter from which bundles).
> This mechanism is just relying on additional Manifest headers which don't
> impact usability of those JARs outside OSGi.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
