Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
This page provides an overview of all ways to define custom JCR node types and create new workspaces with Magnolia.
Even though it has always been possible to define node types and create workspaces within Magnolia Maven modules, the Content Types module brings this functionality also to the light modules. Both approaches are valid.
Whichever approach you choose, we recommend not to develop and refine these definitions in a productive environment.
Editing node type and workspace definitions can lead to new node type definitions and workspaces which are registered again, whereas the system keeps the "old" ones which become obsolete.
With content types
By utilizing the
magnolia-content-types module you can define custom JCR content types and workspaces within light modules.
Defining content types within light modules can be accomplished on a running Magnolia system without redeploying the WAR file of your Magnolia instances and without restarting the instance or a module. This makes it a perfect approach if you have a Magnolia Cloud subscription package.
A content type definition in one file
You can define all of the following in just one file:
- JCR workspace
- JCR nodetype
This node type inherits from the Magnolia node type
mgnl:content. To define more sophisticated node types, you can create a node type definition file in a light module.
- JCR namespace
Defining and using a node type definition
You can define an XML-based node type definition. Since this definition must be readable as a Magnolia Resource, it can be a file in a light module or in a JAR file or in the
resources JCR workspace.
Create an XML-based node type definition file in your light module:
Reference the node type definition from a content type definition:Line 4: References the node type definition resource via
With a Magnolia Maven module descriptor
Magnolia registers workspaces and node types during a module's start-up phase in case they have not yet been registered.
Example of a module descriptor:
In the XML-based module descriptor you can add a
<workspace /> section in
To define and register new node types requires two things:
Creating an XML-based node type definition where you define the required node types and name spaces. Create the XML file in the
Referencing the node type file in the XML-based module descriptor: