Hansa Bootstrap

A three-phased bootstrap process will take care of simplicity, flexibility and power of the system;

1. The hansa-boot.jar is a minimalistic Jar containing the non-evolutionary codebase, which must be placed either in the System Classloader (through -cp or CLASSPATH) or in the Extension Classload (not recommended). It will hold the bridging classes to the JVM, a static singleton and the necessary interfaces and exception classes. It will check for the primordial loader on the local filesystem, and if not found try to download it from the OPS4J server.
2. The primordial loader re-establishes the last known state of a running Hansa Core Runtime. If none is found, a brand new default Hansa Core Runtime will be located/discovered by searching a set of servers. The primordial loader is responsible for the management of classloaders to ensure that everything is loaded and unloaded properly. The loader is also responsible for saving the state of the Hansa Core Runtime, by listening on Events.
3. Once the Hansa Core Runtime is established, it will register itself in the Handler classes for the protocols, and register itself in the singleton Hansa class (residing in boot).