Interface | Description |
---|---|
AbstractJmsFunctionalTestCase.Scenario | |
JmsVendorConfiguration |
Abstracts all the Jms Vendor specific configuration for the Jms integration test suite.
|
Class | Description |
---|---|
AbstractJmsFunctionalTestCase |
This is the base class for all integration tests that are part of the JMS integration test suite.
|
AbstractJmsSingleTransactionSingleServiceTestCase |
This tests single resource transactions through a single service definition (even
though the mule config file will have many service definitions).
|
JmsClientAcknowledgeTransactionTestCase |
Test jms using JmsClientAcknowledgeTransactionFactory
|
JmsConnectorJndiTestCase |
Requires the following connector config:
|
JmsCorrelationIdPropagationTestCase |
Tests the correct propagation of the correlation id property within the JMS transport.
|
JmsCustomCorrelationIdTestCase | |
JmsDeadLetterQueueTestCase |
Tests a transactional exception strategy.
|
JmsDurableTopicSingleTxTestCase |
Testing durable topic with external subscriber
|
JmsDurableTopicTestCase | |
JmsExceptionStrategyTestCase | |
JmsFunctionalTestSuite |
A test suite for JUnit 4 consisting of all JMS functional tests which have been
parameterized in order to support more than one JMS provider.
|
JmsMessageAwareTransformersMule2685TestCase |
JmsTransformersTestCase Tests the JMS transformer implementations. |
JmsMuleSideDurableTopicTestCase | |
JmsMuleSideDurableTopicXATxTestCase |
Testing durable topic with XA transactions
|
JmsObjectToMessageTransformerInResponseTestCase | |
JmsQueueMessageTypesTestCase |
Message is sent to and received from simple queue.
|
JmsQueueTestCase |
Message is sent to and received from simple queue.
|
JmsQueueWithCompressionTestCase |
Message is sent to and received from simple queue using compression in between
|
JmsQueueWithTransactionTestCase | |
JmsRemoteSyncMule2868TestCase | |
JmsReplyToPropertyTestCase | |
JmsResponseElementTestCase | |
JmsSingleTransactionAlwaysBeginConfigurationTestCase | |
JmsSingleTransactionBeginOrJoinAndAlwaysBeginTestCase | |
JmsSingleTransactionComponentTestCase |
There is a separate transaction for each service when single transaction(action:
BEGIN_OR_JOIN) and jms transport are used
|
JmsSingleTransactionNoneTestCase |
Send and recieve JmsMessage without any tx
|
JmsSingleTransactionRecieveAndSendTestCase | |
JmsSynchronousResponseTestCase |
see EE-1688/MULE-3059
|
JmsTemporaryReplyToTestCase |
TODO this test does not use the Test scenarios, I think it would need a new Method
sendAndReceive It might make sense to leave this test as is because it tests that
the client also works with ReplyTo correctly
|
JmsTopicTestCase |
Message is put to topic with two subscribers
|
JmsTransformersTestCase |
JmsTransformersTestCase Tests the JMS transformer implementations. |
JmsXAAlwaysBeginTestCase | |
JmsXAAlwaysBeginTestCase.TestResource | |
JmsXAAlwaysBeginTestCase.TestRollbackComponent | |
JmsXATransactionComponentTestCase | |
SessionEnabledObjectToJMSMessage |
This class overrides getSession() to return the specified test MuleSession;
otherwise we would need a full-fledged JMS connector with dispatchers etc.
|
Copyright © 2003–2016 MuleSoft, Inc.. All rights reserved.