On Mon, 2002-10-28 at 22:40, Peter M. Goldstein wrote: > > Folks, > > Can anyone point me to a quick discussion of the assorted Avalon > containers?
http://jakarta.apache.org/avalon/framework/reference-containers.html note it is a bit out-of-date. phoenix - stable, standalone, very feature-rich. Biggest development community. ecm - stable, embedded, not a very nice design in most people's opinions. Lacks dependency tracking. fortress - alpha but nearing release quality and status. Could be dubbed ecm 2, and is mostly backwards compatible. Embedded, offers lifecycle extension support and other neat stuff. Not as solid a meta model as phoenix or merlin (yet) merlin - merlin2 predecessor stuff no-one but Stephen's clients use IIUC merlin2 (assembly package in excalibur cvs) - alpha. originally based on phoenix, providing additional smart dynamic features and an alternative meta model, embeddable & standalone, though lacks phoenix's management capability and some other features. tweety - beta. education only. No features. myrmidon - alpha. over at ant. Don't think there's a lot going on here atm plexus - alpha. over at zenplex.org. Might be core of turbine 4. Basically crossover between tweety and fortress atm. Simple but usuable. eob - alpha? can't say much, really. over at sourceforge. phoenix, ecm, fortress and plexus provide full support for avalon framework, minus the Re* interfaces (which aren't supported anywhere). Phoenix provides support for the phoenix metamodel. Fortress has limited metamodel support IIUC. Merlin has a metamodel similar to the phoenix metamodel, but currently the two are incompatible. ECM has no formal meta model to speak of. Phoenix knows what to do with .sars (Server application archives) and .bars (block application archives), as does merlin. The other containers have no such concept. There are more extensive writeups in the -dev and -user archives. atm, I recommend people develop using either phoenix or ECM. Future alternatives like fortress and merlin2 will probably offer a high level of support for apps developed using the more 'established' containers. cheers, Leo -- To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
