Definition
Re-use an existing container installation
Explanations
An existing configuration plugs itself onto an existing container installation that exists on your hard disk. This is by opposition to the Standalone Local Configuration which creates a new container installation from scratch in a directory of your choice. Existing configurations require that the user creates a valid configuration directory and points Cargo to it.
Support Matrix
Java |
Ant |
Maven2 |
IntelliJ IDEA |
Netbeans |
---|---|---|---|---|
|
|
|
|
|
Java API
There are different ways of using an existing configuration:
- By directly instantiating the configuration matching your container. For example:
[...] Configuration configuration = new ResinExistingLocalConfiguration("target/resin3x"); [...]
- By using the
DefaultConfigurationFactory
which automatically maps the right implementation for the container you're using. For example:
[...] ConfigurationFactory factory = new DefaultConfigurationFactory(); Configuration configuration = factory.createConfiguration("resin3x", ContainerType.INSTALLED, ConfigurationFactory.EXISTING, "c:/apps/resin-3.0.9"); [...]
Ant Task
Example:
<cargo containerId="resin3x" [...]> <configuration type="existing" home="c:/apps/resin-3.0.9"/> [...] </cargo>
Maven2 Plugin
[...] <container> <containerId>resin3x</containerId> [...] </container> <configuration> <type>existing</type> <home>c:/apps/resin-3.0.9</home> </configuration> [...]