[
https://issues.apache.org/jira/browse/TIKA-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123551#comment-18123551
]
Hudson commented on TIKA-4942:
------------------------------
UNSTABLE: Integrated in Jenkins build Tika » tika-main-jdk17 #1694 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1694/])
TIKA-4942: parsing and detection through the OSGi services no longer recurse
(#3275) (github:
[https://github.com/apache/tika/commit/8fdf05c01456ecef996f447def456916fc1a4ff7])
* (edit)
tika-bundles/tika-bundle-standard/src/main/java/org/apache/tika/bundle/internal/BundleActivator.java
* (edit) tika-core/src/main/java/org/apache/tika/detect/DefaultDetector.java
* (edit) CHANGES.txt
* (add)
tika-core/src/test/java/org/apache/tika/config/DynamicDefaultProviderTest.java
* (edit) tika-core/src/main/java/org/apache/tika/parser/DefaultParser.java
* (edit)
tika-bundles/tika-bundle-standard/src/test/java/org/apache/tika/bundle/BundleIT.java
> Avoid recursion in osgi in 4.x
> ------------------------------
>
> Key: TIKA-4942
> URL: https://issues.apache.org/jira/browse/TIKA-4942
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Blocker
>
> From my bot, based on [https://github.com/apache/tika/pull/3260] and
> [~pkarwasz] report
> {noformat}
> tika-bundle-standard registered a DefaultParser and DefaultDetector backed
> by
> a dynamic ServiceLoader. TikaActivator adds registered services to that same
> dynamic set, so each found itself and every parse or detect through the OSGi
> services overflowed the stack. The bundle now registers both on a
> non-dynamic
> loader, and a dynamic DefaultParser or DefaultDetector no longer merges in
> another dynamic one, which also covers third-party bundles and two bundles
> registering defaults.{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
