Should the agent not be able to start due to configuration problems,
then the agent must still be stopped, thus state changes in this context
should not lead to exceptions when shutting down.
ResourceMap and OrderMap are kept in a StrolchRealm object for each
realm which is configured. This is transparent for the user. When no
realms are defined then the 'defaultRealm' is configured where all
methods without a realm parameter use this realm.
Once a realm is configured, the defaultRealm must be configured if it
is still to be used at runtime.
Tests make sure realms work, for both transient, and empty situations.
Cached agent mode is next to be implemented
Now they are not components, now there is an ElementMapHandler which
is the component and the OrderMap and ResourceMap can be retrieved from
the ElementMapHandler
Currently querying in memory works, now we need the visitor pattern to
abstract away the details of the in memory querying mechanism and allow
other querying mechanisms
The container how sets its own state once it has changed the state of
the components. Now the DefaultStrolchPrivilegeHandler checks that the
container has started before allowing any methods to be called.
This might still be too restrictive in that when the container is
stopped, that then an admin can not log in and perform any actions, but
this can then be changed when needed.
- We now have a container which can be configured with components, can
be setup, started, stopped and destroye.
- Missing is still the implementation of the dependencies.