ConnectionFactory
in different scenarios (development, testing, staging, production) - best explained in the class doc of
ScenarioConnectionFactoryProducer - do
note that this should not be the first thing you delve into when trying out Mats!See: Description
| Interface | Description |
|---|---|
| ConfigurableScenarioDecider.SpecificScenarioDecider |
An implementation of this interface can decide whether a specific Mats Scenario is active.
|
| MatsProfiles |
Specifies Spring Profiles (and also which Spring Environment variables) that are relevant for Mats when used with
conjunction with
ScenarioConnectionFactoryProducer and the default configuration of
ConfigurableScenarioDecider. |
| ScenarioConnectionFactoryWrapper.ConnectionFactoryProvider |
A ConnectionFactory provider which can throw Exceptions - if it returns a
ConnectionFactoryWithStartStopWrapper, start() and stop() will be invoked on that, read more on its
JavaDoc. |
| ScenarioConnectionFactoryWrapper.ScenarioDecider |
We need a way to decide between the three different
MatsScenarios. |
| Class | Description |
|---|---|
| ConfigurableScenarioDecider |
Configurable
ScenarioConnectionFactoryWrapper.ScenarioDecider, whose defaults implements the logic described in
ScenarioConnectionFactoryProducer and handles all the Spring Profiles specified in MatsProfiles. |
| ConfigurableScenarioDecider.StandardSpecificScenarioDecider |
Standard implementation of
ConfigurableScenarioDecider.SpecificScenarioDecider used in the default configuration of
ConfigurableScenarioDecider, which takes a set of profile-or-properties names and checks whether they are
present as a Spring Profile, or (with the "-" replaced by ".") whether it exists as a property in the Spring
Environment. |
| ConnectionFactoryWithStartStopWrapper |
A abstract
ConnectionFactoryWrapper recognized by ScenarioConnectionFactoryProducer, which has a
start() and stop() method, which can be used if you need to fire up a local MQ Broker: This class is meant to be
extended to provide such functionality. |
| ScenarioConnectionFactoryProducer |
Provides a factory for a Spring-integrated Wrapper/Facade around a JMS ConnectionFactory, which in addition to
supporting the production setup, also facilitates the development situation where you often want to run against
either an in-vm MQ Broker or against a MQ Broker running on localhost, and also integrates with the
"mats-spring-test" integration test library where when run with the
MatsTestProfile you will most
probably want an in-vm setup (typically mocking up the project-external Mats endpoints that the tested endpoints
collaborate with). |
| ScenarioConnectionFactoryWrapper |
A
ConnectionFactoryWrapper which lazily decides which of the three MatsScenarios are active, and
produces the wrapper-target ConnectionFactory based on that - you most probably want to use
ScenarioConnectionFactoryProducer to make an instance of this class, but you can configure it directly too. |
| SpringJmsMatsFactoryProducer |
Provides an easy way to get hold of the most probable
JmsMatsFactory transaction manager configuration in the
Spring world (using JmsMatsTransactionManager_JmsAndSpringManagedSqlTx, or only the
JmsMatsTransactionManager_Jms if no DataSource is needed). |
| SpringJmsMatsFactoryWrapper |
Wrapper that should be used for a JmsMatsFactory in a Spring context.
|
| Enum | Description |
|---|---|
| MatsScenario |
The three different Mats Scenarios that the
ScenarioConnectionFactoryWrapper juggles between based on the
results of a set of three ScenarioConnectionFactoryWrapper.ScenarioDeciders, with an optional default choice. |
ConnectionFactory
in different scenarios (development, testing, staging, production) - best explained in the class doc of
ScenarioConnectionFactoryProducer - do
note that this should not be the first thing you delve into when trying out Mats!