@ImplementationsShouldExtend(value=FsAbstractNode.class) public interface FsNode extends net.java.truecommons.cio.Entry
| Modifier and Type | Method and Description |
|---|---|
Set<String> |
getMembers()
Returns a set of strings with the base names of the members of this
directory node or
null if and only if this is not a directory
node. |
String |
getName()
Returns a string representation of the
file system node name. |
net.java.truecommons.shed.BitField<net.java.truecommons.cio.Entry.Type> |
getTypes()
Returns a bit field of types implemented by this file system node.
|
boolean |
isType(net.java.truecommons.cio.Entry.Type type)
Returns
true if and only if this file system node implements
the given type. |
@Nullable Set<String> getMembers()
null if and only if this is not a directory
node.
Whether or not modifying the returned set is supported and the effect
on the file system is implementation specific.null if and only if this is not a
directory node.String getName()
file system node name.getName in interface net.java.truecommons.cio.Entryfile system node name.net.java.truecommons.shed.BitField<net.java.truecommons.cio.Entry.Type> getTypes()
Some file system types allow a node to implement multiple types.
For example, a ZIP or TAR file may contain an archive entry with the
name foo and a directory archive entry with the name foo/.
Yes, this is strange, but sh*t happens!
In this case then, a virtual file system should collapse this into one
file system node which returns true for both
isType(FILE) and isType(DIRECTORY).
boolean isType(net.java.truecommons.cio.Entry.Type type)
true if and only if this file system node implements
the given type.type - the type to test.true if and only if this file system node implements
the given type.getTypes()Copyright © 2005–2018 Schlichtherle IT Services. All rights reserved.