- java.lang.Object
-
- java.nio.file.FileSystems
-
public final class FileSystems extends Object
Factory methods for file systems. This class defines thegetDefault
method to get the default file system and factory methods to construct other types of file systems.The first invocation of any of the methods defined by this class causes the default
provider
to be loaded. The default provider, identified by the URI scheme "file", creates theFileSystem
that provides access to the file systems accessible to the Java virtual machine. If the process of loading or initializing the default provider fails then an unspecified error is thrown.The first invocation of the
installedProviders
method, by way of invoking any of thenewFileSystem
methods defined by this class, locates and loads all installed file system providers. Installed providers are loaded using the service-provider loading facility defined by theServiceLoader
class. Installed providers are loaded using the system class loader. If the system class loader cannot be found then the extension class loader is used; if there is no extension class loader then the bootstrap class loader is used. Providers are typically installed by placing them in a JAR file on the application class path or in the extension directory, the JAR file contains a provider-configuration file namedjava.nio.file.spi.FileSystemProvider
in the resource directoryMETA-INF/services
, and the file lists one or more fully-qualified names of concrete subclass ofFileSystemProvider
that have a zero argument constructor. The ordering that installed providers are located is implementation specific. If a provider is instantiated and itsgetScheme
returns the same URI scheme of a provider that was previously instantiated then the most recently instantiated duplicate is discarded. URI schemes are compared without regard to case. During construction a provider may safely access files associated with the default provider but care needs to be taken to avoid circular loading of other installed providers. If circular loading of installed providers is detected then an unspecified error is thrown.This class also defines factory methods that allow a
ClassLoader
to be specified when locating a provider. As with installed providers, the provider classes are identified by placing the provider configuration file in the resource directoryMETA-INF/services
.If a thread initiates the loading of the installed file system providers and another thread invokes a method that also attempts to load the providers then the method will block until the loading completes.
- Since:
- 1.7
-
-
Method Summary
Methods Modifier and Type Method and Description static FileSystem
getDefault()
Returns the defaultFileSystem
.static FileSystem
getFileSystem(URI uri)
Returns a reference to an existingFileSystem
.static FileSystem
newFileSystem(Path path, ClassLoader loader)
Constructs a newFileSystem
to access the contents of a file as a file system.static FileSystem
newFileSystem(URI uri, Map<String,?> env)
Constructs a new file system that is identified by aURI
static FileSystem
newFileSystem(URI uri, Map<String,?> env, ClassLoader loader)
Constructs a new file system that is identified by aURI
-
-
-
Method Detail
-
getDefault
public static FileSystem getDefault()
Returns the defaultFileSystem
. The default file system creates objects that provide access to the file systems accessible to the Java virtual machine. The working directory of the file system is the current user directory, named by the system propertyuser.dir
. This allows for interoperability with thejava.io.File
class.The first invocation of any of the methods defined by this class locates the default
provider
object. Where the system propertyjava.nio.file.spi.DefaultFileSystemProvider
is not defined then the default provider is a system-default provider that is invoked to create the default file system.If the system property
java.nio.file.spi.DefaultFileSystemProvider
is defined then it is taken to be a list of one or more fully-qualified names of concrete provider classes identified by the URI scheme"file"
. Where the property is a list of more than one name then the names are separated by a comma. Each class is loaded, using the system class loader, and instantiated by invoking a one argument constructor whose formal parameter type isFileSystemProvider
. The providers are loaded and instantiated in the order they are listed in the property. If this process fails or a provider's scheme is not equal to"file"
then an unspecified error is thrown. URI schemes are normally compared without regard to case but for the default provider, the scheme is required to be"file"
. The first provider class is instantiated by invoking it with a reference to the system-default provider. The second provider class is instantiated by invoking it with a reference to the first provider instance. The third provider class is instantiated by invoking it with a reference to the second instance, and so on. The last provider to be instantiated becomes the default provider; itsgetFileSystem
method is invoked with the URI"file:///"
to get a reference to the default file system.Subsequent invocations of this method return the file system that was returned by the first invocation.
- Returns:
- the default file system
-
getFileSystem
public static FileSystem getFileSystem(URI uri)
Returns a reference to an existingFileSystem
.This method iterates over the
installed
providers to locate the provider that is identified by the URIscheme
of the given URI. URI schemes are compared without regard to case. The exact form of the URI is highly provider dependent. If found, the provider'sgetFileSystem
method is invoked to obtain a reference to theFileSystem
.Once a file system created by this provider is
closed
it is provider-dependent if this method returns a reference to the closed file system or throwsFileSystemNotFoundException
. If the provider allows a new file system to be created with the same URI as a file system it previously created then this method throws the exception if invoked after the file system is closed (and before a new instance is created by thenewFileSystem
method).If a security manager is installed then a provider implementation may require to check a permission before returning a reference to an existing file system. In the case of the
default
file system, no permission check is required.- Throws:
IllegalArgumentException
- if the pre-conditions for theuri
parameter are not metFileSystemNotFoundException
- if the file system, identified by the URI, does not existProviderNotFoundException
- if a provider supporting the URI scheme is not installedSecurityException
- if a security manager is installed and it denies an unspecified permission
-
newFileSystem
public static FileSystem newFileSystem(URI uri, Map<String,?> env) throws IOException
Constructs a new file system that is identified by aURI
This method iterates over the
installed
providers to locate the provider that is identified by the URIscheme
of the given URI. URI schemes are compared without regard to case. The exact form of the URI is highly provider dependent. If found, the provider'snewFileSystem(URI,Map)
method is invoked to construct the new file system.Once a file system is
closed
it is provider-dependent if the provider allows a new file system to be created with the same URI as a file system it previously created.Usage Example: Suppose there is a provider identified by the scheme
"memory"
installed:Map<String,String> env = new HashMap<>(); env.put("capacity", "16G"); env.put("blockSize", "4k"); FileSystem fs = FileSystems.newFileSystem(URI.create("memory:///?name=logfs"), env);
- Parameters:
uri
- the URI identifying the file systemenv
- a map of provider specific properties to configure the file system; may be empty- Returns:
- a new file system
- Throws:
IllegalArgumentException
- if the pre-conditions for theuri
parameter are not met, or theenv
parameter does not contain properties required by the provider, or a property value is invalidFileSystemAlreadyExistsException
- if the file system has already been createdProviderNotFoundException
- if a provider supporting the URI scheme is not installedIOException
- if an I/O error occurs creating the file systemSecurityException
- if a security manager is installed and it denies an unspecified permission required by the file system provider implementation
-
newFileSystem
public static FileSystem newFileSystem(URI uri, Map<String,?> env, ClassLoader loader) throws IOException
Constructs a new file system that is identified by aURI
This method first attempts to locate an installed provider in exactly the same manner as the
newFileSystem(URI,Map)
method. If none of the installed providers support the URI scheme then an attempt is made to locate the provider using the given class loader. If a provider supporting the URI scheme is located then itsnewFileSystem(URI,Map)
is invoked to construct the new file system.- Parameters:
uri
- the URI identifying the file systemenv
- a map of provider specific properties to configure the file system; may be emptyloader
- the class loader to locate the provider ornull
to only attempt to locate an installed provider- Returns:
- a new file system
- Throws:
IllegalArgumentException
- if the pre-conditions for theuri
parameter are not met, or theenv
parameter does not contain properties required by the provider, or a property value is invalidFileSystemAlreadyExistsException
- if the URI scheme identifies an installed provider and the file system has already been createdProviderNotFoundException
- if a provider supporting the URI scheme is not foundServiceConfigurationError
- when an error occurs while loading a service providerIOException
- an I/O error occurs creating the file systemSecurityException
- if a security manager is installed and it denies an unspecified permission required by the file system provider implementation
-
newFileSystem
public static FileSystem newFileSystem(Path path, ClassLoader loader) throws IOException
Constructs a newFileSystem
to access the contents of a file as a file system.This method makes use of specialized providers that create pseudo file systems where the contents of one or more files is treated as a file system.
This method iterates over the
installed
providers. It invokes, in turn, each provider'snewFileSystem(Path,Map)
method with an empty map. If a provider returns a file system then the iteration terminates and the file system is returned. If none of the installed providers return aFileSystem
then an attempt is made to locate the provider using the given class loader. If a provider returns a file system then the lookup terminates and the file system is returned.- Parameters:
path
- the path to the fileloader
- the class loader to locate the provider ornull
to only attempt to locate an installed provider- Returns:
- a new file system
- Throws:
ProviderNotFoundException
- if a provider supporting this file type cannot be locatedServiceConfigurationError
- when an error occurs while loading a service providerIOException
- if an I/O error occursSecurityException
- if a security manager is installed and it denies an unspecified permission
-
-
Deutsche Übersetzung
Sie haben gebeten, diese Seite auf Deutsch zu besuchen. Momentan ist nur die Oberfläche übersetzt, aber noch nicht der gesamte Inhalt.Wenn Sie mir bei Übersetzungen helfen wollen, ist Ihr Beitrag willkommen. Alles, was Sie tun müssen, ist, sich auf der Website zu registrieren und mir eine Nachricht zu schicken, in der Sie gebeten werden, Sie der Gruppe der Übersetzer hinzuzufügen, die Ihnen die Möglichkeit gibt, die gewünschten Seiten zu übersetzen. Ein Link am Ende jeder übersetzten Seite zeigt an, dass Sie der Übersetzer sind und einen Link zu Ihrem Profil haben.
Vielen Dank im Voraus.
Dokument erstellt 11/06/2005, zuletzt geändert 04/03/2020
Quelle des gedruckten Dokuments:https://www.gaudry.be/de/java-api-rf-java/nio/file/filesystems.html
Die Infobro ist eine persönliche Seite, deren Inhalt in meiner alleinigen Verantwortung liegt. Der Text ist unter der CreativeCommons-Lizenz (BY-NC-SA) verfügbar. Weitere Informationen auf die Nutzungsbedingungen und dem Autor.
Referenzen
Diese Verweise und Links verweisen auf Dokumente, die während des Schreibens dieser Seite konsultiert wurden, oder die zusätzliche Informationen liefern können, aber die Autoren dieser Quellen können nicht für den Inhalt dieser Seite verantwortlich gemacht werden.
Der Autor Diese Website ist allein dafür verantwortlich, wie die verschiedenen Konzepte und Freiheiten, die mit den Nachschlagewerken gemacht werden, hier dargestellt werden. Denken Sie daran, dass Sie mehrere Quellinformationen austauschen müssen, um das Risiko von Fehlern zu reduzieren.