Handle attributes of files.
Controls modification of files.
Information about files.
Provides access to the hierarchy of resources.
Information about files related to symbolic links.
Controls on moving of files.
Listener for changes in
Listener to changes in annotation of file objects.
An action that it is to be called atomically with respect to filesystem event notification.
Listener to changes in the filesystem pool.
Provides decorations based on file state.
This convenience implementation does much of the hard work of
FileSystem and is generally more pleasant to create
AbstractFileSystem.Attr using a special file
in each folder for holding attributes.
Event used to listen on filesystem attribute changes.
Adapter for changes in
Event for listening on filesystem changes.
Represents an acquired lock on a
This is the base for all implementations of file objects on a filesystem.
Event indicating a file rename.
Event describing a change in annotation of files.
Interface that provides basic information about a virtual filesystem.
Common utilities for handling files.
A virtual filesystem based on a JAR archive.
Implementation of all interfaces List, Change, Info and Attr that delegates to JarFileSystem
The implementation class that implements List, Info and Change interfaces and delegates all the methods to appropriate methods of LocalFileSystem.
to invoke the mime resolving infrastructure.
General base class for filesystems which proxy to others.
Holder for NetBeans default (system, configuration) filesystem, used for most of NetBeans' runtime configuration.
Provides local repositories, depending on the current execution environment.
Dummy adapter for
Event describing adding a filesystem to, or removing a filesystem from, the filesystem pool.
Fired when a filesystem pool is reordered.
Mapper from FileObject -> URL.
Implementation of all interfaces List, Change, Info and Attr that delegates to XMLFileSystem
Exception raised when a file is already locked.
Signals that the file object is somehow corrupted.
Often a mime type can be deduced just by looking at a file extension.
Recognize mime type by looking into header of XML files.
Registration that allows effective, declarative registration of complex
NetBeans itself implements two filesystems: a local filesystem, which encapsulates access to the operating system's normal files; and a JAR filesystem, which allows users to mount Java Archive Files as if they were read-only directories.
Using the Filesystems API, third parties may add support for access to file-like objects stored in some different manner - for example, in a database or proprietary object storage system. More commonly, module authors should use this API whenever they need access to files; then their module should work automatically with any filesystem supported by NetBeans.
Other capabilities provided by the Filesystems API include locking files during write operations; listening for changes in a file's status, so that another part of NetBeans may reflect that change; and providing support for including the filesystem in the runtime class path of an external compiler or executor.