Abstract: A method and computer program product are provided for implementing pushdown queries in a distributed object management system. A pushdown query to a system datastore is performed for a query type returning a single object. Responsive to the system datastore finding the match, checking whether the match refers to an object changed in the current transaction is performed. Responsive to the match not referring to a changed object, the object is returned. Responsive to the match referring to the changed object and the changed object matching the pushdown query, the changed object is returned. Responsive to the system datastore not finding the match, a list of changed objects in a current transaction is obtained. Each of the changed objects are in a current transactional state. An object query is performed on the changed objects in the list of changed objects. A multiple object pushdown query to the system datastore is performed for a query type returning multiple objects.

Abstract: A system, method, and apparatus for ensuring data integrity in a distributed object-oriented transaction processing environment, including support of single- and two-phased commit protocol transactions with a new protocol defined as a mixed-phase commit protocol. A root transaction manager on a server registers distributed object resources requested by a client application for a global transaction as being committable by either the single-phase, two-phase, or mixed-phase protocol. The root transaction manager commits the registered resources in accordance with the results of the registration step.

Abstract: A system, method, and apparatus for enabling a thin client to participate in a global transaction in a distributed object-oriented transaction processing environment that commits resources according to a two-phased commit protocol. The thin client is configured with a pseudo-transaction manager (PTM), and a remote server managing the commit procedure is configured with an object transaction manager having an interface to the (PTM). When an application on the thin client sends a request to begin a transaction, the PTM creates a temporary propagation context including a Global ID identifying the transaction and sets a flag in the context to indicate that this is a new transaction. The context is sent to a remote server for execution of a remote method.