com.jenkov.mrpersister.scope
Interface IScopeAction

All Known Implementing Classes:

ConnectionScope, TransactionScope

public interface IScopeAction

Represents the action(s) that is to be carried out inside the given scope. An IScopeAction can be used inside both a connection scope and a transaction scope.

Author:

Jakob Jenkov - Copyright 2005 Jenkov Development

Method Summary

java.lang.Object

inScope() This method is called by the scope boundary object when it is time to execute the actions inside the scope.

Method Detail

inScope

java.lang.Object inScope()
                         throws java.lang.Throwable

This method is called by the scope boundary object when it is time to execute the actions inside the scope.

As you may have noticed the connection that is scoped is not passed to the IScopeAction in this method. Your implementation of the IScopeAction interface must have a reference to the ScopingDataSource, from which it obtains it's connections. The ScopingDataSource can be obtained from the IScopeFactory you are using, or you can instantiate one yourself. Just remember that the ScopingDataSource referenced by your IScopeAction implementation has to be the same instance as referenced by the IScopeBoundary instance, calling the inScope() method of your IScopeAction implementation.

Returns:

An object if your IScopeAction chooses to.

Throws:

java.lang.Throwable - If something goes wrong inside the IScopeAction. The surrounding IScopeBoundary object will take the correct measures to close the connection and rollback any ongoing transaction.