Databases Reference
In-Depth Information
The next example shows how the requesting thread of a request/reply interaction
is also used to process the BPEL activities associated with the process. The next
example uses a SOAP binding but again it could be any client, including another
service engine or an adapter. The example assumes that there are no dehydration
points within the process and that it terminates after the
reply
activity.
Transactions
Transactions are tightly coupled to dehydration points within a process. Composite
interactions take place within a transaction context. That transaction context is
committed when a dehydration point is reached in a composite. Any updates to
the dehydration store are done in the context of the current transaction.
BPEL transactions
There are a number of ways to control the transaction within a BPEL process. Specific
activities affect the transaction management as well as properties on partner links
and composite components.
BPEL component properties
The transaction property of a BPEL component in
composite.xml
can be used to
control the participation of the BPEL process in the calling entities transaction. This
is similar to the way in which the author of an EJB can control the transactional
behavior of the EJB. This allows the creator of the composite to control the
transaction properties of their components.
