Component Constructors need to be public for PicoContainer to manage them. This is obvious when converting components that are package-private classes.
We would like some feedback from the reader, please.
Is the Five minute introduction enough as an overview of PicoContainer and do we need to go into the details of components, containers and lifecycle?
I think that the example nicely ilustrates how the container works. I have a question though: How would you peel lemon, orange, and banana? Since you register apple in the container you will be always getting apple unless you change the component implementation.
Available components? The "Picosphere?"
Design issues
We would like some feedback from the reader, please.
Is the Five minute introduction enough as an overview of PicoContainer and do we need to go into the details of components, containers and lifecycle?
I think a short definition would be good. If the reader wants more detail, then see the javadocs?
Do you mean a short definition of each of the concepts and then references to the JavaDoc? Sounds like a good idea.
Exactly.
I think that the example nicely ilustrates how the container works. I have a question though: How would you peel lemon, orange, and banana? Since you register apple in the container you will be always getting apple unless you change the component implementation.
You can use ComponentAdapter and Parameter to construct with an exact Peelable
How is this component-based design better than something else? What types of real applications would choose this design and why?