[
https://issues.apache.org/jira/browse/TIKA-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18120356#comment-18120356
]
Hudson commented on TIKA-4940:
------------------------------
FAILURE: Integrated in Jenkins build Tika » tika-main-jdk17 #1684 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1684/])
TIKA-4940: retire Tika's XML entity expansion limit (#3268) (github:
[https://github.com/apache/tika/commit/f7173fe3caba99b0904b9124ce6304476d034e95])
* (edit) CHANGES.txt
* (edit)
tika-serialization/src/main/java/org/apache/tika/serialization/config/GlobalSettings.java
* (edit) .gitignore
* (edit) tika-core/src/main/java/org/apache/tika/utils/XMLReaderUtils.java
* (edit)
tika-serialization/src/main/java/org/apache/tika/config/loader/TikaLoader.java
* (edit) tika-core/src/test/java/org/apache/tika/utils/XMLReaderUtilsTest.java
> Retire Tika's XML entity expansion limit in 4.x
> -----------------------------------------------
>
> Key: TIKA-4940
> URL: https://issues.apache.org/jira/browse/TIKA-4940
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> DIfferent jaxp providers handle entity expansion limits differently. Tika's
> custom entity expansion limit gives false hope that we are actually
> supporting all jaxp providers.
>
> We should make this a no-op in 4.2 with logging and then remove it in 5.0.0.
> Users can set xml entity limits with the standard/non-Tika-specific options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
