Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Fire and forget

Pub sub messages

...

XML/Text based messages

Service has JAXB interface

Java serialized objects

Service has POJO interface

SOAP over JMS

Is this binding.jms, binding.ws or both

Message transformation

Multiple Message Types

Callbacks and conversations

...

Alternative JMS providers?

...

Policy

Binding Type

The JMS binding has native support for some intents.

Code Block

<bindingType type="binding.jms"
             alwaysProvides="jms"
              mayProvide="atLeastOnce atMostOnce ordered conversation"/>

atLeastOnce

atMostOnce

ordered

conversation

priority

Following example given in spec

Code Block

  <policySet name="JMSPolicy"
              provides="priority"
              appliesTo="binding.jms">

 <intentMap provides="priority" default="medium">
   <qualifier name="high">
     <headers JMSPriority="9"/>
    </qualifier>
    <qualifier name="medium">
      <headers JMSPriority="4"/>
    </qualifier>
    <qualifier name="low">
      <headers JMSPriority="0"/>
    </qualifier>
 </intentMap>

 </policySet>
Code Block

 <reference name="StockQuoteService" requires="priority.high log">
   <interface.java interface="services.stockquote.StockQuoteService"/>
   <binding.jms>
      <destination name="StockQuoteServiceQueue"/>
      <connectionFactory name="StockQuoteServiceQCF"/>
   </binding.jms>

Policy setting of user properties