1.4. Container configuration

1.4.1. Kernel configuration namespace
1.4.2. Understanding how configuration files are loaded
1.4.3. eXo container hot reloading
1.4.4. System property configuration
1.4.5. Variable syntaxes
1.4.6. Runtime configuration profiles
1.4.7. Component request life cycle
1.4.8. Thread Context Holder

eXo Platform uses PicoContainer, which implements the Inversion of Control (IoC) design pattern. All eXo containers inherit from a PicoContainer. There are mainly two eXo containers used, each of them can provide one or several services. Each container service is delivered in a JAR file. This JAR file may contain a default configuration. The use of default configurations is recommended and most services provide it.

When a Pico Container searches for services and its configurations, each configurable service may be reconfigured to override default values or set additional parameters. If the service is configured in two or more places the configuration override mechanism will be used.

If you are still confused, see the Service configuration for beginners section to understand the basics.

Copyright ©. All rights reserved. eXo Platform SAS
blog comments powered byDisqus