#2 User cannot specify method dispatch order

[Jens Engel]

VERSION: 0.4

It is currently not possible for a user to specify the
method dispatch order.

The message dispatch order within a container is
currently determined by the component.id attribute and
the internal hash ordering of keys.

Method dispatch ordering is or can be important for the
start() and stop()/dispose() methods that initialize and
finalize the container.

EXAMPLE:
container:A := ( C, B, A )
# -- EXPECT:
>>> A.start()
C.start called
B.start called
A.start called

# -- ACTUALLY (not verified, but experienced as similar
order in another case, not the specification ordering in
the XML file):
>>> A.start()
A.start called
B.start called
C.start called

DESIRED FEATURE CHANGE:
The most natural way would be to specify the order is by
using the component ordering in the container
specification (XML file).

NOTE:
Other, more sofisticated methods (like order index
specification, before/after spec. etc.) may be
necessary/usefull in the future.