JBoss Community Archive (Read Only)

ModeShape 5


There are three ways to configure ModeShape, and it depends on how you're deploying your application.

  1. Embedded ModeShape - In all other cases, ModeShape runs within your application, whether your application is a regular Java SE application or a web application deployed to a web container. This means that your application needs to create a single ModeShape engine, deploy a JSON configuration file for each of the repositories needed by your application, and shut down the engine when your application is shut down. See ModeShape in Java applications for more details.

  2. ModeShape and JBoss Wildfly - When ModeShape is installed into JBoss Wildfly, it is configured using the Wildfly configuration and tools (e.g., the command line interface, or CLI). For more details, see Configuring ModeShape in Wildfly.

  3. ModeShape via JCA - When your application is to be deployed to an environment that supports the Java Connector Architecture (JCA), then you can deploy ModeShape repositories via ModeShape's JCA adapter (available in ModeShape 3.1 or later). See ModeShape's JCA Adapter for more details.

Storage Configuration

You have to decide how you want to persist your repository data and binary data.

Index Configuration

Optionally add one or more index providers to your configuration.

Sequencer Configuration

Optionally add one or more sequencers to your configuration

External Content Configuration

Optionally add one or more external sources to your configuration

JBoss.org Content Archive (Read Only), exported from JBoss Community Documentation Editor at 2020-03-11 12:12:28 UTC, last content change 2016-04-05 10:54:38 UTC.