Peter, >I've been quietly reading the user and dev lists for a week or two and >am now getting my brain round my first trivial components. Many thanks >to Berin for "Developing with Apache Avalon". It makes a lot of sense >and has helped considerably in understanding the principals. > >I have struggled a bit with the 'ContainerComponent' and >'ComponentManager' part of 'Implementing the Dream'. I am only slowly >beginning to see how these actually fit into an application. It is >relatively clear what they do, I think, just not clear to my very slow >mind what best practice is in using them. > >If a re-usable component itself uses components, in addition to >implementing its work interface it needs to also be a container to be >able to obtain the references to the components it needs. Is this >correct? > >I had wondered whether the 'work interface' should be kept separate from >the 'container', but I think I am right in saying that this is not what >the framework intends. > > >If someone could either confirm my thoughts or put me on the right track >I would be most grateful. > > I find it best to not think of the contaner's impl (I use Phoenix mostly) and just to think of the hosted component. The container just cycles through the lifecycle methods in order and the component starts up.
http://jakarta.apache.org/avalon/framework/reference-the-lifecycle.html >One small point that confused me is the javadoc for the Serviceable >interface. Am I correct that line 11 of the source should start 'A >Serviceable' and not 'A Composable'? > > Done by another. - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
