Specifies how the container is configured
A Configuration specifies how the container is configured (logging, security, data sources, location where to put deployables, etc).
|There are no images attached to this page.|
There are 2 main types of Configurations:
- Local Configuration: You use a local configuration when you're using a Local Container. There are 2 local configuration types: Standalone Local Configuration and Existing Local Configuration.
- Runtime Configuration: You use a runtime configuration when you want to access your container as a black box through a remote protocol (JMX, etc). Whereas a local configuration allow you to tune almost all aspects of a container, a runtime configuration only support configuring container properties that can be modified from a distance.
(TODO: update the section below as it's no longer exact)
The Cargo API allows you to plug your own custom configuration implementation. The only requisites is that the implementation must implement
ContainerConfiguration and have a
CustomConfiguration(URI home) constructor (for local containers,
home is the URI pointing to directory from where to start the container; for remote containers,
home is the URI required to manipulate the container).
You can then register your configuration against the
DefaultConfigurationFactory class. It's optional and only required if you want to let users use the
DefaultConfigurationFactory class to instantiate your configuration. You would write:
new ConfigurationType("customhint") is to create a type of configuration, used to differentiate your configuration from other existing ones associated with the container represented by its id. You could of course implement an existing type such as