Interface I_CmsResourceType

All Superinterfaces:
I_CmsConfigurationParameterHandler, Serializable
All Known Implementing Classes:
A_CmsResourceType, A_CmsResourceTypeFolderBase, A_CmsResourceTypeLinkParseable, CmsResourceTypeBinary, CmsResourceTypeFolder, CmsResourceTypeFolderExtended, CmsResourceTypeFolderSubSitemap, CmsResourceTypeFunctionConfig, CmsResourceTypeHtmlRedirect, CmsResourceTypeImage, CmsResourceTypeJsp, CmsResourceTypeLocaleIndependentXmlContent, CmsResourceTypeMacroFormatter, CmsResourceTypePlain, CmsResourceTypePointer, CmsResourceTypeSeoFile, CmsResourceTypeSubsitemapContentFolder, CmsResourceTypeUnknown, CmsResourceTypeUnknownFile, CmsResourceTypeUnknownFolder, CmsResourceTypeXmlAdeConfiguration, CmsResourceTypeXmlContainerPage, CmsResourceTypeXmlContent, CmsResourceTypeXmlPage

Resource type descriptors for all resources in the VFS.

Each file in the VFS must belong to an initialized resource type. The available resource type are read during system startup from the configuration file opencms-vfs.xml.

Certain resource types may require special handling for certain operations. This is usually required for write operations, or other operations that modify the VFS database. Therefore, the CmsObject defers handling of this operations to implementations of this interface.

If you implement a new resource type, it's a good idea to extend the abstract class A_CmsResourceType.

Important: The CmsObject passes the CmsSecurityManager object to implementations of this class. Using this object correctly is key to the resource type operations. Mistakes made in the implementation of a resource type can screw up the system security and the database structure, and make you unhappy.

Since:
6.0.0