Two new compressed streams have been added as a change:
- java.util.zip.DeflaterInputStream: Data read from this stream is compressed.
- java.util.zip.InflaterOutputStream: Data written to this stream is decompressed.
For example, these can be useful if a client wants to send compressed data over a network. The data can be compressed into packets with DeflaterInputStream, and those packets written over the network connection. The receiving end then reads the compressed packets from the network connection, and decompresses them by writing to an InflaterOutputStream.
Changes to the jar command
There are two changes to the behavior of the jar command:
- Before Java SE 6, the timestamps (date and time) of extracted files by jar command are those listed the current time means extraction time instead of archive file time. In Java SE 6, they do a change in jar command behavior that is the date and time of extracted files by jar command was the archive time.
-
- At the time of creating a jar, we have the ability in executable jar file to specify the entry point for stand-alone application bundle. The 'e' option declares the entry point through creating or overriding the Main-Class attribute value in the jar file's manifest.
Changes in ZIP File:
On all platforms, zip files can contain more than 64k entries.
On Windows some limitations have been removed:
- File names longer than 256 characters are now supported.
- The limitation of just over 2,000 simultaneously open zip files has been removed.
- It removed a limitation on the number of concurrently open ZIP files on Microsoft Windows. The maximum used to be 2036, but now it's whatever the platform will support.
- The ZIP file format has a 2-byte field to record the number of entries in the file.
- We now use the same support for long file names in ZIP files as we use in the java.io package.
-
- java.util.ServiceLoader added as the standard way for clients to load plugable code.
. |
Total Members
Delicious
Digg
Technorati
Blink
Furl
Reddit
Newsvine
Google
