- Is Fortress Dead?
No. Fortress 1.1 was just released in early 2004. We are working on a unified Avalon platform (with a single container project) which will mean Fortress, like the other current containers, will be phased out. A migration path will be provided. Until then, current Fortress users can continue using the container without concerns. New users of Avalon are encouraged to consider Merlin before adopting Fortress however.
- When should I use ECM instead?
Never. Fortress supports all of ECMs features, is better designed, more extensible, etc. The only reason to use ECM is because you are already using it and don't want to upgrade.
- Component assembly in Fortress?
- When should I use Merlin instead?
- Merlin is not (yet) as flexible and light-weight as Fortress. So if your need is primarily a light-weight container without all the bells and whistles, Fortress may better suite you. If you need a command-line driven (embedding is supported in Merlin, but not the primary focus) server framework, that does automatic dependency resolution, handles central component repositories, enhanced security (under development) and dozens of other advanced features, Merlin is your choice. You can even embed Fortress solutions in Merlin if you like, the other way around is trickier.
What are the Fortress runtime dependencies?
- avalon-framework : 4.1.5
- logkit : 1.2.2
- commons-collections : 2.1 (NOT included in fortress-container-complete)
- commons-beanutils : 1.6.1
- concurrent : 1.3.1 (NOT included in fortress-container-complete)
- excalibur-instrument : 1.0
- excalibur-instrument-manager : 1.0
- excalibur-instrument-manager-interfaces : 1.0
- excalibur-event-api : 1.1
- excalibur-event-impl : 1.1
- bcel : 5.1
- excalibur-logger : 1.1
- excalibur-sourceresolve : 1.1
- excalibur-lifecycle : 1.0
- xml-apis : 2.0.2
These jars can be found on a maven repository like http://ibiblio.org/maven