JMS provider endpoints have a number of behaviors that are configurable. These include:
how messages are correlated
the use of durable subscriptions
if the service uses local JMS transactions
the message selectors used by the endpoint
Service endpoints can be configure in one of two ways:
Tip | |
---|---|
The recommended method is to place the provider endpoint specific information into the Celtix Enterprise configuration file for the endpoint. |
Provider endpoint configuration is specified using the jms:destination
configuration element. Using this configuration element, you can specify the provider endpoint's behaviors using the jms:runtimePolicy
element. When configuring a provider endpoint you can use the following jms:runtimePolicy
attributes:
Table 2.4. Provider Endpoint Configuration
Example 2.4, “Configuration for a Provider Endpoint” shows a Celtix Enterprise configuration entry for configuring a provider endpoint.
Example 2.4. Configuration for a Provider Endpoint
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ct="http://cxf.apache.org/configuration/types" xmlns:jms="http://cxf.apache.org/transports/jms" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> ... <jms:destination id="{http://cxf.apache.org/jms_endpt}HelloWorldJMSPort.jms-destination"> ... <jms:runtimePolicy messageSelector="cxf_message_selector" useMessageIDAsCorrelationID="true" transactional="true" durableSubscriberName="cxf_subscriber" /> ... </jms:destination> ... </beans>
Provider endpoint behaviors are configured using the optional jms:server
element. The jms:server
element is a child of the WSDL wsdl:port
element and has the following attributes:
Table 2.5. JMS Provider Endpoint WSDL Extensions