[
https://issues.apache.org/jira/browse/ARIES-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959731#comment-17959731
]
Amichai Rothman commented on ARIES-2124:
----------------------------------------
I just noticed this module/artifact was silently dropped from the project,
looks like in commit 64c2461, with no mention anywhere, not even in the git log
message. It's still being referenced in the jaxrs whiteboard features module.
Also in org.osgi:org.osgi.service.jaxrs, btw.
What should users of the deleted module migrate to? is it sufficient to replace
this dependency with org.apache.geronimo.specs:geronimo-osgi-locator and
org.apache.geronimo.specs:geronimo-jaxrs_2.1_spec? or is additional bundle
tweaking of some sort needed?
> Embedded jar file is corrupt
> ----------------------------
>
> Key: ARIES-2124
> URL: https://issues.apache.org/jira/browse/ARIES-2124
> Project: Aries
> Issue Type: Bug
> Components: jax-rs-whiteboard
> Affects Versions: jax-rs-whiteboard-2.0.2
> Reporter: Amichai Rothman
> Assignee: Jean-Baptiste Onofré
> Priority: Critical
>
> The aries-jax-rs-whiteboard karaf feature requires the bundle
> mvn:org.apache.aries.spec/org.apache.aries.javax.jax.rs-api/1.0.1. This
> bundle, in turn, contains an embedded jar and Bundle-ClassPath =
> .,lib/geronimo-osgi-locator.jar.
> This embedded jar is corrupt:
> {quote}
> $ unzip -t lib/geronimo-osgi-locator.jar
> Archive: lib/geronimo-osgi-locator.jar
> testing: META-INF/ OK
> testing: META-INF/MANIFEST.MF bad extra-field entry:
> EF block length (61373 bytes) exceeds remaining EF data (4 bytes)
> $jar tf lib/geronimo-osgi-locator.jar
> java.util.zip.ZipException: Invalid CEN header (invalid zip64 extra data
> field size)
> at java.base/java.util.zip.ZipFile$Source.zerror(ZipFile.java:1736)
> {quote}
> Even worse, other mechanisms that scan for resources within bundles balk at
> this (with the same ZipException) when scanning this bundle even if they have
> nothing to do with the jaxrs whiteboard. So this issue also breaks various
> unrelated application components.
> Note that the ZipFile exception may be related to changes in the JDK
> (11.0.20?) that added stricter validity checks on zip files, however even
> after and additional fix in JDK-8313765, using 11.0.20.1, this still occurs -
> presumably because the file is truly corrupt (as shown by the unzip/jar
> tools). Also setting the system property
> -Djdk.util.zip.disableZip64ExtraFieldValidation=true (as referenced in some
> of the linked JDK issues) doesn't help in this case.
> btw I couldn't find where the source for org.apache.aries.javax.jax.rs-api
> is, and maven central has a few newer releases up to 1.0.4, but all contain
> the same embedded corrupt jar. Further, I'm not sure where the corrupt
> geronimo-osgi-locator.jar came from. Maven central has a
> geronimo-osgi-locator-1.0.jar and a geronimo-osgi-locator-1.1.jar, neither of
> which are corrupt.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
