Uses of Package
io.helidon.pico.api
Packages that use io.helidon.pico.api
Package
Description
NĂma WebServer module, combining common server API, HTTP API and HTTP/1.1 API to create a server.
The Pico API provide these annotation types that are typically used at compile time
to assign special meaning to the type.
Pico's config-driven-service API.
Internal tooling for the pico maven plugin.
Pico runtime services.
Pico SPI.
Pico testing support.
Pico Tools.
Tools SPI support.
-
Classes in io.helidon.pico.api used by io.helidon.nima.webserverClassDescriptionThe
Contractannotation is used to relay significance to the type that it annotates. -
Classes in io.helidon.pico.api used by io.helidon.pico.apiClassDescriptionTracks the transformations of
ServiceProvider'sActivationStatusin lifecycle activity (i.e., activation startup and deactivation shutdown).Log entry for lifecycle related events (i.e., activation startup and deactivation shutdown).Provide a means to query the activation log.Request to activate a service.Represents the result of a service activation or deactivation.The activation status.Activators are responsible for lifecycle creation and lazy activation of service providers.This is the bootstrap needed to provide toPicoinitialization.For internal use only to Helidon.Combines theServiceInfocriteria along with theInjectionPointInfocontext that the query applies to.TheContractannotation is used to relay significance to the type that it annotates.Request to deactivate aServiceProvider.DeActivators are responsible for lifecycle, transitioning aServiceProviderthrough itsPhase's, notably including anyPreDestroymethod invocations, and finally into the terminalPhase.DESTROYEDphase.Describes aQualifiertype annotation associated with a service being provided or dependant upon.The fluent builder.Represents a perServiceInfomapping ofDependencyInfo's.Aggregates the set ofInjectionPointInfo's that are dependent upon a specific and commonServiceInfodefinition.Abstractly describes method or field elements of a managed service type (i.e., fields, constructors, injectable methods, etc.).The access describing the target injection point.The kind of injection target.A lifecycle activation event.Represents an injection exception.Describes a receiver for injection - identifies who/what is requesting an injection that needs to be satisfied.Provides ability to contextualize the injected service by the target receiver of the injection point dynamically at runtime.Used to perform programmatic activation and injection.The strategy the injector should attempt to apply.Provides optional, contextual tunings to theInjector.Implementors of this contract must beNamedaccording to theInterceptedannotation they support.Represents the next in line for interception, terminating with a call to the wrapped service provider.Used byInterceptor.Pico Metrics.Provides a means to identify if the instance is optionally named.Forms a progression of full activation and deactivation.A general exception indicating that something failed related to Pico.An exception relative to aServiceProvider.Abstract factory for all services provided by a single Helidon Pico provider implementation.This is the configuration that the Pico service provider uses internally.Represents thePostConstructmethod.Represents thePreDestroymethod.Represents a tuple of the Qualifier and optionally any value.Implementors of this contract are capable of resetting the state of itself (i.e., clears cache, log entries, etc.).Responsible for binding service providers to the service registry.Describes a managed service or injection point.Basic service info that describes a service provider type.Criteria to discover services.Responsible for registering the injection plan to the services in the service registry.The binder builder for the service plan.Provides management lifecycle around services.An extension toServiceProviderthat allows for startup binding from aPico$$Application, and thereby works in conjunction with theServiceBinderduring pico service registry initialization.The service registry. -
Classes in io.helidon.pico.api used by io.helidon.pico.configdriven.runtimeClassDescriptionA receiver of events from the
Servicesregistry and providers held by the service registry.Activators are responsible for lifecycle creation and lazy activation of service providers.Combines theServiceInfocriteria along with theInjectionPointInfocontext that the query applies to.DeActivators are responsible for lifecycle, transitioning aServiceProviderthrough itsPhase's, notably including anyPreDestroymethod invocations, and finally into the terminalPhase.DESTROYEDphase.A lifecycle activation event.Describes a receiver for injection - identifies who/what is requesting an injection that needs to be satisfied.Provides ability to contextualize the injected service by the target receiver of the injection point dynamically at runtime.Forms a progression of full activation and deactivation.Abstract factory for all services provided by a single Helidon Pico provider implementation.Represents a tuple of the Qualifier and optionally any value.Implementors of this contract are capable of resetting the state of itself (i.e., clears cache, log entries, etc.).Describes a managed service or injection point.Criteria to discover services.Provides management lifecycle around services.An extension toServiceProviderthat allows for startup binding from aPico$$Application, and thereby works in conjunction with theServiceBinderduring pico service registry initialization.Instances of these provide lists and maps ofServiceProviders. -
Classes in io.helidon.pico.api used by io.helidon.pico.maven.pluginClassDescriptionProvides aggregation of services to the "containing" (jar) module.Represents a tuple of the Qualifier and optionally any value.Provides management lifecycle around services.
-
Classes in io.helidon.pico.api used by io.helidon.pico.runtimeClassDescriptionTracks the transformations of
ServiceProvider'sActivationStatusin lifecycle activity (i.e., activation startup and deactivation shutdown).A receiver of events from theServicesregistry and providers held by the service registry.Request to activate a service.Represents the result of a service activation or deactivation.Activators are responsible for lifecycle creation and lazy activation of service providers.This is the bootstrap needed to provide toPicoinitialization.Combines theServiceInfocriteria along with theInjectionPointInfocontext that the query applies to.Request to deactivate aServiceProvider.DeActivators are responsible for lifecycle, transitioning aServiceProviderthrough itsPhase's, notably including anyPreDestroymethod invocations, and finally into the terminalPhase.DESTROYEDphase.Represents a perServiceInfomapping ofDependencyInfo's.Aggregates the set ofInjectionPointInfo's that are dependent upon a specific and commonServiceInfodefinition.The access describing the target injection point.The kind of injection target.A lifecycle activation event.Represents an injection exception.Describes a receiver for injection - identifies who/what is requesting an injection that needs to be satisfied.Provides ability to contextualize the injected service by the target receiver of the injection point dynamically at runtime.Represents the next in line for interception, terminating with a call to the wrapped service provider.Used byInterceptor.Forms a progression of full activation and deactivation.Abstract factory for all services provided by a single Helidon Pico provider implementation.Represents thePostConstructmethod.Represents thePreDestroymethod.Represents a tuple of the Qualifier and optionally any value.Implementors of this contract are capable of resetting the state of itself (i.e., clears cache, log entries, etc.).Responsible for binding service providers to the service registry.Describes a managed service or injection point.The binder builder for the service plan.Provides management lifecycle around services.An extension toServiceProviderthat allows for startup binding from aPico$$Application, and thereby works in conjunction with theServiceBinderduring pico service registry initialization. -
Classes in io.helidon.pico.api used by io.helidon.pico.spiClassDescriptionThis is the bootstrap needed to provide to
Picoinitialization.Describes a receiver for injection - identifies who/what is requesting an injection that needs to be satisfied.Abstract factory for all services provided by a single Helidon Pico provider implementation.Provides management lifecycle around services. -
Classes in io.helidon.pico.api used by io.helidon.pico.testingClassDescriptionA receiver of events from the
Servicesregistry and providers held by the service registry.Activators are responsible for lifecycle creation and lazy activation of service providers.DeActivators are responsible for lifecycle, transitioning aServiceProviderthrough itsPhase's, notably including anyPreDestroymethod invocations, and finally into the terminalPhase.DESTROYEDphase.Provides ability to contextualize the injected service by the target receiver of the injection point dynamically at runtime.Abstract factory for all services provided by a single Helidon Pico provider implementation.Implementors of this contract are capable of resetting the state of itself (i.e., clears cache, log entries, etc.).Basic service info that describes a service provider type.Provides management lifecycle around services.An extension toServiceProviderthat allows for startup binding from aPico$$Application, and thereby works in conjunction with theServiceBinderduring pico service registry initialization. -
Classes in io.helidon.pico.api used by io.helidon.pico.toolsClassDescriptionRepresents a per
ServiceInfomapping ofDependencyInfo's.Abstractly describes method or field elements of a managed service type (i.e., fields, constructors, injectable methods, etc.).The access describing the target injection point.Represents a tuple of the Qualifier and optionally any value.Implementors of this contract are capable of resetting the state of itself (i.e., clears cache, log entries, etc.).Basic service info that describes a service provider type. -
Classes in io.helidon.pico.api used by io.helidon.pico.tools.spiClassDescriptionThe
Contractannotation is used to relay significance to the type that it annotates.Basic service info that describes a service provider type.