Fork me on GitHub

Node Types and Namespaces

Packages can register custom JCR node types and Namespaces during import by carrying arbitrarily many .cnd files. All files names matching the regular expression pattern set in package property cndPattern as well as all *.cnd files below META-INF/vault are considered. Details around the CND file format can be found at Node types and namespaces whose qualified name/prefix/uri is already registered are not touched. This also means that existing namespaces and node types are never modified but only once initially installed in case they are not yet there.

Namespace Prefixes

As the Standard Form of JCR Paths only uses qualified names (i.e. leveraging prefixes instead of full URLs) it is important that the destination repository uses the same prefixes as are being used in the package.

Although you can redefine a namespace URL to be mapped from another prefix in the FileVault Document View (DocView) Format this will only be used during parsing that file (i.e. once during import) but is not persisted in the destination repository. Particularly it won't affect:

  1. property values containing a path in the JCR standard form (for properties of type STRING). Property type PATH on the other hand internally always stores the full namespace URL and the local name, therefore the qualified name is calculated for each conversion to string and takes into account the current prefix mapping.
  2. the standard form of JCR paths containing namespaced items