Does the Aegis context really have to be a map, as opposed to just
having specific properties? It doesn't have very many, and it seems to
me that they would be easier to configure with (e.g.) Spring if they
were just ordinary properties.

Reply via email to