Mats3 API and
Mats3 Intercept API.See: Description
| Interface | Description |
|---|---|
| JmsMatsJmsSessionHandler |
Interface for implementing JMS Connection and JMS Session handling.
|
| JmsMatsJmsSessionHandler.JmsSessionHolder |
A "sidecar object" for the JMS Session, so that additional stuff can be bound to it.
|
| JmsMatsStartStoppable | |
| JmsMatsStatics |
Common "static" stash, hacked up as an interface to be implemented if you need it.
|
| JmsMatsTransactionManager |
Transactional aspects of the JMS Mats implementation.
|
| JmsMatsTransactionManager.JmsMatsTxContextKey |
Provided to
getTransactionContext(...) when a Mats-component
fetches the TransactionContext implementation. |
| JmsMatsTransactionManager.ProcessingLambda |
The lambda that is provided to the
JmsMatsTransactionManager for it to provide transactional demarcation
around. |
| JmsMatsTransactionManager.TransactionContext |
Implementors shall do the transactional processing and handle any Throwable that comes out of the
JmsMatsTransactionManager.ProcessingLambda by rolling back. |
| Class | Description |
|---|---|
| JmsMatsContextLocalCallback | |
| JmsMatsEndpoint<R,S,Z> |
The JMS implementation of
MatsEndpoint. |
| JmsMatsFactory<Z> | |
| JmsMatsInternalExecutionContext |
This is an internal context object, for execution of initiations and stage processing in JMS-Mats - one instance is
made per initiation and per message reception.
|
| JmsMatsJmsSessionHandler_Pooling |
Pooling implementation of
JmsMatsJmsSessionHandler - upon
creation, you decide how
Connections are shared for JmsMatsStageProcessors and MatsInitiators. |
| JmsMatsJmsSessionHandler_Pooling.JmsSessionHolderImpl | |
| JmsMatsJmsSessionHandler_Simple |
A dead simple implementation of
JmsMatsJmsSessionHandler which does nothing of pooling nor connection
sharing. |
| JmsMatsMessage<Z> |
Holds the entire contents of a "Mats Message" - so that it can be sent later.
|
| JmsMatsMessageBrokerSpecifics |
Some small specifics for the underlying JMS Implementation.
|
| JmsMatsProcessContext<R,S,Z> |
The JMS Mats implementation of
MatsEndpoint.ProcessContext. |
| JmsMatsStage<R,S,I,Z> |
The JMS implementation of
MatsStage. |
| JmsMatsTransactionManager_Jms |
Implementation of
JmsMatsTransactionManager handling only JMS (getting Connections, and creating Sessions),
doing all transactional handling "native", i.e. |
| JmsMatsTransactionManager_Jms.TransactionalContext_Jms |
The
JmsMatsTransactionManager.TransactionContext implementation for
JmsMatsTransactionManager_Jms. |
| JmsMatsTransactionManager_JmsAndJdbc |
Implementation of
JmsMatsTransactionManager that in addition to the JMS transaction also handles a JDBC SQL
Connection (using only pure java, i.e. |
| JmsMatsTransactionManager_JmsAndJdbc.TransactionalContext_JmsAndJdbc |
The
TransactionContext-implementation for JmsMatsTransactionManager_Jms. |
| Enum | Description |
|---|---|
| JmsMatsJmsSessionHandler_Pooling.PoolingKeyInitiator |
What kind of sharing of JMS Connections to employ for a
JmsMatsInitiator. |
| JmsMatsJmsSessionHandler_Pooling.PoolingKeyStageProcessor |
What kind of sharing of JMS Connections to employ for a
JmsMatsStageProcessor. |
| Exception | Description |
|---|---|
| JmsMatsException |
Base class for Exceptions thrown around in the JMS implementation of Mats.
|
| JmsMatsException.JmsMatsJmsException |
Thrown if anything goes haywire with the backend implementation, e.g.
|
| JmsMatsException.JmsMatsOverflowRuntimeException |
If we get "stack overflow" or "call overflow", then the sending method will throw this.
|
| JmsMatsException.JmsMatsUndeclaredCheckedExceptionRaisedRuntimeException |
Thrown if a undeclared checked exception propagates out of the user-supplied lambda.
|
| JmsMatsFactory.CannotInstantiateClassException | |
| JmsMatsTransactionManager_JmsAndJdbc.TransactionalContext_JmsAndJdbc.MatsSqlCommitOrRollbackFailedException |
Raised if commit or rollback of the SQL Connection failed.
|
Mats3 API and
Mats3 Intercept API.
The JMS v2.0 API is a superset of JMS v1.1. This implementation has run in production for a substantial financial
system since ~2018 on ActiveMQ (which implements JMS v1.1), but all tests are run for Artemis too (which implements
JMS v2.0).