|
org.openide.filesystems 7.8 | |||||||||
PREV NEXT | FRAMES NO FRAMES |
See:
Description
File System API | |
---|---|
org.openide.filesystems | NetBeans internally uses the concept of a virtual filesystem. |
NetBeans internally uses the concept of a virtual filesystem. This module provide APIs for accessing such virtual files as well as some support classes to make writing of custom vitual filesystems easier.
Added methods urlForArchiveOrDir
and archiveOrDirForURL
to FileUtil
to make it easier to work with classpaths.
Added utility methods:
public static FileObject addFileChangeListener (final FileChangeListener fcl)
to receive
FileEvents
from FileSystems
providing instances
of FileObject
convertible to java.io.File
public static FileObject removeFileChangeListener (final FileChangeListener fcl)
to no longer receive
FileEvents
from FileSystems
providing instances
of FileObject
convertible to java.io.File
public static FileObject refreshAll ()
to refreshes all FileObject
that represent files File.listRoots()
and their children recursively.
Added helper method for refreshing all necessary filesystems, to get
refreshed all instances of FileObject
representing
passed files
and their children recursively.
Simple way to run atomic action without having a fileobject is ensured by
adding two methods: FileUtil.runAtomicAction
.
All events about filesystem changes (related to events on all affected instances of FileSystem
)
are postponed after the whole code runned in atomic block is executed.
Added method isLocked
to FileObject
.
Many of the usecases are described at the overall documentation, in a way how to register a mime type. Some of the additional usecases are covered here.
Since version 7.1 there is a way to change the content of system file system in a dynamic way. As system file systems contains various definitions (in NetBeans Platform menus, toolbars, layout of windows, etc.) it de-facto allows global change to these settings for example when user logs into some system.
First thing to do is to create an implementation of filesystem. It can be created either from scratch, or by subclassing AbstractFileSystem, or MultiFileSystem. In this example we will subclass the MultiFileSystem:
public class LoginFileSystem extends MultiFileSystem { private static LoginFileSystem INSTANCE; public LoginFileSystem() { // let's create the filesystem empty, because the user // is not yet logged in INSTANCE = this; } public static void assignURL(URL u) throws SAXException { INSTANCE.setDelegates(new XMLFileSystem(u)); } }
It is necessary to register this instance in lookup by creating the file:
META-INF/services/org.openide.filesystems.FileSystem
with a single line containing the full
name of your filesystem - e.g. your.module.LoginFileSystem
.
When done, the system will find out your registration of the filesystem
on startup and will merge the content of the filesystem into the
default system file system. You can show a dialog letting the user
to log in to some system anytime later, and when the user is successfully
in, just call LoginFileSystem.assignURL(url)
where the
URL is an XML file in the same format
as used for regular layer files inside of many NetBeans modules.
The system will notice the change in the content and notify all the
config file listeners accordingly.
Of course, instead of XMLFileSystem you can use for example memory file system, or any other you write yourself.
|
|
|
The sources for the module are in the NetBeans Mercurial repositories.
XXX no answer for deploy-dependencies
Read more about the implementation in the answers to architecture questions.
|
org.openide.filesystems 7.8 | |||||||||
PREV NEXT | FRAMES NO FRAMES |