| org.apache.ojb.odmg.ImplementationExt
All known Subclasses: org.apache.ojb.odmg.ImplementationImpl,
| ImplementationExt | | public interface ImplementationExt extends Implementation(Code) | | Offers useful none odmg-standard methods of the odmg
org.odmg.Implementation interface.
Note: All listed methods are not part of the standard ODMG-api -
they are special (proprietary) OJB extensions.
version:
$Id: ImplementationExt.java,v 1.1.2.6 2005/12/21 22:29:21 tomdz Exp $ |
| setImplicitLocking | | public void setImplicitLocking(boolean impliciteLocking)(Code) | | Set the global property implicit locking. This method can be used
to activate or deactivate the global implicit
locking mechanism.
If set true OJB implicitly locks objects to ODMG transactions
after performing OQL queries. Also if implicit locking is used
locking objects is recursive, that is associated objects are also
locked. If ImplicitLocking is set to 'false', no locks are obtained
in OQL queries, lookup objects and there is also no recursive locking.
However it's possible to set this value only for the current used
org.odmg.Transaction using
TransactionExt.setImplicitLocking(boolean) and to detect the implicit locking
state of the used transaction instance call
TransactionExt.isImplicitLocking .
Turning off implicit locking may improve performance but requires
additional care to make sure that all changed objects are properly
registered to the transaction.
Parameters:
impliciteLocking - If set true implicit locking is enabled,if false, implicit locking is disabled. |
| setImpliciteWriteLocks | | public void setImpliciteWriteLocks(boolean impliciteWriteLocks)(Code) | | If the OJB implicit locking feature (see
TransactionExt.setImplicitLocking(boolean) ) is
enabled, this define the lock type of all implicit locked objects.
If set to true, acquiring a write-lock on a given object x implies write locks on all
implicit locked objects.
If set to false, in any case implicit read-locks are acquired.
Acquiring a read- or write lock on x thus allways results in implicit read-locks
on all associated objects.
Parameters:
impliciteWriteLocks - If true implicit write locks will enabled. |
| setOqlCollectionClass | | public void setOqlCollectionClass(Class oqlCollectionClass)(Code) | | Set the used collection type class returned by OQL queries.
NOTE: Each specified class must implement interface
org.apache.ojb.broker.ManageableCollection to work proper with OJB.
Parameters:
oqlCollectionClass - The collection class used in OQL queries. |
| setOrdering | | public void setOrdering(boolean ordering)(Code) | | Disable/enable OJB's ordering algorithm when insert, update, delete a
bunch of objects within a transaction. The ordering algorithm try to
calculate the correct order of the modified/new persistent objects to
prevent problems on commit of the transaction.
If the used databases support 'deferred checks' it's recommended to
use this feature and to disable OJB's object ordering.
However it's possible to set this value only for the current
used
org.odmg.Transaction using
TransactionExt.setOrdering(boolean)
Parameters:
ordering - If true OJB's ordering algorithm is used. |
|
|