Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


The configuration files are the files to add to your container's configuration. It is internally used by some containers and is accessible for you can to add extra files.


This feature is only available for local containers


In some cases, it is necessary to enrich your container configuration with extra files. This can be done using Cargo's configFiles option, accessible via the Cargo APIs.

The advantage of using this option is that it can replace configuration properties in your files: simply use, for example, @argo.servlet.port@ to have it replaced with the port on which the Servlet/JSP container is listening to.

Careful with binary files!


If you want to inject binary configuration files (JAR files, for example), you should use setFileProperty (instead of setConfigFileProperty) with the Java API and <files> and <file> (instead of <configfiles> and <configfile>) with the Maven2/Maven3 plugin.

You might for example want to add the advanced login configuration to your JBoss instance.

Example using the Java API


The method's name is setConfigFileProperty rather than addConfigFileProperty; but it actually adds files to the configFiles list.

Example using the Maven 2 plugin

  • No labels