Pawel, Good questions.
Things have been a little turbulent around here as we are trying to work out the details of moving forward with a single platform. Some individuals have stepped down from the PMC and others have decided to work on similar container projects outside of Avalon. I've considered setting up an IRC meeting for all those interested in hammering out more of the details for Avalon's next step. If this works out, we'll probably have it next week. > -----Original Message----- > From: Pawel Karendys [mailto:[EMAIL PROTECTED] > > 1) Which containers are positively being deprecated? ECM, Fortress, and Phoenix. ECM is already deprecated. Fortress was its replacement. Phoenix development has been halted for a while. Those not interested in Merlin or who have a heavy investment in Phoenix should take a look at Loom. (http://loom.jcontainer.org/) Fortress is being cleaned up and stabilized so that it can safely retire. NOTE: These containers are still stable and usable. I prefer to say that we will freeze active development here at Avalon (someone else could take them up -- they are open source). Bug fixes and submitted patches would still be welcome. We'll then work on a single platform and once that is stabilized we will then have a good target to start working on legacy support, migration tools, etc. > 2) What is the current offering for stand-alone and web (or EJB container) > embedded applications? Probably, it would be nice to have one container > with its configuration determining how light-weight one wants to "travel"? There is still work going on in this area. Most of this is centered around the "facilities" feature of Merlin which allows for special components to extend the basic container features. Work is underway on HTTP, JMS, and JMX facilities. I'd like to see an AltRMI facility too. This would be mostly for stand-alone applications. In the embedded Merlin area we still have some work to do. As far as I am concerned this has to do with starting up Merlin without the use of a repository or with "embedded" repositories. > 3) A general summary of where we're going with this project would also > help. http://marc.theaimsgroup.com/?l=avalon-dev&m=107997042911859&w=2 I hope that helps. J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
