[
https://issues.apache.org/jira/browse/TIKA-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18068394#comment-18068394
]
ASF GitHub Bot commented on TIKA-4700:
--------------------------------------
kwin opened a new pull request, #2714:
URL: https://github.com/apache/tika/pull/2714
Generate according capabilities headers for providers via TikaComponent
annotations and Bnd's
https://bnd.bndtools.org/chapters/230-manifest-annotations.html#meta-infservices-annotations.
According capabilities headers for the consumer are generated via Bnd's
ServiceConsumer annotations.
> 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)
