What I need to do is write a servlet app, and I would like to write it in a component-oriented style (your docs about this are much improved over a year ago, btw - good job). From the faq, I noted that for such a situation, fortress was recommended.
So, am I to assume that the excalibur-fortress-1.0.zip plus logkit plus framework is all I need?
Not exactly: you will also need an xml parser (included in all recent JREs though); the BCEL library is needed if you run on a 1.2 JRE (not for later versions), you need the jakarta commons-collections package and the util.concurrent package from Doug Lea.
Grab these jars:
http://www.ibiblio.org/maven/avalon-framework/jars/avalon-framework-4.1.4.jar http://www.ibiblio.org/maven/excalibur-fortress/jars/excalibur-fortress-complete-1.0.jar http://www.ibiblio.org/maven/commons-collections/jars/commons-collections-2.1.jar http://www.ibiblio.org/maven/concurrent/jars/concurrent-1.3.2.jar http://www.ibiblio.org/maven/bcel/jars/bcel-5.0.jar http://www.ibiblio.org/maven/xml-apis/jars/xml-apis-1.0.b2.jar http://www.ibiblio.org/maven/xerces/jars/xerces-2.3.0.jar
also get the src.zip from the excalibur-fortress distribution, as well as the src zip from the avalon-framework distribution. Get all that hooked up inside your favorite IDE (I find it very useful to be able to do a "Go to declaration" when looking stuff up :D).
Then, take a look at the servlet example that is provided and take it from there.
That is one way. Another way (which I usually recommend to friends just getting started with avalon and COP and who find it difficult "getting started") is to take a look at keel framework (www.keelframework.org) and get started with their three-kitchen-sinks-pick-one distribution. It comes prepackaged with pretty much everything you need, and then a lot more is pluggable. It's also a *pretty big* download though.
From their FAQ: -------------------- Q: Which version of Avalon and which container do we use?
A: The latest stable Avalon, and we use Fortress.
Q: Why should I use keel instead of just using Avalon?
A: Keel uses avalon as its base, but keel provides several benefits over "straight" Avalon. For starters, keel has selected different avalon components and already configured them for you-- at task that can be quite daunting for an avalon beginner. Secondly, through the use of "models" and "services", keel attempts to provide a more simplified programming model and several default implementations of different keel services. Keel's focus is usability, code reuse and simplicity. In that vein, keel has chosen to use Avalon to reap the fantastic benefits such as inversion of control and separtation of concerns that avalon provides. However, keel provides structure, code, example applications, installation tools, deployment tools, documentation and services that "extend" the basic features provided in a "vanilla" avalon installation.
--------------------
the existence of keel is one reason I don't feel the need to provide a fortress-getting-started.war :D
cheers!
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
