3.4 Components

Added by Jon Tirsen, last edited by Mauro Talevi on Jan 25, 2006  (view change)

Authors: paul, Aslak Hellesøy, Jon Tirsen

Overview


A pico compatible component is a public class that, for PicoContainer at least, is characterized in the following ways:

  • Does not have to implement or extend anything (unless they want to participate in the default lifecycle, see 3.3 Lifecycle).
  • Declares one or more public constructors where the arguments are the component's dependencies and configuration.
  • Reusable in many different deployment scenarios (root, Servlet, Applet, ClassLoaders etc).

Labels

 
(None)

Comments (3)

 

  1. Feb 22, 2004

    Miguel A Paraz says:

    In particular private or packageprivate classes can not <i>be</i> components.

    In particular private or package-private classes can not <i>be</i> components.

  2. Feb 23, 2004

    Jon Tirsen says:

    Miguel, what is the difference? Do you feel the current phrasing is wrong?

    Miguel, what is the difference? Do you feel the current phrasing is wrong?

  3. Mar 29, 2004

    steve_molitor says:

    Just to be pendantic, I guess the difference is that you could write a class lik...

    Just to be pendantic, I guess the difference is that you could write a class like this:

    /* package-private */ class Foo {
    public Foo() {}
    }

    Foo declares a 'public' constructor, but since it's package private, it can't be a component, correct?

    Steve