META-INF.xsd.smooks.jms-routing-2.0.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of smooks-routing-cartridge Show documentation
Show all versions of smooks-routing-cartridge Show documentation
The Smooks Routing cartridge provides support for routing and splitting fragments
The newest version!
Smooks JMS Routing Configuration
JMS router configuration
The JMS router routes messages to a JMS destination (Queue or Topic).
The message payload is created from a bean out of the bean context. It is possible
to send Text or Object messages. The correlation id can be generated out of a FreeMarker
template.
JMS Router
The message configuration.
The JMS connection configuration.
The JMS session configuration.
The JNDI configuration.
The configuration for the max number of messages that can be sitting in the
JMS Destination at any any time.
The element to route on.
The beanId of the bean from the bean context to be used as message payload.
The JMS destination string
If the routing is done before or after the selected element. Default is 'false'.
The message configuration.
JMS Correlation pattern that will be used for the outgoing message.
Templating support is available via the FreeMarker template engine.
The type of JMS Message that should be sent. 'TextMessage'(default) or 'ObjectMessage'.
The JMS DeliveryMode. 'persistent'(default) or 'non-persistent'.
The JMS Priority to be used
The JMS Time-To-Live to be used.
The JMS connection configuration.
The ConnectionFactory to look up
The security principal use when creating the JMS connection.
The security credentials to use when creating the JMS connection.
The JMS session configuration.
Determines if the session should be transacted. Defaults to 'false'.
The acknowledge mode to use. One of 'AUTO_ACKNOWLEDGE'(default), 'CLIENT_ACKNOWLEDGE', 'DUPS_OK_ACKNOWLEDGE'.
The JNDI configuration.
A .properties file containing the JNDI properties to be used for JMS resource
lookups.
The JNDI ContextFactory to use
The JNDI Provider URL to use.
The JNDI NamingFactory to use
The configuration for the max number of messages that can be sitting in the
JMS Destination at any any time.
The max number of messages that can be sitting in the JMS Destination at any any time. Default is 200.
The number of milliseconds to wait for the system to process JMS Messages from the JMS destination so that the
number of JMS Messages drops below the highWaterMark. Default is 60000 ms.
The number of milliseconds to wait between checks on the High Water Mark, while waiting for it to drop.
Default is 1000 ms.
The possible JMS acknowledge modes
With this acknowledgement mode, the session automatically acknowledges a client's receipt of a
message when it has either successfully returned from a call to receive or the message listener
it has called to process the message successfully returns.
With this acknowledgement mode, the client acknowledges a message by calling a message's acknowledge method.
This acknowledgement mode instructs the session to lazily acknowledge the delivery of messages.
The possible JMS message types.
A TextMessage is used to send a message containing a java.lang.String.
To retrieve the string the cartridge calls the 'toString()' method of the target bean.
An ObjectMessage is used to send a message that contains a serializable Java object.
Only Serializable Java objects can be used.
A MapMessage is used to send a set of name-value pairs where names are Strings and values are Java primitive types or Strings.
Only Map Java objects can be used.
For the keys of the map the 'toString()' method is called to retrieve the String representation.
Objects that aren't primitive types or Strings get the toString() method called to return the String representation.
The possible JMS delivery modes.
This mode instructs the JMS provider to log the message to stable storage as part of the client's send operation.
This is the lowest overhead delivery mode because it does not require that the message be logged to stable storage.