-
Enhancement
-
Resolution: Unresolved
-
P3
-
None
-
1.4.0, 1.4.1
-
Fix Understood
-
generic, x86
-
generic, windows_2000
Name: gm110360 Date: 04/03/2003
A DESCRIPTION OF THE REQUEST :
The Class-Path manifest file option has a length limit of 512 bytes for its value. Cannot specify complete list of Jars for our application. Cannot take advantage of Jar indexing feature because of this limitation.
JUSTIFICATION :
The 512 byte limitation is preventing our application from taking full advantage from the Jar indexing feature. We have over 60 Jars that need to be indexed to enhance the download process. There also seems to be no reason to even have such limitation.
EXPECTED VERSUS ACTUAL BEHAVIOR :
Jar utility to dynamically allocate space for any (at least 2K) size for the Class-Path manifest option value.
The "Line too long" Exception is thrown.
CUSTOMER SUBMITTED WORKAROUND :
No work around, except to rename our jar files with a short meanigless names
(Review ID: 183364)
======================================================================
A DESCRIPTION OF THE REQUEST :
The Class-Path manifest file option has a length limit of 512 bytes for its value. Cannot specify complete list of Jars for our application. Cannot take advantage of Jar indexing feature because of this limitation.
JUSTIFICATION :
The 512 byte limitation is preventing our application from taking full advantage from the Jar indexing feature. We have over 60 Jars that need to be indexed to enhance the download process. There also seems to be no reason to even have such limitation.
EXPECTED VERSUS ACTUAL BEHAVIOR :
Jar utility to dynamically allocate space for any (at least 2K) size for the Class-Path manifest option value.
The "Line too long" Exception is thrown.
CUSTOMER SUBMITTED WORKAROUND :
No work around, except to rename our jar files with a short meanigless names
(Review ID: 183364)
======================================================================
- duplicates
-
JDK-4620323 Manifest read() should remove 512 byte limit for Manifest main attributes
- Closed
- relates to
-
JDK-6372077 JarFile.getManifest() should handle manifest attribute name 70 bytes
- Closed
-
JDK-6443578 Continuation lines in JAR manifests do not follow RFC-822
- Open
-
JDK-4245700 Manifest spec and Class-Path header spec are contradictory
- Resolved