Turbine provides a number of annotations to inject dependencies into your actions,
screens and layouts. All Assemblers
that is, all modules of type
Action
, Screen
, Layout
, Page
,
Navigation
and ScheduledJob
as well as all
Valves
in the pipeline support the injection of services,
configurations and loaders. This relieves you from the burden of looking
them up at runtime and thus simplifies and accelerates the code.
@TurbineService
gets injected an instance of this service at the time the instance
of the class is created. The field should have the type of the service
interface like in the following two examples:
SERVICE_NAME
and then ROLE
in the type class of the field to retrieve the service name. If none
of them can be found, the fully qualified class name of the
service interface is used to look up the service.
@TurbineConfiguration
gets injected an instance of the Turbine configuration object at
the time the instance of the class is created. The field should have
the type Configuration
@TurbineLoader
gets injected an instance of the specified Loader
at
the time the instance of the class is created. The field should have
the type of the loader.
@TurbineActionEvent
is associated to a named action event. The annotation parameter
is required and defines the name of the event. See the
Action Events Howto
for usage and examples.
module.cache
to true
in
TurbineResources.properties
.