2.2.6.3. StandaloneContainer

In the same way as the PortalContainer the StandaloneContainer takes over the configuration of the RootContainer. After that our configuration gets a little bit more tricky because standalone containers can be initialized using an URL. This URL contains a link to an external configuration. As you probably never need a standalone configuration you can safely jump over the remaining confusing words of this section.

After taking over RootContainer's configuration, there are three cases which depend on the URL initialization, :

Independent configuration by URL No other configuration file is taken in consideration. The configuration provided by the URL is used without any default configs. That means that the container creates a new empty hashtable and not any bit of previous configuration is used. Apply the following code to do this:
```
StandaloneContainer.setConfigurationURL(containerConf);
```
Additional configuration by URL The StandaloneContainer is initialized very similar to the PortalContainer, but the last step is slightly different. A configuration file that is provided by the URL is used to replace some of the service configurations.The code looks like this:
```
StandaloneContainer.addConfigurationURL(containerConf);
```
1. Take over the configurations of the RootContainer
2. Default StandaloneContainer configurations from JAR files (folder /conf/portal/configuration.xml)
3. Web application configurations from WAR files (folder /WEB-INF/conf/configuration.xml)
4. Configuration from added URL containerConf overrides only services configured in the file
File based configuration No URL is involved, in this case the sequence is:
1. Take over the configurations of the RootContainer
2. Default StandaloneContainer configurations from JAR files (folder /conf/portal/configuration.xml)
3. Web applications configurations from WAR files (folder /WEB-INF/conf/configuration.xml)
4. External configuration for StandaloneContainer services, it will be found at $user_home/exo-configuration.xml. If $user_home/exo-configuration.xml doesn't exist and the StandaloneContainer instance obtained with the dedicated configuration classloader the container will try to retrieve the resource conf/exo-configuration.xml within the given classloader (user_home is your home directory like "C:/Documents and Settings/Smith").