Cargo : Standalone Local Configuration This page last changed on Mar 08, 2006 by vmassol. ### Definition Configures your container in a specific directory ### Explanation The 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. ### Example using the Java API There are different ways of using a standalone configuration: By directly instantiating the configuration matching your container. For example:
    LocalConfiguration configuration =
        new Resin3xStandaloneLocalConfiguration(new File("target/myresin3x"));
By using the `DefaultConfigurationFactory` which automatically maps the right implementation for the container you're using. For example:
    ConfigurationFactory configurationFactory =
        new DefaultConfigurationFactory();
    LocalConfiguration configuration =
        (LocalConfiguration) configurationFactory.createConfiguration(
            "resin3x", ConfigurationType.STANDALONE);
### Example using the Ant API
    <cargo containerId="resin3x" [...]>
      <configuration hint="standalone" dir="target/resin3x"/>
      [...]
    </cargo>
### Example using the Maven 2 plugin
    [...]
    <container>
      <containerId>resin3x</containerId>
      [...]
    </container>
    <configuration>
      <type>standalone</type>
      <dir>target/resin3x</dir>
    </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 Mar 22, 2006 15:28