| Class and Description |
|---|
| LifecycleManager
The LifecycleManager is responsible for managing the different lifecycle phases of the server and managing the transitions
between lifecycle phases.
|
| Class and Description |
|---|
| LifecycleManager
The LifecycleManager is responsible for managing the different lifecycle phases of the server and managing the transitions
between lifecycle phases.
|
| Class and Description |
|---|
| LifecycleState
A safe facade for lifecycle manager that objects can use to monitor its own state
|
| LifecycleStateEnabled
Objects that have an associated lifecycle manager such as
FlowConstruct should
implement this interface so that the registry lifecycle manager can introspect the lifecycle state of an object. |
| Class and Description |
|---|
| LifecycleStateEnabled
Objects that have an associated lifecycle manager such as
FlowConstruct should
implement this interface so that the registry lifecycle manager can introspect the lifecycle state of an object. |
| Class and Description |
|---|
| LifecycleManager
The LifecycleManager is responsible for managing the different lifecycle phases of the server and managing the transitions
between lifecycle phases.
|
| Class and Description |
|---|
EventListener
EventListener is a marker interface that is implemented by objects wishing to receive Mule events in managed
environments, such as an EJB container. |
| LifecycleInterceptor
Allows intercepting the application of
lifecycle phases over each target object. |
| LifecyclePhase
Encapsulates the notion of a lifecycle phase i.e.
|
| LifecycleState
A safe facade for lifecycle manager that objects can use to monitor its own state
|
| Class and Description |
|---|
InitialisationCallback
InitialisationCallback is used to provide customised initialiation for more complex components. |
| Class and Description |
|---|
| LifecycleStateEnabled
Objects that have an associated lifecycle manager such as
FlowConstruct should
implement this interface so that the registry lifecycle manager can introspect the lifecycle state of an object. |
| Class and Description |
|---|
Callable
Callable is used to provide a Service with an interface that supports event calls. |
InitialisationCallback
InitialisationCallback is used to provide customised initialiation for more complex components. |
| LifecycleCallback
This callback is used to execute lifecycle behaviour for an object being managed by a
LifecycleManager The callback is
used so that transitions can be managed consistently outside of an object |
| LifecycleManager
The LifecycleManager is responsible for managing the different lifecycle phases of the server and managing the transitions
between lifecycle phases.
|
| Class and Description |
|---|
Callable
Callable is used to provide a Service with an interface that supports event calls. |
EventListener
EventListener is a marker interface that is implemented by objects wishing to receive Mule events in managed
environments, such as an EJB container. |
| Class and Description |
|---|
FatalException
FatalException can be thrown during initialisation or during execution to indicate that something fatal has
occurred and the MuleManager must shutdown. |
| Class and Description |
|---|
| LifecycleManager
The LifecycleManager is responsible for managing the different lifecycle phases of the server and managing the transitions
between lifecycle phases.
|
| Class and Description |
|---|
| LifecycleManager
The LifecycleManager is responsible for managing the different lifecycle phases of the server and managing the transitions
between lifecycle phases.
|
| Class and Description |
|---|
| LifecycleCallback
This callback is used to execute lifecycle behaviour for an object being managed by a
LifecycleManager The callback is
used so that transitions can be managed consistently outside of an object |
| LifecycleManager
The LifecycleManager is responsible for managing the different lifecycle phases of the server and managing the transitions
between lifecycle phases.
|
| LifecycleState
A safe facade for lifecycle manager that objects can use to monitor its own state
|
| LifecycleStateEnabled
Objects that have an associated lifecycle manager such as
FlowConstruct should
implement this interface so that the registry lifecycle manager can introspect the lifecycle state of an object. |
| Class and Description |
|---|
| LifecyclePhase
Encapsulates the notion of a lifecycle phase i.e.
|
| Class and Description |
|---|
| HasLifecycleInterceptor
Contract interface for an object on which a
LifecycleInterceptor can be set into |
| LifecycleCallback
This callback is used to execute lifecycle behaviour for an object being managed by a
LifecycleManager The callback is
used so that transitions can be managed consistently outside of an object |
| LifecycleInterceptor
Allows intercepting the application of
lifecycle phases over each target object. |
| LifecycleManager
The LifecycleManager is responsible for managing the different lifecycle phases of the server and managing the transitions
between lifecycle phases.
|
| LifecyclePhase
Encapsulates the notion of a lifecycle phase i.e.
|
| LifecycleState
A safe facade for lifecycle manager that objects can use to monitor its own state
|
| Class and Description |
|---|
| LifecycleState
A safe facade for lifecycle manager that objects can use to monitor its own state
|
| Class and Description |
|---|
InitialisationCallback
InitialisationCallback is used to provide customised initialiation for more complex components. |
| Class and Description |
|---|
| LifecycleState
A safe facade for lifecycle manager that objects can use to monitor its own state
|
| LifecycleStateEnabled
Objects that have an associated lifecycle manager such as
FlowConstruct should
implement this interface so that the registry lifecycle manager can introspect the lifecycle state of an object. |
| Class and Description |
|---|
| LifecycleState
A safe facade for lifecycle manager that objects can use to monitor its own state
|
| Class and Description |
|---|
FatalException
FatalException can be thrown during initialisation or during execution to indicate that something fatal has
occurred and the MuleManager must shutdown. |
Copyright © 2003–2017 MuleSoft, Inc.. All rights reserved.