Package org.apache.ode.bpel.dao

Data-Access Object (DAO) interfaces used by the BPEL Service Provider to communicate with the data store; can be used to customize the BPEL persistence layer.

See:
          Description

Interface Summary
ActivityRecoveryDAO Activity recovery object.
BpelDAOConnection Represents the physical resource for connecting to the bpel state store.
BpelDAOConnectionFactory  
BpelDAOConnectionFactoryJDBC Extension of the BpelDAOConnectionFactory interface for DAOs that are based on J2EE/JDBC data sources.
CorrelationSetDAO Data access object representing a BPEL correlation set.
CorrelatorDAO Data access object representing a correlator.
FaultDAO Fault data access object.
MessageDAO Representation of a message (i.e.
MessageExchangeDAO Data access object for a message exchange.
MessageRouteDAO Data access object representing a message consumer.
PartnerLinkDAO Data access object representing the endpoint reference of a specific partner link role (typically the partnerRole).
ProcessDAO BPEL process data access objects.
ProcessInstanceDAO BPEL process instance data access object.
ProcessManagementDAO This DAO handles any process and instance management related database operations.
ScopeDAO Data access objec representing a BPEL scope instance.
XmlDataDAO Data access object representing a piece of XML data.
 

Class Summary
ProcessInstanceDAO.EventsFirstLastCountTuple Transport object holding the date of the first and last instance event along with the number events.
RoleEnum Partner-link role enumeration; one of RoleEnum.MY_ROLE or RoleEnum.PARTNER_ROLE.
ScopeStateEnum  
 

Exception Summary
NoRootContextException Exception thrown when no root context.
QueryReturnedEmptyResultException Thrown when a query returns empty results.
QueryReturnedMultipleResultsException Thrown when a query returns multiple results.
 

Package org.apache.ode.bpel.dao Description

Data-Access Object (DAO) interfaces used by the BPEL Service Provider to communicate with the data store; can be used to customize the BPEL persistence layer. The BPEL DAO layer is used to maintain persistent state of each active BPEL process instance. This includes the values of scope variables, as well as instance "state snapshots" that may need to be persisted due to the activation of receive, pick, or invoke activity that cannot be immediately satisfied. Like the DAO of the framework (see com.fs.jlo.sfwk.bapi.dao), the BPEL DAO is a "dumb" object-relational model supporting transactional access.