Ask Questions and Find Answers

Sure.

You just create an orchestrating method in the SB tier.

Say, for example, that you are saving 3 different entities, you could create a method saveAll() that invokes the individual saves.  As long as the method follows the standard naming conventions, the transaction will be bound to, as in this example, saveAll().  On exit of saveAll(), it will either commit or roll back depending upon the outcome.

Matthew K.:

Hello!

I know that Liferay supports transactions (and a proper rollback mechanism) when using the service builder. But using the service builder everytime I make multiple Liferay api calls in a row feels kind of overkill to me. So I want to ask you if there is another, maybe more compact way to put several api calls in one transaction.

You can create a transaction using TransactionInvokerUtil

That util is internally used by Staging process in order to create a transaction during all import operation.

Groovy script example:

import com.liferay.portal.kernel.transaction.*;
import com.liferay.portal.kernel.service.*;

import java.util.concurrent.*;

private _invokeTransactionally(Callable callable)
    throws Throwable {

    Class<?>[] rollbackForClasses = new Class<?>[1];

    rollbackForClasses[0]=Exception.class;

    TransactionInvokerUtil.invoke(
        TransactionConfig.Factory.create(
            Propagation.REQUIRED, rollbackForClasses), callable);
}

Callable yourLogic = new Callable<Void>() {
    Void call() throws Exception {
        ....your code....
    }
}

_invokeTransactionally(yourLogic);

The callable that is passed to TransactionInvokerUtil.invoke is executed in a isolated transaction that will be rolledback in case a Exception specified in rollbackForClasses variable is thrown.

Regards,

Jorge Díaz