dependency between two nodes
dependency event
error handling
send the next message later
base class for engine internal message
a message - reply to decompose, basically asynchronous completion of a message
a message - reply to decompose, basically asynchronous completion of a message
The engine will stich the AST together and continue
send this from async executors
a message - request to decompose
a message - request to decompose
The engine will decompose the given node a and send to self a DERep
DDD - base trait for events
DDD - node expanded
DDD - node status
a diesel application context - setup actor infrastructure etc
a diesel application context - setup actor infrastructure etc
todo properly injecting these todo eventually supporting more contexts per JVM
wrapper for JS scripts - this is the object diesel
a trace.
a trace. traces can be communicated between engines. Also, this is what you get when setting the response type to trace
a tree node
a tree node
kind is spec/sampled/generated/test etc
todo optimize tree structure, tree binding
todo need ID conventions to suit distributed services
mix this in if you want to control display/traversal
specific root context for an engine instance
specific root context for an engine instance
it can keep unique IDs and such, to help with tests ran continuously
the engine: one flow = one engine = one actor
exec context for engine - each engine has its own.
exec context for engine - each engine has its own.
it will serialize status udpates and execution
engine router - routes updates to proper engine actor
engine router - routes updates to proper engine actor
todo can i drop refMap and address actors directly?
various settings for each wf engine, see http://specs.dieselapps.com/Topic/Flags_and_modes
a REST request or response: content and type and processing thereof
accumulate results and infos and errors
the kinds of nodes we understand
initialize and stop the engine
suspend the engine for async messages - to continue you have to fire off a DERep yourself, later
an application static - engine factory, manager and cache
a tree node
a tree node
kind is spec/sampled/generated/test etc
todo optimize tree structure, tree binding
todo need ID conventions to suit distributed services
the states of a node
content processing utils
RDOM extensions
error handling
todo should not be part of normal processing DEMsg