Package io.micronaut.context.annotation


package io.micronaut.context.annotation
Contains core annotations related to Dependency Injection and the Bean Container.
Since:
1.0
Author:
graemerocher
  • Class
    Description
    A repeatable annotation that allows defining multiple AliasFor definitions.
    Allows specifying an annotation member alias.
    Qualifier that can be used on a bean to indicate it should match any qualifier or on a injection point to indicate it should match any bean.
    Annotation used to configure a bean.
    Bean properties configuration annotation.
    The access type for bean properties.
    Visibility policy for bean properties and fields.
    An annotation indicating that a bean can be loaded into the Bootstrap Context.
    A configuration is a grouping of bean definitions under a package.
    An annotation applicable to a field or method of a ConfigurationProperties instance that allows to customize the behaviour of properties that are builders themselves.
    Allows injecting configuration values into a constructor or method based on the parameter names.
    Defines a singleton bean whose property values are resolved from a PropertyResolver.
    A meta annotation for use with other annotations to indicate that the annotation reads configuration.
    Context scope indicates that the classes life cycle is bound to that of the BeanContext and it should be initialized and shutdown during startup and shutdown of the underlying BeanContext.
    Annotation used to indicate the annotated class participates in the application context building phase.
    An annotation to apply to an interface to indicate which implementation is the default implementation.
    A meta annotation that can be applied to another annotation to specify a fallback scope of no scope is specified by the user for a bean.
    This annotation allows driving the production of Bean definitions from presence of other bean definitions.
    This annotation allows driving the production of Bean definitions from either configuration or the presence of another bean definition
    Annotation applied to the method or type indicating that a ExecutableMethod should be produced for this method.
    A factory is a Singleton that produces one or many other bean implementations.
    Allows importing an already compiled set of beans, placing any generating beans relative to the class where the import annotation is defined.
    Infrastructure scope represents a bean that cannot be overridden or replaced because it is critical to the functioning of the system.
    An annotation that can be declared on a constructor or method parameter that indicates that the injected bean should be destroyed after injection completes.
    Excludes a member of an annotation type (such as a qualifier type or interceptor binding type) from consideration when the container compares two annotation instances.
    A hint annotation that can be added to Bean definitions or Executable methods to indicate that they can be initialized in parallel with the application context.
    Specifies that an argument to a bean constructor is user provided and a ParametrizedBeanFactory should be generated.
    A Qualifier that indicates that this bean is the primary bean that should be selected in the case of multiple possible interface implementations.
    A property that can be contained within a PropertySource or used generally throughout the system.
    An annotation that can be used on either the main class or a test to provide additional hard coded property values to the Environment.
    Prototype scope is a non-singleton scope that creates a new bean for every injection point.
    Deprecated.
    Use the typed member of the Bean annotation instead
    Allows a bean to specify that it replaces another bean.
    For specifying multiple requirements.
    Expresses a requirement for a bean or Configuration.
    Used to express an operation system family.
    Used to express a required SDK version.
    Counter part to Primary that allows reducing the priority of a given bean for the purposes of dependency injection.
    Allows restricting injection by type.
    Allows configuration injection from the environment on a per property, field, method/constructor parameter basis.