> -----Original Message----- > From: Dorninger Bernhard [mailto:[EMAIL PROTECTED]
> As far as i can see, Avalon will now be hosted and maintained by the > Excalibur project, whereas Merlin goes Metro on DPML.net. Unfortunately, > this information is only available in mailing lists and is not reflected > on the project websites (yet?). Yet. :) I'm working on it. My first attempt at getting the redirects working didn't pan out. A "closed" message is at http://avalon.apache.org/closed.html > My question here is: What is the difference/are the different goals of > Fortress and Merlin? Can someone please drop a short notice about that > question? Metro seeks to be a full service/component deployment platform. In a sense, it competes with J2EE. Fortress is designed to be a small container that you embed in your application, more along the lines of Pico or Nanocontainer. Another way to think of it is that you run your application in Metro while you run Fortress in your application. There are exceptions to this rule (of course), but that's the general idea. > Does fortress support hot deploy of components? No. But then again, neither does Merlin/Metro. I'm not sure if Loom or Plexus (other Avalon-based containers) do. I don't think so, though. jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
