Examples of UnitOfWorkImpl

oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl
Implementation of oracle.toplink.essentials.sessions.UnitOfWork The public interface should be used by public API and testing, the implementation should be used internally. @see oracle.toplink.essentials.sessions.UnitOfWork Purpose: To allow object level transactions.
Description: The unit of work is a session that implements all of the normal protocol of a TopLink session. It can be spawned from any other session including another unit of work. Objects can be brought into the unit of work through reading them or through registering them. The unit of work will opperate on its own object space, that is the objects within the unit of work will be clones of the orignial objects. When the unit of work is commited, all changes to any objects registered within the unit of work will be commited to the database. A minimal commit/update will be performed and any foreign keys/circular reference/referencial integrity will be resolved. If the commit to the database is successful the changed objects will be merged back into the unit of work parent session.
Responsibilities:
- Allow parallel transactions against a session's objects.
- Allow nested transactions.
- Not require the application to write objects that is changes, automatically determine what has changed.
- Perform a minimal commit/update of all changes that occured.
- Resolve foreign keys for newly created objects and maintain referencial integrity.
- Allow for the object transaction to use its own object space.
org.apache.lenya.transaction.UnitOfWorkImpl
Default implementation of a unit of work. @version $Id: UnitOfWorkImpl.java 574827 2007-09-12 08:00:57Z andreas $
org.eclipse.persistence.internal.sessions.UnitOfWorkImpl
Implementation of org.eclipse.persistence.sessions.UnitOfWork The public interface should be used. @see org.eclipse.persistence.sessions.UnitOfWork
Purpose: To allow object level transactions.
Description: The unit of work is a session that implements all of the normal protocol of an EclipseLink session. It can be spawned from any other session including another unit of work. Objects can be brought into the unit of work through reading them or through registering them. The unit of work will operate on its own object space, that is the objects within the unit of work will be clones of the original objects. When the unit of work is committed, all changes to any objects registered within the unit of work will be committed to the database. A minimal commit/update will be performed and any foreign keys/circular reference/referential integrity will be resolved. If the commit to the database is successful the changed objects will be merged back into the unit of work parent session.
Responsibilities:
- Allow parallel transactions against a session's objects.
- Allow nested transactions.
- Not require the application to write objects that is changes, automatically determine what has changed.
- Perform a minimal commit/update of all changes that occurred.
- Resolve foreign keys for newly created objects and maintain referential integrity.
- Allow for the object transaction to use its own object space.

Examples of org.eclipse.persistence.internal.sessions.UnitOfWorkImpl

    /**
     * Get the value from the wrapped value holder, instantiating it
     * if necessary, and clone it.
     */
    protected Object instantiate() {
        UnitOfWorkImpl unitOfWork;
        if (isSerializedRemoteUnitOfWorkValueHolder()) {
            unitOfWork = getRemoteUnitOfWork();
        } else {
            unitOfWork = getUnitOfWork();
        }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.