Package bexee.core

Core classes and interfaces of the bexee engine.

See:
Description

Interface Summary

ProcessController

The ProcessController is the core of the engine and contains the execution logic for every BPEL activity.

Class Summary

BexeeMessage	This class is used for crossing the bridge between Axis and bexee in both ways.
Dispatcher	This class is used to lookup or create a ProcessInstance given an inbound BexeeMessage and dispatch the message to the ProcessControllereither synchronously or asynchronoulsy.
FlowThread	This class is used to implement "Flow" BPEL activities. i.e. parallel activity execution.
ProcessContext	The ProcessContext contains state information about a very specific process instance.
ProcessControllerFactory	Abstract factory class for creating ProcessControllerFactory implementations.
ProcessControllerImpl	The default imlementation of the ProcessController.
ProcessInstance	The ProcessInstance contains no logic at all but merely serves as a container for encapsulating a ProcessContext instance and its corresponding BPELProcess reference.

Exception Summary

AwaitMessageException	While the Process Controller is executing a process, it will necessarily arrive at a Receive activity without the message for the receive, there the process execution must stop and wait for a right message to resume execution.
DispatcherException	This class is used to indicate that something went wrong when trying to dispatch an inbound message to the ProcessController.
MessageNotFoundException	This Exception is used to signalize that a message has not been found where excepted.
MissingActivityException	This exception is used to signalize that a BPEL process has no root activity assigned.

Package bexee.core Description

Core classes and interfaces of the bexee engine.

Last modified: $Revision: 1.1 $, $Date: 2004/12/15 14:18:10 $