leosimons 2002/11/15 12:29:43 Modified: . tabled-discussions.txt Log: adding some stuff here so I can remember what I want to put in a wiki if we get one Revision Changes Path 1.2 +27 -0 jakarta-avalon-excalibur/tabled-discussions.txt Index: tabled-discussions.txt =================================================================== RCS file: /home/cvs/jakarta-avalon-excalibur/tabled-discussions.txt,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- tabled-discussions.txt 23 Jul 2002 14:38:57 -0000 1.1 +++ tabled-discussions.txt 15 Nov 2002 20:29:43 -0000 1.2 @@ -42,3 +42,30 @@ component's configuration so that we can reinitialize ourselves properly the next time. + +META / INFO MODEL +----------------- +We need a model to represent component metadata. Some ideas on +this have been codified in the containerkit, info, meta and +xfc modules. See there for more information. +It would be beneficial to share as much of any such model across +different containers as possible to make component portability +easy. + + +ONE CONTAINER TO RULE THEM ALL +------------------------------ +There has been (and probably always will be) talk about creating +a single container that can take on the roles of all current +ones. There's also been talk about creating a "reference +implementation" of a container. If we were to succeed in this it +would make things more transparent for our users. + + +AVALON 5 +-------- +There was talk about and a proposal about a new non-backwards- +compatible version of avalon framework under the name "avalon 5"; +there's a proposal on this in the jakarta-avalon cvs attic. +Mostly this would involve small changes only. Hence it isn't +really neccessary and has been put on hold indefinately. \ No newline at end of file
-- To unsubscribe, e-mail: <mailto:avalon-cvs-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-cvs-help@;jakarta.apache.org>
