Differences between revisions 1 and 2
Revision 1 as of 2005-03-22 05:40:07
Size: 882
Editor: anonymous
Comment: missing edit-log entry for this revision
Revision 2 as of 2009-09-20 23:16:38
Size: 884
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
After reading through any introducing document like [http://jakarta.apache.org/avalon/developing/index.html Developing with Avalon] you probably want to know more especially how you can use the concepts introduced by Avalon. There is so much talk about ''inversion of control'', but if you don't have the control then who After reading through any introducing document like [[http://jakarta.apache.org/avalon/developing/index.html|Developing with Avalon]] you probably want to know more especially how you can use the concepts introduced by Avalon. There is so much talk about ''inversion of control'', but if you don't have the control then who

What is a Container in Avalon?

After reading through any introducing document like Developing with Avalon you probably want to know more especially how you can use the concepts introduced by Avalon. There is so much talk about inversion of control, but if you don't have the control then who will?

The answer to this and many more questions is the Container: Its responsibility is to handle all the requests the components signal through their interfaces. Containers come in many different flavors and it is not always easy to find the right one for you: you have to look at the ProsAndConsOfContainers.

On the other hand there is the concept of an application server which is more concrete concept. AvalonPhoenix is such an application server and is ready to act as a Container for your application.

AvalonFAQ/WhatIsAContainer (last edited 2009-09-20 23:16:38 by localhost)