Annotations

Metro provides five optional annotations supporting:

1. association of runtime policy to a class
2. association of additional meta data

These annotations are summarasied under the following table.

Activation	Used to associate an explicit activation policy with the class.
Component	Used to declare a default component name, lifestyle policy, collection policy, an explicit lifecycle graph, and/or alternative runtime handler uri or classname.
Context	Annotation used to mark an interface as compliant with the Metro Context contract (in effect a bean like instance built and populated by the container delivering the component dependencies).
Parts	Annotation used to mark an interface as compliant with the Metro Parts contract (though which the internal structure of a component may be established).
Services	Annotation used to to declare the service classes that a component is publishing towards other components.