org.mule.tests.internal

Class TransactionProfilingConsumptionOperations

java.lang.Object

org.mule.tests.internal.TransactionProfilingConsumptionOperations

public class TransactionProfilingConsumptionOperations
extends Object

This class is a container for operations, every public method in this class will be taken as an extension operation.

Constructor Summary

Constructors

Constructor and Description
TransactionProfilingConsumptionOperations()

Method Summary

Modifier and Type	Method and Description
void	addTransactionExpectation(boolean active, String state) Adds an expectation for the transaction events to come
void	assertTransactions() Performs assertions between the expected states of transactions, and the actual received ones.
void	startConsumingTransactions() Clears the consumed ProfilingEventType for transactions, and registers the ProfilingDataConsumer to get Transaction Profiling Events.

Methods inherited from class java.lang.Object

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

Constructor Detail

TransactionProfilingConsumptionOperations

public TransactionProfilingConsumptionOperations()

Method Detail

startConsumingTransactions

@MediaType(value="*/*",
           strict=false)
public void startConsumingTransactions()

Clears the consumed ProfilingEventType for transactions, and registers the ProfilingDataConsumer to get Transaction Profiling Events.

addTransactionExpectation

@MediaType(value="*/*",
           strict=false)
public void addTransactionExpectation(boolean active,
                                                                                       String state)

Adds an expectation for the transaction events to come

Parameters:

active - The current transaction state (at the moment of the execution of this operation)

state - The state of the last received event (commit, continue, rollback, start)

assertTransactions

@MediaType(value="*/*",
           strict=false)
public void assertTransactions()

Performs assertions between the expected states of transactions, and the actual received ones. The expected and obtained states must be the same amount, and they should be coincide in "active" and "status" in the order it was defined. To avoid problems with parallel executions (e.g. Try within ParallelForeach), we check this order by incoming Thread.