opencms-workplace.dtd

来自「找了很久才找到到源代码」· DTD 代码 · 共 765 行 · 第 1/2 页

<!-- 
# The root configuration node is called <opencms> for all OpenCms configurations.
-->
<!ELEMENT opencms (workplace)>

<!--
# <workplace> configuration:
#
# The workplace configuration contains options required for the "back office" 
# part of OpenCms.
-->
<!ELEMENT workplace (
	defaultlocale,
	localizedfolders,
	dialoghandlers, 
	editorhandler, 
	editoraction,
	editorcsshandlers?,
	editorpreconditions?,
	directeditprovider?, 
	exportpoints, 
	autolock?, 
	xmlcontentautocorrection?,	
	enableusermanagement?, 	
	defaultpropertiesonstructure,
	enableadvancedpropertytabs,
	maxfileuploadsize?, 
	labeledfolders?,
	workflow?,
	rfsfileviewsettings?,
	explorertypes+,
	user-infos?,
	default-preferences,
	workplace-customfoot?,
	tool-manager?)>

<!--
# The user additional information configuration.
-->
<!ELEMENT user-infos (info-block+) >

<!--
# The configuration of a block of user additional information.
-->
<!ELEMENT info-block (user-info+) >
<!ATTLIST info-block name CDATA #REQUIRED>

<!--
# The user additional information entry configuration.
-->
<!ELEMENT user-info EMPTY >
<!ATTLIST user-info key CDATA #REQUIRED
                    type (java.lang.Byte|java.lang.Short|java.lang.Integer|java.lang.Long|java.lang.Float|java.lang.Double|java.lang.Boolean|java.lang.Character|java.lang.String|java.util.Date|org.opencms.CmsUUID) #IMPLIED
		  			widget CDATA #IMPLIED
		  			params CDATA #IMPLIED
		  			optional (true|TRUE|false|FALSE) #IMPLIED >

<!--
# The workplace foot is customizable, color and background-color can be changed to have a better overview when
# working with more OpenCms installations. Also an additional text can be added to the foot which is displayed which
# is shown instead of the standard text.
-->	
<!ELEMENT workplace-customfoot (color?, background-color?, text?)>

