Class TransactionSystemCouchbaseException

java.lang.Object

java.lang.Throwable

java.lang.Exception

java.lang.RuntimeException

org.springframework.core.NestedRuntimeException

org.springframework.transaction.TransactionException

org.springframework.transaction.TransactionSystemException

org.springframework.data.couchbase.transaction.error.TransactionSystemCouchbaseException

All Implemented Interfaces:

Serializable

Direct Known Subclasses:

TransactionSystemAmbiguousException, TransactionSystemUnambiguousException

public abstract class TransactionSystemCouchbaseException
extends TransactionSystemException

A base class of transaction-level exceptions raised by Couchbase, allowing them to be handled in one place.

Author:

Graham Pople

See Also:

• Serialized Form

Constructor Summary

Constructors

Constructor	Description
TransactionSystemCouchbaseException(com.couchbase.client.java.transactions.error.TransactionFailedException ex)

Method Summary

Modifier and Type	Method	Description
List<com.couchbase.client.core.cnc.events.transaction.TransactionLogEvent>	logs()	An in-memory log is built up during each transaction.

Methods inherited from class TransactionSystemException

contains, getApplicationException, getOriginalException, initApplicationException

Methods inherited from class NestedRuntimeException

getMostSpecificCause, getRootCause

Methods inherited from class Throwable

addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString

Methods inherited from class Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Constructor Details

TransactionSystemCouchbaseException

public TransactionSystemCouchbaseException(com.couchbase.client.java.transactions.error.TransactionFailedException ex)

Method Details

logs

public List<com.couchbase.client.core.cnc.events.transaction.TransactionLogEvent> logs()

An in-memory log is built up during each transaction. The application may want to write this to their own logs, for example upon transaction failure.