Packages 
Package Description
org.agilewiki.jactor2
Why JActor2?
org.agilewiki.jactor2.core
The JActor2 is organized in 4 parts:
org.agilewiki.jactor2.core.blades
Blades hold state and a set of operations which are performed on that state.
org.agilewiki.jactor2.core.impl  
org.agilewiki.jactor2.core.impl.mtMessages  
org.agilewiki.jactor2.core.impl.mtPlant  
org.agilewiki.jactor2.core.impl.mtReactors  
org.agilewiki.jactor2.core.messages
Messages are passed to a blade's reactor where they are invoked on the appropriate thread to update the blade's state.
org.agilewiki.jactor2.core.messages.alt
Alternative message forms.
org.agilewiki.jactor2.core.messages.impl
These are the classes that are implemented in the mtMessages package.
org.agilewiki.jactor2.core.plant
The Plant class is in the jactor2-coreMT module, as it deals with implementation and configuration rather than API.
org.agilewiki.jactor2.core.plant.impl
The classes in this package are implemented in the mtPlant package.
org.agilewiki.jactor2.core.reactors
Reactors are light-weight threads, or fibers, which manage and process the messages for a set of blades.
org.agilewiki.jactor2.core.reactors.closeable
Supports objects with dependencies on 1 or more reactors (beta).
org.agilewiki.jactor2.core.reactors.closeable.impl
Implements Closeable.
org.agilewiki.jactor2.core.reactors.facilities
Facilities are IsolationReactors which support the registration of NamedBlades, with IsolationReactors themselves being NamedBlades.
org.agilewiki.jactor2.core.reactors.impl
These are the classes that are implemented in the mtReactor package.
org.agilewiki.jactor2.core.readme.blades  
org.agilewiki.jactor2.core.readme.plant  
org.agilewiki.jactor2.core.readme.reactors  
org.agilewiki.jactor2.core.readme.requests  
org.agilewiki.jactor2.core.revisited  
org.agilewiki.jactor2.metrics