blob: e1b39d9e0720f02dd5a182fb509bbc524ad4f167 [file] [log] [blame]
<!--
~ Licensed to the Apache Software Foundation (ASF) under one
~ or more contributor license agreements. See the NOTICE file
~ distributed with this work for additional information
~ regarding copyright ownership. The ASF licenses this file
~ to you under the Apache License, Version 2.0 (the
~ "License"); you may not use this file except in compliance
~ with the License. You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
~ KIND, either express or implied. See the License for the
~ specific language governing permissions and limitations
~ under the License.
-->
<html>
<head><title>DAO Package</title></head>
<body>
<p>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 &quot;state snapshots&quot; 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 {@link com.fs.jlo.sfwk.bapi.dao}), the
BPEL DAO is a &quot;dumb&quot; object-relational model supporting
transactional access.</p>
</body>
</html>