public enum RepositoryFilePermission extends Enum<RepositoryFilePermission>
Why no EXECUTE
?
See JCR-2446.
Why no APPEND
?
Some implementations of these bits may not be able to distinguish between a file create and update. In this
case, APPEND
is useless. In the case of JCR, one might reasonably map APPEND to set_property and WRITE
to add_node. However, even an update on a file might involve the addition of a node.
Why no DELETE_CHILD
?
DELETE_CHILD
was believed to be too technical for end users to understand.
Why no DELETE
?
DELETE
mapped to jcr:removeNode which was also required for WRITE
. So if you had WRITE
,
you had DELETE
, making DELETE
redundant.
Enum Constant and Description |
---|
ACL_MANAGEMENT |
ALL |
DELETE |
READ |
WRITE |
Modifier and Type | Method and Description |
---|---|
static RepositoryFilePermission |
valueOf(String name)
Returns the enum constant of this type with the specified name.
|
static RepositoryFilePermission[] |
values()
Returns an array containing the constants of this enum type, in
the order they are declared.
|
public static final RepositoryFilePermission READ
public static final RepositoryFilePermission WRITE
public static final RepositoryFilePermission DELETE
public static final RepositoryFilePermission ACL_MANAGEMENT
public static final RepositoryFilePermission ALL
public static RepositoryFilePermission[] values()
for (RepositoryFilePermission c : RepositoryFilePermission.values()) System.out.println(c);
public static RepositoryFilePermission valueOf(String name)
name
- the name of the enum constant to be returned.IllegalArgumentException
- if this enum type has no constant with the specified nameNullPointerException
- if the argument is null