Add support to have modular, pre-packaged configurations (aka “config modules”)

Type: New Feature
Status: Closed
Priority: 1 Critical
Resolution: Fixed
Component/s:
Labels:

Assignee: nharward
Reporter: jhartley
Created: January 07, 2007
Votes: 0
Watchers: 0
Updated:
July 27, 2012
Resolved:
March 02, 2007

Description

Motivation: Move towards modularization to help adoption of 3rd party frameworks.

Requirements: “Configuration Modules” refers to bundles each with a separate configuration file to be layered on top of each other. This will make it easier for framework developers and other 3rd parties to build integrations and will make it easier for operators to deploy those integrations with Terracotta into their environments.

Application Developer/Operator – * List modules going to use * Have spot to put and/or retrieve modules * Be notified when Boot JAR needs rebuilding

Framework Provider – * Specify Terracotta configuration information (tc-config.xml) for a JAR * Specify dependencies * Tool for creating module * Needs version information

Allow kits to be shipped with default modules. For example, if there is a Swing module, it should be included in the kit so that running the JTable sample application can be done out-of-the-box without rebuilding the Boot JAR.

Comments

Nathaniel Harward 2007-01-15

There is a wiki page for developers located here: http://wiki.terracotta.org/confluence/display/wiki/Configuration+bundles

Nathaniel Harward 2007-01-18

Updating the issue name to be a little more descriptive.

Fiona OShea 2007-02-22

Moving due date to end of last dev iteration. As this issue has many dependencies.

Nathaniel Harward 2007-02-24

Need to rename “plugins” to “modules” per Taylor.

Nathaniel Harward 2007-03-02

Finally! Infrastructure support should be over at this point, save some minor detail or bug. Work at this point should be largely on the individual modules themselves.