You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Unable to render {include} The included page could not be found.
Unable to render {include} The included page could not be found.

<binding.jms>

The Tuscany Java SCA runtime supports the Java Messaging Service using the <binding.jms> SCDL extension. New JMS based service endpoints can be provided using a <binding.jms> element within a SCA <service>, existing JMS queues can be accessed using a <binding.ws> element within a SCA <reference>.

The JMS binding is one of the SCA extensions which is being formalized in the OASIS Open Composite Services Architecture with a published specifications document.

The JMS binding SCDL has the following format:

SCDL Content                                        Default  Value                    Feature Implemented
============                                        ==============                    ===================
<binding.jms correlationScheme="string"?            requestmsgidtocorrelid            No
             initialContextFactory="xs:anyURI"?     
             jndiURL="xs:anyURI"?
             requestConnection="QName"?
             responseConnection="QName"?
             operationProperties="QName"?
             ... >
  <destination name="xs:anyURI" 
               type="string"? 
               create="string"?>
    <property name="NMTOKEN" type="NMTOKEN">*
  </destination>?
  <connectionFactory name="xs:anyURI" 
                     create="string"?>
    <property name="NMTOKEN" type="NMTOKEN">*
  </connectionFactory>?
  <activationSpec name="xs:anyURI" 
                  create="string"?>
    <property name="NMTOKEN" type="NMTOKEN">*
  </activationSpec>?

  <response>
    <destination name="xs:anyURI" 
                 type="string"? 
                 create="string"?>
      <property name="NMTOKEN" type="NMTOKEN">*
    </destination>?
    <connectionFactory name="xs:anyURI" 
                      create="string"?>
      <property name="NMTOKEN" type="NMTOKEN">*
    </connectionFactory>?
    <activationSpec name="xs:anyURI" 
                    create="string"?>
      <property name="NMTOKEN" type="NMTOKEN">*
    </activationSpec>?
  </response>?

  <resourceAdapter name="NMTOKEN">?
    <property name="NMTOKEN" 
              type="NMTOKEN">*
  </resourceAdapter>?

  <headers JMSType="string"?
           JMSCorrelationId="string"?
           JMSDeliveryMode="string"?
           JMSTimeToLive="int"?
           JMSPriority="string"?>
    <property name="NMTOKEN" type="NMTOKEN">*
  </headers>?

  <operationProperties name="string" 
                       nativeOperation="string"?>
    <property name="NMTOKEN" type="NMTOKEN">*
    <headers JMSType="string"?
             JMSCorrelationId="string"?
             JMSDeliveryMode="string"?
             JMSTimeToLive="int"?
             JMSPriority="string"?>
      <property name="NMTOKEN" type="NMTOKEN">*
    </headers>?
  </operationProperties>*
</binding.jms>

(question) see JMS Binding S Vpecification 1.0 for deatils of each of these configuration options.

Binding Operation

<binding.jms>

Some examples:

From the binding.jms module tests.
  • No labels