Uses of Interface org.refcodes.component.ConnectionComponent (org.refcodes:refcodes-component 1.10.1 API)

Uses of ConnectionComponent in org.refcodes.component

Subinterfaces of ConnectionComponent in org.refcodes.component
Modifier and Type	Interface	Description
`static interface`	`CompositeComponent.ExtendedCompositeComponent<CTX,CON>`	The `CompositeComponent.ExtendedCompositeComponent` provides extended functionality to the `CompositeComponent`'s functionality by including extended `Openable` functionality (`ConnectionOpenable`) and extends `Initializable` functionality (`Configurable`).
`static interface`	`ConnectionComponent.ConnectionAutomaton<CON>`	A system implementing the `ConnectionComponent.ConnectionAutomaton` interface supports managing `ConnectionComponent` instances and takes care that the open/close statuses are invoked in the correct order by throwing according exceptions in case the open/close-cycle is invoked in the wrong order.
`static interface`	`ConnectionComponent.ConnectionComponentBuilder<CON,B extends ConnectionComponent.ConnectionComponentBuilder<CON,B>>`	Similar to the `ConnectionComponent` with additional according builder methods.

Classes in org.refcodes.component that implement ConnectionComponent
Modifier and Type	Class	Description
`static class`	`CompositeComponentImpl.ExtendedCompositeComponentImpl<C extends Component,CTX,CON>`	The `CompositeComponentImpl.ExtendedCompositeComponentImpl` is an implementation of the `CompositeComponent.ExtendedCompositeComponent`.
`class`	`ConnectionAutomatonImpl<CON>`	This class implements a `ConnectionComponent.ConnectionAutomaton`.

Fields in org.refcodes.component declared as ConnectionComponent
Modifier and Type	Field	Description
`protected ConnectionComponent<CON>`	ConnectionAutomatonImpl.`_connectionComponent`

Constructors in org.refcodes.component with parameters of type ConnectionComponent
Constructor	Description
`ConnectionAutomatonImpl(ConnectionComponent<CON> aConnectionComponent)`	This constructor uses a `LifeCycleStatus` for wrapping it inside the `ConnectionAutomatonImpl`, making sure of obeying and guarding the correct `LifeCycleStatus`'s order of `LifeCycleStatus` states for you.