Page tree
Skip to end of metadata
Go to start of metadata

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:

Artifact

Download


Usage / purpose

magnolia-tomcat-barebone

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.

Artifact name

Download

Usage
Travel demo
DX Core

dx-core-webapp

This is the DX Core webapp for projects. 

 Use dx-core-webapp for local Magnolia Cloud development.

(info) Add a tomcat-bundle classifier to use with Apache Tomcat. 

(minus)
dx-core-demo-webapp

DX Core webapp plus the travel demo for evaluation purposes.

(info) Add a tomcat-bundle classifier to use with Apache Tomcat. 

(tick)

dx-core-weblogic-webapp

Webapp tuned for Weblogic.(tick)

dx-core-websphere-webapp

Webapp tuned for Websphere

(warning) Does not include workflow modules.

(tick)
dx-core-wildfly-webapp

Webapp tuned for Wildfly.(tick)
dx-core-cloud-webapp

Mostly for internal and partner cloud Magnolia usage.

(warning) Use dx-core-webapp for local Magnolia Cloud development.

(tick)
Community Edition


magnolia-empty-webapp

This is the most basic Magnolia webapp. Use this as a basis for your custom webapp.(minus)

magnolia-community-webapp

Complete Magnolia Community Edition webapp for community projects.(minus)

magnolia-community-demo-webapp

Community Edition webapp plus the travel demo for evaluation purposes.(tick)
magnolia-community-demo-bundle

magnolia-community-demo-webapp bundled with Apache Tomcat. 

(tick)



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.

Path

Contents

cache/

Files with cached content.

docroot/

Files extracted from mgnl-files/docroot in the JAR.

logs/

Magnolia log files.

META-INF/

Meta information files, e.g. from Maven.

repositories/

Repository.

templates/

Templates extracted from mgnl-files/templates in the JAR.

tmp/

Temporary work directory.

WEB-INF/

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.

WEB-INF/bootstrap

Bootstrap files. Empty by default.

WEB-INF/bootstrap/common

Bootstrapped on author and public instances.

WEB-INF/bootstrap/author

Bootstrapped on author instance only.

WEB-INF/bootstrap/public

Bootstrapped on public instance only.

WEB-INF/classes

Class path for manually deployed classes.

WEB-INF/config

Configuration files for repository and properties.

WEB-INF/config/default

Configuration files.

WEB-INF/config/default/magnolia.properties

Properties such as: repository location, persistence manager to be used, should samples be bootstrapped, should installation be done in unattended mode etc.

WEB-INF/config/default/repositories.xml

Defines repository configuration.

WEB-INF/config/default/log4j.xml

Log4j logging configuration.

WEB-INF/config/magnoliaAuthor

Properties used on author instance only.

WEB-INF/config/magnoliaPublic

Properties used on public instance only.

WEB-INF/config/repo-config/typeOfPM.xml

Persistence manager configuration files.

WEB-INF/config/jaas.config

Configuration for authentication and authorization.

WEB-INF/lib

JAR files.

WEB-INF/web.xml

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:

<filter>
    <display-name>Magnolia global filters</display-name>
    <filter-name>magnoliaFilterChain</filter-name>
    <filter-class>info.magnolia.cms.filters.MgnlMainFilter
    </filter-class>
</filter>
<filter-mapping>
    <filter-name>magnoliaFilterChain</filter-name>
    <url-pattern>/*</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
    <dispatcher>ERROR</dispatcher>
</filter-mapping>

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

In web.xml we also register one listener:

<listener>
    <listener-class>
    info.magnolia.cms.servlets.MagnoliaServletContextListener
    </listener-class>
</listener>

The listener initializes the system, starts the repository and modules, while the filter handles all requests.