@DefaultAnnotation(value=edu.umd.cs.findbugs.annotations.NonNull.class)
TPath class and its
dependent classes.See: Description
| Interface | Description |
|---|---|
| TFileSystemProvider.Parameter |
Keys for environment maps.
|
| Class | Description |
|---|---|
| TFileSystem |
A
FileSystem implementation based on the TrueZIP Kernel module. |
| TFileSystemProvider |
A
FileSystemProvider implementation
based on the TrueZIP Kernel module. |
| TPath |
A
Path implementation based on the TrueZIP Kernel module. |
TPath class and its
dependent classes.
This is the primary API for JSE 7 compliant TrueZIP applications: Like the API of the module TrueZIP File*, this API is just a facade for the module TrueZIP Kernel. In contrast to the TrueZIP File* API however, this API can access any (virtual) file system, not just the platform file system and any archive files within the platform file system. In contrast to the TrueZIP Kernel API, both APIs are designed to be easy to learn and convenient to use while providing a great level of flexibility. Because all virtual file system state is managed by the TrueZIP Kernel module, this module can concurrently access the same file systems than the TrueZIP File* module.
For example, an application could access an entry within an archive file
which is located at a web site using a TPath like this:
Path path = new TPath(new URI("http://acme.com/download/everything.tar.gz/README.TXT"));
try (InputStream in = Files.newInputStream(path)) {
// Read archive entry contents here.
...
}
This example presumes that the JARs of the file system driver modules TrueZIP Driver HTTP(S) and TrueZIP Driver TAR are present on the run time class path.
Mind that a TPath is a Path, so you can use it
polymorphically with the NIO.2 API.
This package provides a JSE 7 compliant
file system provider
implementation in its class
TFileSystemProvider.
If the JAR of this package is present on the run time class path, an
application can transparently access archive files without a compile time
dependency on this API.
However, some constraints apply in this case because the NIO.2 API does not
support file system federation:
FileSystemProvider instance is limited to support exactly only
one file system
provider scheme.
So the installed TrueZIP file system provider
instance limits
the access to the platform file system, which is identified by the
custom URI scheme "tpath".
ZipFileSystemProvider instance provided by JSE 7.
So when
probing
ZIP or JAR files, it's undefined which provider will be used - see below.
Paths.get(String, String[]), the
returned Path instance is always associated with
the default file system provider, which depends on the JVM platform.
Path object to resolve another Path object,
e.g. by calling Path.resolve(Path), then the new
Path object is typically associated with the same
FileSystemProvider object.
So unless the original Path object was an instance of
TPath, when traversing a directory tree which contains a
prospective archive file, the new Path object will not be a
TPath instance, too, and so the application will most likely not
be able to access the archive file transparently as if it were just a
plain directory.
So the only way how an application can use the TrueZIP file system
provider instance without a compile time dependency is to use
FileSystems.newFileSystem(java.nio.file.Path, java.lang.ClassLoader).
However, this is unlikely to get used in most applications.
To overcome these constraints, an application should
not rely on File System Provider Service Location and directly create
TPath instances instead by calling
one of the public class constructors.
Once created, it's safe to use TPath instances polymorphically as
Path instances.
Mind that the NIO.2 API provides some features which are not supported by
the current implementation of this package, e.g. a file system permissions
or watch services.
Consequently, if an unsupported method is called, an
UnsupportedOperationException gets thrown.
Copyright © 2005-2013 Schlichtherle IT Services. All Rights Reserved.