Uses of Interface
org.refcodes.component.ConnectionComponent

Uses of ConnectionComponent in org.refcodes.component

Subinterfaces of ConnectionComponent in org.refcodes.component

Modifier and Type	Interface	Description
static interface	ComponentComposite.ExtendedComponentComposite<CTX,CON>	The ComponentComposite.ExtendedComponentComposite provides extended functionality to the ComponentComposite'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	AbstractComponentComposite.ExtendedCompositeComponentImpl<C extends Component,CTX,CON>	The AbstractComponentComposite.ExtendedCompositeComponentImpl is an implementation of the ComponentComposite.ExtendedComponentComposite.
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

Modifier	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.