-
name
String name
-
id
Serializable id
-
createdDate
Date createdDate
Read-only.
-
creatorId
String creatorId
-
lastModifiedDate
Date lastModifiedDate
Read-only.
-
folder
boolean folder
-
path
String path
Read-only.
-
hidden
boolean hidden
-
versioned
boolean versioned
-
fileSize
long fileSize
-
versionId
Serializable versionId
The version name or number. Read-only.
-
locked
boolean locked
Locked status. Read-only.
-
lockOwner
String lockOwner
Username of the owner of the lock. Read-only. null
if file not locked.
-
lockMessage
String lockMessage
Message left by the owner when he locked the file. Read-only. null
if file not locked.
-
lockDate
Date lockDate
The date that this lock was created. Read-only. null
if file not locked.
-
title
String title
A title for the file for the current locale. If locale not available, the file's name is returned. Read-only.
-
description
String description
A description of the file for the current locale. Read-only.
-
locale
String locale
The locale string with which locale-sensitive fields (like title) are populated. Used in
RepositoryFile.equals(Object)
calculation to guarantee caching works correctly. Read-only.
-
originalParentFolderPath
String originalParentFolderPath
The original folder path where the file resided before it was deleted. If this file has been deleted (but not
permanently deleted), then this field will be non-null. Read-only.
-
deletedDate
Date deletedDate
The date this file was deleted. If this file has been deleted (but not permanently deleted), then this field will
be non-null. Read-only.
-
localePropertiesMap
Map<K,V> localePropertiesMap
A map for locale properties. Keys are locale names and values are locale key-value pairs.
-
aclNode
boolean aclNode
A boolean describing if a repository file is acl node or not. The purpose of a acl node is to be a placeholder
for ACLs on another node which cannot have such ACLs on it's own. An example of such a scenario is one where the
node being shadowed is in an area of the repository which prevents any access (/etc/*). Subsystems can create a
acl node in this case to store and check access rules (ACLs), while still preserving the original acled node
in the restricted area.