AbstractBrokerFunctionalTestCase |
Base test class for tests that require an Active MQ broker that is not embedded in the Mule application.
|
AbstractJmsRedeliveryTestCase |
|
CustomCachingConnectionFactoryTestCase |
|
DefaultJmsTopicResolverTestCase |
|
DynamicEndpointWithConnectorTestCase |
|
Jms11SupportTestCase |
|
JmsCachingDisposeTestCase |
|
JmsCachingTestCase |
Tests that JMS message are correctly sent when caching elements
|
JmsConnectionFactoryTestCase |
|
JmsConnectorTestCase |
|
JmsEndpointTestCase |
|
JmsExceptionReaderTestCase |
|
JmsInfiniteRedeliveryTestCase |
|
JmsJndiReconnectionTestCase |
|
JmsMessageUtilsTestCase |
|
JmsMuleMessageFactoryTestCase |
|
JmsNoRedeliveryTestCase |
|
JmsReconnectForeverTestCase |
|
JmsReconnectionActiveMQTestCase |
MULE-7534: JMS connector doesn't reconnect to ActiveMQ broker 5.6 when using blocking=true
When using ActiveMQ 5.6, the createConnection() method of the connection factory returns an invalid connection
object instead of failing when the broker is down, in newer versions the createConnection() method throws an
exception.
|
JmsReconnectionTestCase |
|
JmsRedeliveryTestCase |
|
JmsSelectorDetectionTestCase |
|
JmsSessionVariablesPropagationTestCase |
|
JmsTransactionalCachingTestCase |
Tests that JMS message are correctly sent when caching elements and use transactions
|
JmsTransactionalCachingTestCase.AbortMessageOnEventCount |
|
JmsTransformerTestCase |
|
MultiConsumerJmsMessageReceiverTest |
|
OutboundSessionAndProducerReuseTestCase |
Tests that JMS message are correctly sent when caching elements
|
XaPollingTimeoutTestCase |
|
XaPollingTimeoutTestCase.TestXaTransactedJmsMessageReceiver |
|
XaTransactedJmsMessageReceiverTest |
|