A module for Apache Isis to manage and persist both application and user settings (using Isis' JDO Objectstore).
Java HTML Shell CSS
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.



Build Status

This module, intended for use with Apache Isis, is a provides two services provide the ability to persist configuration settings using Isis' own JDO Objectstore.

With ApplicationSettingsService these settings have global scope; for the UserSettingsService the settings are scoped per user.

The settings themselves are keyed by a simple string, and can store any of boolean, String, int, long and LocalDate. The implementation persists these values in a single raw format, but the API exposed by the services aims to be type-safe.


The following screenshots show an example app’s usage of the module.

Installing the Fixture Data

Install sample fixtures:

010 install fixtures

App Settings

List all (demo) application settings:

020 list appsettings

listed in a table:

030 appsettings

and inspect detail:

040 appsetting detail

User Settings

List all (demo) user settings:

050 list usersettings

listed in a table:

060 usersettings

and inspect detail:

070 usersetting detail

How to run the Demo App

The prerequisite software is:

  • Java JDK 8 (>= 1.9.0) or Java JDK 7 (<= 1.8.0)

    • note that the compile source and target remains at JDK 7

  • maven 3 (3.2.x is recommended).

To build the demo app:

git clone https://github.com/isisaddons/isis-module-settings.git
mvn clean install

To run the demo app:

cd webapp
mvn jetty:run

Then log on using user: sven, password: pass

Relationship to Apache Isis Core

Isis Core 1.6.0 included the org.apache.isis.module:isis-module-settings:1.6.0 Maven artifact (and its submodules, isis-module-settings-applib and isis-module-settings-impl-jdo. This module is a direct copy of that code, with the following changes:

  • package names have been altered from org.apache.isis to org.isisaddons.module.settings

  • the persistent-unit (in the JDO manifest) has changed from isis-module-settings to org-isisaddons-module-settings-dom

  • for simplicity, the applib and impl submodules have been combined into a single module

Otherwise the functionality is identical; warts and all!

Isis 1.7.0 no longer ships with org.apache.isis.module:isis-module-settings; instead use this addon module.

How to configure/use

You can either use this module "out-of-the-box", or you can fork this repo and extend to your own requirements.


To use "out-of-the-box":

  • update your classpath by adding this dependency in your dom project’s pom.xml:

  • if using AppManifest, then update its getModules() method:

    public List<Class<?>> getModules() {
        return Arrays.asList(
  • otherwise, update your WEB-INF/isis.properties:


"Out-of-the-box" (-SNAPSHOT)

If you want to use the current -SNAPSHOT, then the steps are the same as above, except:

  • when updating the classpath, specify the appropriate -SNAPSHOT version:

  • add the repository definition to pick up the most recent snapshot (we use the Cloudbees continuous integration service). We suggest defining the repository in a <profile>:


Forking the repo

If instead you want to extend this module’s functionality, then we recommend that you fork this repo. The repo is structured as follows:

  • pom.xml - parent pom

  • app - the module implementation, depends on Isis applib, dom and fixture

  • dom - the module implementation, depends on Isis applib

  • fixture - fixtures, holding a sample domain objects and fixture scripts; depends on dom

  • integtests - integration tests for the module; depends on app

  • webapp - demo webapp (see above screenshots); depends on app


ApplicationSettingsService and ApplicationSettingsServiceRW

The module defines two interfaces for application settings. The first, ApplicationSettingsService, provides read-only access:

public interface ApplicationSettingsService {
    ApplicationSetting find(String key);
    List<ApplicationSetting> listAll();

The second, ApplicationSettingsServiceRW, extends the first and allows settings to be created:

public interface ApplicationSettingsServiceRW extends ApplicationSettingsService {
    ApplicationSetting newBoolean(String name, String description, Boolean defaultValue);
    ApplicationSetting newString(String name, String description, String defaultValue);
    ApplicationSetting newLocalDate(String name, String description, LocalDate defaultValue);
    ApplicationSetting newInt(String name, String description, Integer defaultValue);
    ApplicationSetting newLong(String name, String description, Long defaultValue);

UserSettingsService and UserSettingsServiceRW

The module defines two interfaces for user settings. These are almost identical to the application settings above, the significant difference being each setting is additional identified by the username that 'owns' it.

The first interface, UserSettingsService, provides read-only access:

public interface UserSettingsService {
    UserSetting find(String user, String key);
    List<UserSetting> listAll();
    List<UserSetting> listAllFor(String user);

The second, UserSettingsServiceRW, extends the first and allows settings to be created:

public interface UserSettingsServiceRW extends UserSettingsService {
    UserSetting newBoolean(String user, String name, String description, Boolean defaultValue);
    UserSetting newString(String user, String name, String description, String defaultValue);
    UserSetting newLocalDate(String user, String name, String description, LocalDate defaultValue);
    UserSetting newInt(String user, String name, String description, Integer defaultValue);
    UserSetting newLong(String user, String name, String description, Long defaultValue);


The ApplicationSettingsServiceJdo implements ApplicationSettingsServiceRW (and therefore also ApplicationSettingsService).

Similarly, the UserSettingsServiceJdo implements UserSettingsServiceRW (and therefore also UserSettingsService).

In 1.7.0, it was necessary to explicitly register these services in isis.properties, rationale being that the service contributes functionality that appears in the user interface. The module also provided "hidden" equivalents (ApplicationSettingsServiceJdoHidden and UserSettingsServiceJdoHidden) which could be registered which also implement the same services, but do not contribute actions to the UI.

In 1.8.0 the above policy is reversed: the ApplicationSettingsServiceJdo and UserSettingsServiceJdo services are both automatically registered, and both will provide functionality that will appear in the user interface. If this is not required, then either use security permissions or write a vetoing subscriber on the event bus to hide this functionality.

The two "hidden" equivalent services are deprecated in 1.8.0.

Change Log

  • 1.14.0 - released against Isis 1.14.0

  • 1.13.0 - released against Isis 1.13.0

  • 1.12.1 - released against Isis 1.12.1

  • 1.12.0 - (no release)

  • 1.11.0 - released against Isis 1.11.0

  • 1.10.0 - released against Isis 1.10.0

  • 1.9.0 - released against Isis 1.9.0

  • 1.8.0 - released against Isis 1.8.0. Services are automatically registered; their UI can be suppressed using subscriptions.

  • 1.7.0 - released against Isis 1.7.0

  • 1.6.0 - re-released as part of isisaddons, with classes under package org.isisaddons.module.settings


Copyright 2013~2016 Dan Haywood

Licensed under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at


Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.


The application uses icons from icons8.

Maven deploy notes

Only the dom module is deployed, and is done so using Sonatype’s OSS support (see user guide).

Release to Sonatype’s Snapshot Repo

To deploy a snapshot, use:

pushd dom
mvn clean deploy

The artifacts should be available in Sonatype’s Snapshot Repo.

Release an Interim Build

If you have commit access to this project (or a fork of your own) then you can create interim releases using the interim-release.sh script.

The idea is that this will - in a new branch - update the dom/pom.xml with a timestamped version (eg It then pushes the branch (and a tag) to the specified remote.

A CI server such as Jenkins can monitor the branches matching the wildcard origin/interim/* and create a build. These artifacts can then be published to a snapshot repository.

For example:

sh interim-release.sh 1.14.0 origin


  • 1.15.0 is the base release

  • origin is the name of the remote to which you have permissions to write to.

Release to Maven Central

The release.sh script automates the release process. It performs the following:

  • performs a sanity check (mvn clean install -o) that everything builds ok

  • bumps the pom.xml to a specified release version, and tag

  • performs a double check (mvn clean install -o) that everything still builds ok

  • releases the code using mvn clean deploy

  • bumps the pom.xml to a specified release version

For example:

sh release.sh 1.14.0 \
              1.15.0-SNAPSHOT \
              dan@haywood-associates.co.uk \
              "this is not really my passphrase"

where * $1 is the release version * $2 is the snapshot version * $3 is the email of the secret key (~/.gnupg/secring.gpg) to use for signing * $4 is the corresponding passphrase for that secret key.

Other ways of specifying the key and passphrase are available, see the `pgp-maven-plugin’s documentation).

If the script completes successfully, then push changes:

git push origin master && git push origin 1.14.0

If the script fails to complete, then identify the cause, perform a git reset --hard to start over and fix the issue before trying again. Note that in the dom’s `pom.xml the nexus-staging-maven-plugin has the autoReleaseAfterClose setting set to true (to automatically stage, close and the release the repo). You may want to set this to false if debugging an issue.

According to Sonatype’s guide, it takes about 10 minutes to sync, but up to 2 hours to update search.