A Java Web Application (webapp) is a collection of servlets, other Java classes, static resources such as HTML pages, other resources, and meta information that describes the webapp bundled together. You can run a webapp on a servlet container. A Java webapp has a typical structure. It can be packaged as a WAR file. A webapp usually contains already packed portions called libraries or modules as JAR files.
Webapps provided by Magnolia
Magnolia provides the following stand-alone, pre-configured Apache Tomcat server that does not include a webapp:
|Usage / purpose|
|A preconfigured Tomcat server ready to be used with any Magnolia webapp.|
Magnolia provides the following webapps and bundles.
To get the complete list of the modules in each webapp or bundle, look at the corresponding pom file of the bundle or see Supported modules in the cloud.
This is the DX Core webapp for projects.
DX Core webapp plus the travel demo for evaluation purposes.
For internal and partner cloud Magnolia usage.
Partners should use
|This is the most basic Magnolia webapp. Use this as a basis for your custom webapp.|
|Complete Magnolia Community Edition webapp for community projects.|
|Community Edition webapp plus the travel demo for evaluation purposes.|
Webapp directory structure
The directory structure is the container that holds the components of a webapp. The first step in creating a Magnolia webapp is creating this structure. The following table describes what each directory should contain.
Files with cached content.
Files extracted from
Magnolia log files.
Meta information files, e.g. from Maven.
Templates extracted from
Temporary work directory.
All resources related to the application that are not in the document root. WEB-INF directory is not part of the public document. No files contained in this directory can be served directly to a client.
Bootstrap files. Empty by default.
Bootstrapped on author and public instances.
Bootstrapped on author instance only.
Bootstrapped on public instance only.
Class path for manually deployed classes.
Configuration files for repository and properties.
Properties such as: repository location, persistence manager to be used, should samples be bootstrapped, should installation be done in unattended mode etc.
Defines repository configuration.
Log4j logging configuration.
Properties used on author instance only.
Properties used on public instance only.
Persistence manager configuration files.
Configuration for authentication and authorization.
Deployment descriptor. Describes configuration information for the entire web application.
Adding the Magnolia main filter to the webapp
The Magnolia main filter is registered in the
web.xml file. The file only defines one filter:
The Magnolia main filter will delegate the request to the Magnolia filter chain. The filter is also mapped to forward requests, which means that the Magnolia filter chain will be re-executed on internal forwards.
Adding the Magnolia context listener
web.xml we also register one listener:
The listener initializes the system, starts the repository and modules, while the filter handles all requests.