|Modifier and Type||Method and Description|
This method is most probably not for you!.
Waits a couple of seconds for a message to appear on the Dead Letter Queue for the provided endpoint- or stageId (Queue name "DLQ."+matsendpointPrefix+endpointOrStageId) - and also checks the standard common ActiveMQ DLQ (Queue name "ActiveMQ.DLQ") in case the broker is not configured with specific DLQs per Queue, which is relevant if you fire up an unmodified ActiveMQ distribution on the command line, check the
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
public MatsTestBrokerInterface.MatsTestBrokerInterface_JmsMatsFactory _latePopulate(javax.jms.ConnectionFactory connectionFactory, MatsFactory matsFactory)
SpringJmsMatsFactoryWrapper, by reflection invocation when it is both on classpath and as an instance in the Spring context, to perform "late setting" of the properties which the tool needs to perform its job. (Reason for reflection: This class resides in the 'mats-test' project - which is for testing, while the
SpringJmsMatsFactoryWrapperis in the 'mats-spring-jms' project - which is for "production"). The matsFactory parameter currently needs to be a JmsMatsFactory. We need all of the following from it
MatsInterceptable, which JmsMatsFactory is)
MatsSerializerto provide access to contents from messages (from JmsMatsFactory)
MatsFactory.MatsFactoryWrapper, but it must resolve to a
MatsFactory.unwrapFully()! Otherwise, it'll throw an
protected void checkCorrectSetup()
public MatsTestBrokerInterface.MatsMessageRepresentation getDlqMessage(java.lang.String endpointOrStageId)
MatsTestBrokerclass JavaDoc for how to use an external MQ instead of the in-VM which otherwise is fired up. (NOTE: It is HIGHLY suggested to use the "specific DLQ" pattern in any production setting, as this is much easier to reason about when ugly things starts hitting fans).