Apache Isis™

Docs » Core

Deployment Types and Component Defaults

One important configuration setting is the deploymentType, which, in turn, specifies the deploymentCategory. If a component implementation is not specified explicitly, then the default is based on the deployment category (see the InstallerLookupDefault class). Certain other features are based on the category also.

Deployment category Deployment types Authentication
(if not specified)		 Authorization
(if not specified)		 Object store
(if not specified)		 Profile store
(if not specified)		 @Exploration actions @Prototype actions
EXPLORING SERVER_EXPLORATION
EXPLORATION
UTILITY		 Bypass Bypass In-memory In-memory Visible Not visible
PROTOTYPING SERVER_PROTOTYPE
PROTOTYPE		 File-based Bypass In-memory In-memory Not visible Visible
PRODUCTION SERVER
UNIT_TESTING
SINGLE_USER		 File-based File-based XML XML Not visible Not visible

Specifying the deploymentType explicitly

Scimpi, HTML, Restful Objects

For the scimpi, html and restfulobjects viewers, the deploymentType is specified in the <web.xml> file:

<context-param>
    <param-name>deploymentType</param-name>
    <param-value>SERVER</param-value>
</context-param>

If running these viewers using the WebServer, then the deploymentType can be overridden at the command line:

-t server_prototype

or using the long form:

--type server_exploration

Only server_*-style deploymentTypes should be specified (it has a bearing on the way that Isis does its session management).

The default if not specified is SERVER.

Wicket

For the wicket viewer, the Isis deploymentType is inferred from Apache Wicket's own deployment mode:

The Wicket mode is set in the usual way for a Wicket application:

<init-param>
    <param-name>configuration</param-name>
    <param-value>deployment</param-value>
</init-param>

DnD

For the dnd viewer, the deploymentType is specified at the command-line, for example:

-t prototype

or using the long form:

--type exploration

The default if not specified is PROTOTYPE.