JmsAttributes carries around the JMS settings.
JmsAttributes carries around the JMS settings.
As the JmsReqReplyBuilder is building a request from the DSL, it uses this object to represent the in progress request. Once the request is built it can then be used so that the JmsReqReplyAction knows exactly what message to send.
Type for jms checks
Provides the enumeration of JMSMessage types that the implementation supports
define trait for message matching logic with separate request/response to see how it can be used check JmsDefaultMessageMatcher
Wraps a JMS protocol configuration
Core JMS Action to handle Request-Reply semantics
Core JMS Action to handle Request-Reply semantics
This handles the core "send"ing of messages. Gatling calls the execute method to trigger a send. This implementation then forwards it on to a tracking actor.
Bookkeeping actor to correlate request and response JMS messages Once a message is correlated, it publishes to the Gatling core DataWriter
Advise actor a response message was received from JMS provider
Advise actor a message was sent to JMS provider
JmsProtocolBuilder allows building of the JMS protocol
JmsProtocolBuilder allows building of the JMS protocol
This allows multiple scenarios or jms methods to refer to a single protocol configuration.
See your JMS provider documentation for information on the values to set here.
Imports to be used to simplify the DSL
Imports to be used to simplify the DSL
Scenario scripts will import this and generally start interacting with the DSL from the functions exposed here