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. Also remapping an existing namespace URI to another prefix is not supported.

Implicit Namespace Registration

Apart from the explicit namespace registration via CND files mentioned above they are sometimes also registered implicitly. FileVault Document View (DocView) Format enforces the declaration of each namespace with a mandatory prefix in the XML file. Those namespace mappings are globally registered lazily (i.e. when the according XML is processed) in case

  1. the namespace URI is not registered (mapped) yet in the repository namespace registry
  2. the prefix is not yet bound to another URI

In all other cases the namespace mapping is just overwritten for the current session (used for importing the docview XML).

Due to this implicit registration there is technically no need to register namespaces which are used outside the node types in CND files.

Namespace Prefixes

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

Although you can redefine a namespace URI 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 in case the namespace URI is already mapped to another prefix or the prefix is already bound to another URI. 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