...
Configuration parameters for JMS receiver and the sender are XML fragments that represent JMS connection factories. A typical JMS parameter configuration would look like this:
| Code Block |
|---|
<parameter name="myTopicConnectionFactory">
<parameter name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
<parameter name="java.naming.provider.url">tcp://localhost:61616</parameter>
<parameter name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</parameter>
<parameter name="transport.jms.ConnectionFactoryType">topic</parameter>
</parameter>
|
...
Parameter Name | Description | Requried | Possible Values | Default Value |
|---|---|---|---|---|
transport.jms.ConnectionFactory | Name of the JMS connection factory the service should use. | No | A name of an already defined connection factory | default |
transport.jms.PublishEPR | JMS EPR to be published in the WSDL. | No | A JMS EPR |
|
Please, refer Introduction to Switching TransportsTransports, Switching from HTTP/S to JMS, Pure Text/Binary and POX Message Support with JMS, Bridging from JMS to HTTP and Replying with a 202 Accepted Response that illustrate the usage of the JMS transport in a number of useful scenarios.
| Excerpt | ||
|---|---|---|
| ||
Description of JMS transport. |