UnixCompress Chilkat2 Java Reference Documentation

UnixCompress

Current Version: 11.7.0

Markdown version of this page for AI tools (v 11.7.0) · all AI docs

Chilkat.UnixCompress

Compress, uncompress, and unpack legacy UNIX .Z files.

Chilkat.UnixCompress provides UNIX compress and uncompress functionality for legacy .Z files. It supports file-based, memory-based, and string-based workflows, uses LZW compression, can unpack .tar.Z archives, and includes abort and progress-related support for longer-running operations.

Compress to .Z

Compress files, memory data, or strings into UNIX .Z format using LZW compression.

Uncompress .Z data

Expand UNIX-compressed data back to files, memory, byte arrays, or text depending on the application workflow.

File workflows

Compress and uncompress directly between input and output files when working with existing filesystem data.

Memory workflows

Work with compressed or uncompressed byte data in memory when temporary files are not desired.

String workflows

Compress and uncompress text using an explicit character set so string data round-trips correctly.

Unpack tar.Z archives

Use UnTarZ to decompress and extract legacy .tar.Z archives in a single workflow.

Common pattern: Use UnixCompress when the data is in classic UNIX .Z format or when a .tar.Z archive must be unpacked. Use Chilkat.Gzip for .gz and .tar.gz files, Chilkat.Bz2 for .bz2 files, and Chilkat.Compression for raw compression algorithms and general-purpose compression workflows.

Object Creation

import com.chilkatsoft.chilkat2.ChilkatException;
import com.chilkatsoft.chilkat2.UnixCompress;

try (UnixCompress unixCompress = new UnixCompress()) {
    // ... use unixCompress ...
} catch (ChilkatException e) {
    System.out.println(e.getMessage());          // "UnixCompress.someMethod failed: <reason>"
    System.out.println(e.getLastErrorText());    // the full log of the failed call
}
public UnixCompress()

Creates the underlying native Chilkat object. The native library (chilkat2java) is loaded the first time any Chilkat2 object is created; see the README in the download for where it is looked for (-Dchilkat2.library.path, a classpath resource, or java.library.path).

public void close()

Releases the native object (UnixCompress is AutoCloseable, so try-with-resources calls it). Calling it again does nothing; any other method or property accessor called afterwards throws IllegalStateException. An object that is never closed is freed by a background cleaner once it becomes unreachable, but the garbage collector does not see native memory, so closing is the normal path. Objects returned by methods are owned by the caller too.

public boolean isClosed()

Returns true once close() has been called.

Errors

A method that fails throws ChilkatException, an unchecked exception carrying getClassName(), getMethodName(), getReason() (one line, also in the message) and getLastErrorText() (the full log, captured at the moment of the failure). The object remains usable. Methods that look something up and find nothing return null instead of throwing (each such method says so), and methods that answer a question (hasMember, isUnlocked, ...) return a plain boolean. Property accessors do not throw for Chilkat reasons.

A null string or object argument throws NullPointerException naming the parameter (except where a method documents that null is accepted), and a string containing U+0000 throws IllegalArgumentException.

Use an object from one thread at a time; it may be handed from one thread to another. The one cross-thread operation is setting setAbortCurrent(true) on an object that is busy in another thread (on the classes that have AbortCurrent). Unlocking: call new Global().unlockBundle("...") once at startup.

Properties

AbortCurrent
// read/write
boolean getAbortCurrent()
void setAbortCurrent(boolean value)
Introduced in version 9.5.0.58

When set to true, causes the currently running method to abort. Methods that always finish quickly (i.e.have no length file operations or network communications) are not affected. If no method is running, then this property is automatically reset to false when the next method is called. When the abort occurs, this property is reset to false. Both synchronous and asynchronous method calls can be aborted. (A synchronous method call could be aborted by setting this property from a separate thread.)

top
DebugLogFilePath
// read/write
String getDebugLogFilePath()
void setDebugLogFilePath(String value)

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

  • A timeout property set to 0, indicating an infinite timeout.
  • A hang occurring within an event callback in the application code.
  • An internal bug in the Chilkat code causing the hang.

More Information and Examples
top
HeartbeatMs
// read/write
int getHeartbeatMs()
void setHeartbeatMs(int value)

The interval in milliseconds between each AbortCheck event callback, which enables an application to abort certain method calls before they complete. By default, HeartbeatMs is set to 0, meaning no AbortCheck event callbacks will trigger.

More Information and Examples
top
LastErrorHtml
// read-only
String getLastErrorHtml()

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorText
// read-only
String getLastErrorText()

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorXml
// read-only
String getLastErrorXml()

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastMethodSuccess
// read/write
boolean getLastMethodSuccess()
void setLastMethodSuccess(boolean value)

Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

top
VerboseLogging
// read/write
boolean getVerboseLogging()
void setVerboseLogging(boolean value)

If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
// read-only
String getVersion()

Version of the component/library, such as "10.1.0"

More Information and Examples
top

Methods

CompressFile
void compressFile(String inFilename, String destPath)

Compresses a file to create a UNIX compressed file (.Z). This compression uses the LZW (Lempel-Ziv-Welch) compression algorithm.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
CompressStringToFile
void compressStringToFile(String inStr, String charset, String destPath)

