Cargo : Standalone Local Configuration
This page last changed on Mar 17, 2007 by vmassol.
DefinitionConfigures your container in a specific directory ExplanationThe standalone configuration allows configuring your container so that it is setup to start in a directory you choose (see the configuration page for more general explanations). Whenever you start a container which uses a standalone configuration, Cargo will delete the configuration directory in order to reinstall a clean standalone configuration. Thus all deployables that would have been previously deployed to this configuration will be removed. Of course, they will be deployed again if you have added them to the configuration (see Static Deployment). The reason for this behavior is reproducibility which is for example very useful for automated testing. If you wanted to keep a generated configuration you could ask Cargo to generate a standalone configuration once and then consider it an existing configuration. Support Matrix
Java APIThere are different ways of using a standalone configuration:
LocalConfiguration configuration = new Resin3xStandaloneLocalConfiguration("target/myresin3x");
ConfigurationFactory configurationFactory = new DefaultConfigurationFactory(); LocalConfiguration configuration = (LocalConfiguration) configurationFactory.createConfiguration( "resin3x", ContainerType.INSTALLED, ConfigurationType.STANDALONE); Ant Task<cargo containerId="resin3x" [...]> <configuration type="standalone" home="target/resin3x"/> [...] </cargo> Maven2 Plugin[...] <container> <containerId>resin3x</containerId> [...] </container> <configuration> <type>standalone</type> <home>target/resin3x</home> </configuration> [...] Note that the standalone configuration is the default for the Maven 2 plugin so specifying only the following would also work: [...] <container> <containerId>resin3x</containerId> [...] </container> [...] |
![]() |
Document generated by Confluence on Jun 02, 2010 22:47 |