> There are at least the following distinct subjects that I see: > > * A special container established as peer to the current root container > that is provided with the SPI classloader and contains components > intended for use as a part of the container system - these components > would not be available to classic components - instead thay are > specifically established to service container sub-sytems. >
perfect! > > * An appliance listener/event model that enables registration of > listeners that listen to appliance lifecyle events (and sub-stage event). > greate! I would like to start collecting all ideas and bring that in a structure. My idea here would be to define a sort of architecture. Means: The service you are talking about I would like to call "core system services (CSS)" which are part of "primary system services (PSS)". Other PSS could be security, persistence, meta info etc. In addition to that, I would like to see "optional system services" like printing, messaging etc. Most of those system services should be offered through contexts. To cluster requirements like that would give a clear picture who could implement what and about the direction Merlin will go. Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