<!ELEMENT color (#PCDATA)>
<!ELEMENT background-color (#PCDATA)>
<!ELEMENT text (#PCDATA)>
<!ATTLIST text replace (true|TRUE|false|FALSE) #REQUIRED>

<!--
# The tool manager configuration.
-->
<!ELEMENT tool-manager (roots) >

<!--
# A list of tool's roots.
-->
<!ELEMENT roots (root*) >

<!--
# A root.
-->
<!ELEMENT root (key, uri, name, helptext) >

<!--
# The key for accessing a root.
-->
<!ELEMENT key (#PCDATA) >

<!--
# The uri to look for tools for this root.
-->
<!ELEMENT uri (#PCDATA) >

<!--
# a macro for the display name of the given root.
-->
<!ELEMENT name (#PCDATA) >

<!--
# a macro for the helptext of the given root.
-->
<!ELEMENT helptext (#PCDATA) >

<!--
# The default locale of the OpenCms workplace that is selected if a user
# log into the workplace for the first time, of if his current selection 
# is invalid. User can change this setting individually with the preference dialog.
-->
<!ELEMENT defaultlocale (#PCDATA)>

<!--
# The worplace localized folders control if the workplace locale handler is used
# for a configured folder.
-->
<!ELEMENT localizedfolders (resource*)>
<!ELEMENT resource EMPTY>
<!ATTLIST resource uri CDATA #REQUIRED>

<!--
# The worklace dialog handlers allow extending / changing the default
# Workplace dialogs with another, customized implementation.
# For example, if your application requires a lot of special properties,
# you can implement your own property dialog handler that contains only
# the properties required by your application in a more user friendly form.
#
# If OpenCms does not start because a customized dialog handler class is not found, use the following 
# default dialog handler classes:
# - Delete dialog: org.opencms.workplace.commons.CmsDelete
# - Lock dialog: org.opencms.workplace.commons.CmsLock
# - Property dialog: org.opencms.workplace.commons.CmsPropertyAdvanced
-->
<!ELEMENT dialoghandlers (dialoghandler+)>
<!ELEMENT dialoghandler EMPTY>
<!ATTLIST dialoghandler class CDATA #REQUIRED>

<!--
# Using editor handler and editor action classes you can
# modify the behaviour of the "edit" action in the OpenCms Workplace.
-->
<!ELEMENT editorhandler EMPTY>
<!ATTLIST editorhandler class CDATA #REQUIRED>

<!ELEMENT editoraction EMPTY>
<!ATTLIST editoraction class CDATA #REQUIRED>

<!--
# The editor css handler classes.
# Classes handling the CSS stylesheet assignment for edited files.
# The specified class must implement the org.opencms.workplace.editors.I_CmsEditorCssHandler interface.
-->
<!ELEMENT editorcsshandlers (editorcsshandler+)>
<!ELEMENT editorcsshandler EMPTY>
<!ATTLIST editorcsshandler class CDATA #REQUIRED>

<!--
# The pre editor condition definition classes.
# For each resource type (identified by the resource type name), a precondition can be executed before the editor is opened.
# The specified class must implement the org.opencms.workplace.editors.I_CmsPreEditorActionDefinition interface.
-->
<!ELEMENT editorpreconditions (editorprecondition+)>
<!ELEMENT editorprecondition EMPTY>
<!ATTLIST editorprecondition name CDATA #REQUIRED class CDATA #REQUIRED>

<!ELEMENT directeditprovider (param*)>
<!ATTLIST directeditprovider class CDATA #REQUIRED>

<!ELEMENT param (#PCDATA)>
<!ATTLIST param name CDATA #REQUIRED>

<!--
# An export point is a folder inside the OpenCms VFS that is copied 1:1 to a 
# location in the real file system during publishing. This is for example used to 
# copy Java classes, JAR files or other system resouces from the VFS to the WEB-INF/classes or 
# WEB-INF/lib folder. No link processing is done for resources written with export points. 
-->
<!ELEMENT exportpoints (exportpoint+)>
<!ELEMENT exportpoint EMPTY>
<!ATTLIST exportpoint uri CDATA #REQUIRED destination CDATA #REQUIRED>

<!--
# Optional workflow settings. 
# The showmessages tag either contains "true" or "false" to add the workflow messages in the 
# workflow mails or not. Default is "false".
-->
<!ELEMENT workflow (showmessages)>
<!ELEMENT showmessages (#PCDATA)>

<!--
# Enables or disables the automatic locking of resources in the explorer view.
# If this is set to "true" (the default) edit operations can be performed
# on a resource that is unlocked, and the resource will be automatically locked
# for the user that performs the operation. If set to "false", an explicit
# locking of the resource is required.
-->
<!ELEMENT autolock (#PCDATA)>

<!--
# Enables or disables the auto correction of XML content resources in the editor if the XML Schema Definition has changed.
# If this is set to "true" (the default) the XML content editor corrects automatically the edited content
# without notifying the user. If this is set to "false", the user gets a confirmation dialog before the
# content is adjusted.
-->
<!ELEMENT xmlcontentautocorrection (#PCDATA)>

<!--
# Enables or disables the icons for editing users and groups 
# in the user management view. Set this to "false" if you
# administrate groups and users with an external tool.
# The default is "true".
-->
<!ELEMENT enableusermanagement (#PCDATA)>

<!--
# The default properties on structure setting of the OpenCms workplace 
# determines if a new property in the customized property dialogs should be written
# to the structure entry of a resource (i.e. a sibling) or to a resource.
# Resource properties are valid for all siblings until they are overwritten by setting
# an individual structure property.
-->
<!ELEMENT defaultpropertiesonstructure (#PCDATA)>

<!--
# The enable advanced property tabs setting of the OpenCms workplace 
# enables or disables the possibility to edit both the resource properties
# and the individual structure properties.
# If disabled, either the structure or the resource properties can be edited 
# depending on the default properties on structure setting.
-->
<!ELEMENT enableadvancedpropertytabs (#PCDATA)>

<!--
# Limits the size of the files which can be uploaded
# by users to the VFS. Limitation does not apply for members
# of the Administrators group.
# The value is the maximum file size in kilobytes.
# Disable the limitation by setting the value to -1, 
# or leaving this node empty.
-->
<!ELEMENT maxfileuploadsize (#PCDATA)>

<!--
# List of labeled folders. If a resource has a sibling in one of these folders,
# a special label icon will be shown in the explorer view on all siblings.
# Use this feature to identify "dangerous" folders (e.g. folders that 
# contain material that will be public available after publishing) 
# to prevent accidental creation of siblings in this folder to a resource that 
# contains sensitive data.
-->
<!ELEMENT labeledfolders (resource*)>

<!--
# Rfs file view settings:
# This corresponds to the bean class: org.opencms.util.CmsRfsFileView.
# The effect of these settings may be seen in OpenCms at: 
# new Administration -> workplace-tools -> logfile.
-->	
<!ELEMENT rfsfileviewsettings (
    filePath?,
    enabled?,
    fileEncoding?,
    isLogfile?, 
    windowSize?)>

<!--
# This element should be non-existant in new files during initialisation. 
# It is an absolute path to a file that will be shown. 
-->
<!ELEMENT filePath (#PCDATA)> 

<!--
# Boolean value ("true"|"false") that enables/disables preview of file content. 
-->
<!ELEMENT enabled (#PCDATA)>

<!--
# One of the charset.name() the local machine's java VM would return by: 
# Charset.availableCharsets().values() for each charset of that Set. 
# It depends on the java vendor / Operating System which values are valid but 
# at least the "Standard Charsets" mentioned in the java API doc for class 
# java.nio.Charset have to be supported everywhere.
-->
<!ELEMENT fileEncoding (#PCDATA)>

<!-- 
# Currently unused. In future this information may be used 
# to display file views  that are marked with isLogfile==true 
# in a more convenient way as the format is well known. 
-->
<!ELEMENT isLogfile (#PCDATA)>

<!-- 
# Determines how many lines of text will be previewed. 
-->
<!ELEMENT windowSize (#PCDATA)>

<!--
# Settings for the new resource dialog and the contextmenus in the explorer view.
# Configure which options are shown in the new resource dialog and if resources are 
# visible and editable depending on the current users group(s). The defaultaccesscontrol
# describes the default access control settings for all resourcestypes.
# The optional multicontextmenu describes the multi context menu configuration that is used if more
# files are selected in the explorer view.
-->
<!ELEMENT explorertypes (explorertype+, defaultaccesscontrol, multicontextmenu?, menurules?)>

<!--
# Enter the default permissions for OpenCms groups. 
-->
<!ELEMENT defaultaccesscontrol (accesscontrol)>

<!--
# Enter the default permissions for OpenCms groups. 
-->
<!ELEMENT multicontextmenu (
	entry*,
	separator*)*>

<!--
# Defines rule sets for menu items that should be displayed for a resource.
-->
<!ELEMENT menurules (menurule+)>

<!--
# A named menu rule set that can be referenced as rule by a context menu item entry.
-->
<!ELEMENT menurule (menuitemrule+)>
<!ATTLIST menurule name CDATA #REQUIRED>

<!--
# Defines a single rule for a menu item entry, the order of the menu item rules is important.
-->
<!ELEMENT menuitemrule EMPTY>
<!ATTLIST menuitemrule class CDATA #REQUIRED>

<!--
# <importexport> node options.
# In this node the import and export options are configured.
# If you are installing a fresh OpenCms system without migrating
# content from old OpenCms versions, you usually do not need any special 
# configuration. 
-->
<!ELEMENT importexport (
	importexporthandlers, 
	import )>

<!--
# List of import / export handlers.
# When content is imported, the manifest.xml is analyzed and the 
# appropriate handler for the import format is selected. 
-->
<!ELEMENT importexporthandlers (importexporthandler+)>
<!ELEMENT importexporthandler EMPTY>
<!ATTLIST importexporthandler class CDATA #REQUIRED>

<!-- 
# <import> node options.
# There are several options to ensure backward compatibility.
-->
<!ELEMENT import (overwrite?, convert?, oldwebappurl?, importversions+, immutables*, principaltranslations*, ignoredproperties*)>

<!--
# If this flag is set to "false" then imports > v2 (that should have resource UUIDs
# in the manifest) will move colliding resources to /system/lost-found/. Otherwise
# colliding resources will be overwritten. v1 and v2 imports (without resource 
# UUIDs in the manifest) are forced to overwrite colliding  resources, no matter 
# how this flag is set.
-->
<!ELEMENT overwrite (#PCDATA)>

<!--
# This flag controls if editabled content of older versions is automatically
# conterted to the current version upon import. For example, content of type 
# "page" from 5.0 is converted into "xmlpage" in 6.0.
-->
<!ELEMENT convert (#PCDATA)>

<!--
# Convert file content from 4.x to 5.x style during import
# This is needed for the correct content conversion of the import.
# Enter the URL of the OpenCms web application from which the content was exported,
# e.g. http://localhost:8080/opencms/opencms/ for a standard local Tomcat installation.
-->