Design Rational

Before taking the decision to implement a new microkernel I took a look at the following:

My main requirements for a kernel framework are:

  • Ease of use:
    • File (XML) configuration should be optional
    • Components should not have to inherit classes or implement methods
    • Component persistence should be an integral part of the kernel
  • Ease of implementation:
    • Wherever possible use existing components
    • Wherever possible use standards
  • Support LifeCycle methods (init, start, stop, destroy)
  • On startup restore state of all persistent components

The current implementation is an experiment in this direction. If you have ideas or suggestions please share them on the mailing list.

[MX - HOME] [Architecture] [Kernel] [Persister] [ClassLoader] [Entry] [RepositoryManager] [Design Rational] [Adapters] [Utils] [Services] [Quick Start] [Current state & TODO] [Links] [License]