Unix compresses and creates a .Z file from string data. The charset specifies the character encoding used for the byte representation of the characters when compressed. The charset can be any one of a large number of character encodings, such as utf-8, iso-8859-1, Windows-1252, ucs-2, etc.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

More Information and Examples
top
UncompressFile
void uncompressFile(String inFilename, String destPath)

Uncompresses a .Z file. (This compression uses the LZW (Lempel-Ziv-Welch) compression algorithm.)

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
UncompressFileToString
String uncompressFileToString(String zFilename, String charset)

Uncompresses a .Z file that contains a text file. The contents of the text file are returned as a string. The character encoding of the text file is specified by charset. Typical charsets are iso-8859-1, utf-8, windows-1252, shift_JIS, big5, etc.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

More Information and Examples
top
UnTarZ
void unTarZ(String zFilename, String destDir, boolean bNoAbsolute)

Unpacks a .tar.Z file. The decompress and untar occur in streaming mode. There are no temporary files and the memory footprint is constant (and small) while untarring.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top

Events

All Chilkat methods are synchronous: the call returns when the work is done. During a long-running call, UnixCompress reports progress through a ProgressListener, an interface with three methods, each with a default, so you override only what you need:

import com.chilkatsoft.chilkat2.ProgressListener;

unixCompress.setProgressListener(new ProgressListener() {
    @Override public boolean percentDone(int pctDone) {
        System.out.println(pctDone + "%");
        return false;           // return true to abort the method in progress
    }
    @Override public void progressInfo(String name, String value) {
        System.out.println(name + ": " + value);
    }
});
unixCompress.setHeartbeatMs(250);   // abortCheck 4 times per second

For a single callback, a lambda is shorter:

unixCompress.onPercentDone(pct -> { System.out.println(pct + "%"); return false; });
public void setProgressListener(ProgressListener listener)

Installs listener as the receiver of this object's events, replacing any listener or lambda installed before; null removes it.

public ProgressListener getProgressListener()

Returns the installed listener, or null.

public void onAbortCheck(BooleanSupplier callback)
public void onPercentDone(IntPredicate callback)
public void onProgressInfo(BiConsumer<String, String> callback)

Each installs a listener whose only callback is the given lambda (from java.util.function). Like setProgressListener, each replaces the listener installed before, so to handle more than one event, implement ProgressListener. null removes the listener.

abortCheck is called at the interval set by the HeartbeatMs property (0, the default, disables it); percentDone is called when an operation's completion percentage is known; progressInfo delivers named progress values. Returning true from abortCheck or percentDone aborts the running method, which then throws ChilkatException.

Callbacks run on the thread that called the method, before it returns. Inside a callback, property accessors of the object (such as setAbortCurrent(true)) and other objects may be used, but calling a method of the same object throws IllegalStateException. An exception thrown by a callback aborts the running method and is rethrown from it; the object remains usable.

AbortCheck
// ProgressListener method (default returns false), or onAbortCheck(BooleanSupplier)
boolean abortCheck()

Enables a method call to be aborted by triggering the AbortCheck event at intervals defined by the HeartbeatMs property. If HeartbeatMs is set to its default value of 0, no events will occur. For instance, set HeartbeatMs to 200 to trigger 5 AbortCheck events per second.

More Information and Examples

Example

import java.util.concurrent.atomic.AtomicBoolean;

final AtomicBoolean stop = new AtomicBoolean(false);   // another thread may call stop.set(true)
unixCompress.setHeartbeatMs(250);                     // call abortCheck 4 times per second
unixCompress.onAbortCheck(() -> stop.get());
top
PercentDone
// ProgressListener method (default returns false), or onPercentDone(IntPredicate)
boolean percentDone(int pctDone)

This provides the percentage completion for any method involving network communications or time-consuming processing, assuming the progress can be measured as a percentage. This event is triggered only when it's possible and logical to express the operation's progress as a percentage. The pctDone argument will range from 1 to 100. For methods that finish quickly, the number of PercentDone callbacks may vary, but the final callback will have pctDone equal to 100. For longer operations, callbacks will not exceed one per percentage point (e.g., 1, 2, 3, ..., 98, 99, 100).

The PercentDone callback also acts as an AbortCheck event. For fast methods where PercentDone fires, an AbortCheck event may not trigger since the PercentDone callback already provides an opportunity to abort. For longer operations, where time between PercentDone callbacks is extended, AbortCheck callbacks enable more responsive operation termination.

To abort the operation, set the abort output argument to true. This will cause the method to terminate and return a failure status or corresponding failure value.

More Information and Examples

Example

unixCompress.onPercentDone(pct -> {
    // pct ranges from 0 to 100.
    System.out.println("Percent done: " + pct);
    return false;   // return true to abort the method in progress
});
top
ProgressInfo
// ProgressListener method (default does nothing), or onProgressInfo(BiConsumer<String, String>)
void progressInfo(String name, String value)

This event callback provides tag name/value pairs that detail what occurs during a method call. To discover existing tag names, create code to handle the event, emit the pairs, and review them. Most tag names are self-explanatory.

Note: Some Chilkat methods don't fire any ProgressInfo events.

More Information and Examples

Example

unixCompress.onProgressInfo((name, value) -> System.out.println(name + ": " + value));
top