SetterConfiguration:
- add type based removal of setters.
- add values(Class aType) method for selecting a setter. 
- add add(Class aType) method for selecting a type. 
- verify that superclass setters are also taken into account.



opzoeken waar de provided interfaces van de scope gebruikt worden, als het
goed is nog nergens. Scope moet een Component worden en publiceren van een 
interface leidt tot een nieuw provided interface.

Component infrastructure
* support simple component
  - requires through constructor
  - provides through getters
* optional start and stop methods
* giving names to a component must be optional
* support for cached components and non-cached components.


- Annotaties definieren


@Component
  class MyComponent {  

  public MyComponent(Def aArg, Ghi aArg2) { 
  }

  @Provided(name = "name")
  public Xyz getXyz();

  @Start
  public void myStart(); // Unlike the component
}

- Algemene classes maken die de constructor, start method, en 
  methodes  identificeren om de component als Component te benaderen. 
  in een object, samen met een wrapper die deze info gebruikt om het
  object als Component te exportern. 
  Er moet ook een wrapper zijn voor reeds geinstantieerde  objecten.

- wrapper maken die geannoteerde classes interpreteert en via de eerdere
  wrapper het object ontsluiten als component. 
  Zowel geinstantieerde objecten als classes ondersteunen. 

- add support for private setters.
- add support or exposing provided services 
  - superclass or interface of the concrete type instead of the concrete type
    or not based on the concrete type at all. 
  - based on getters. 
- add support for field injection. 

- add support for annotation based configuration instead of API-based

- add support for type conversions. 

- add support for multiplicity. 

- add support for aggregating multiple servicss. 

- add support for explicitly configuring which provided interface of 
  a container is provided by which internal service. 

- do not use equality but use logic for matching external required and
  provided interfaces of a container. 

  e.g. a service T provided by a container can be provided by a service 
  U that provides subclasses of the provided interfaces of T

  a service T required by a component inside a container is covered
  by stronger requirements for subclasses of T. 

- separate logic for connecting required and provided interfaces 
  through a general graph model of the application. 
  Then use generic filters, validations, and graph traversal APIs 
  to implement the current functionality in the container.