You can override the settings for the default project by placing a mcs-project.xml file either in the same directory as an XDIME page being processed, or somewhere on the path to it. The following table lists the project configuration elements.
You can override the settings for the default project by placing a mcs-project.xml file either in the same directory as an XDIME page being processed, or somewhere on the path to it. The following table lists the project configuration elements.
Name | Purpose |
---|---|
assets | Project specific configuration relating to assets. |
bindings | Contains a set of binding policies (provided by projects or libraries) that can be applied to elements from within the project. |
cache | Allows page authors to control caching for a given project. |
constraints | Container for elements that limit the range of values that are acceptable for individual cache entries. |
default-layout | Specifies a layout which should be used as the default layout by the selected project. |
interval | Specifies the time between one failed attempt to refresh the policy and the next attempt. |
jdbc-policies | Indicates that policies are stored in a JDBC database. |
libraries | Container for a list of libraries. |
library | A reference to a library. |
max-count | Specifies the maximum number of retries that are allowed before the policy is treated as being unavailable. |
policy | A reference to a policy. |
policy-cache-partition | Represents the configuration of the policy cache partition. |
project | Container for project information. |
retain | Specifies whether or not the cached policy should be used to satisfy requests that occur during the retry period. |
retry | Controls whether or not to retry a failed attempt to retrieve the entry from the associated policy. |
themes | Specifies a number of themes that will be used by all the pages in the project. |
time-to-live | Specifies the length of time that the cached entry is valid from the time it enters the cache. |
type | Specifies the policy type(s) for which a partition should be created. Each type in the sequence gets its own partition created with the constraints rather than sharing a cache. |
type-partition | Specifies the configuration for the policy type specific sub partitions. |
xml-policies | Indicates that policies are stored as XML. |