Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. It is no longer a mandatory to provide a JMS ConnectionFactory. For a single JVM simple usage, you may use the default in-memory, non-persistent ActiveMQ connection factory, or you could configure your JMSProvider in several ways.
  2. The library is no longer used as a Groovy Category. The Groovy Category are hidden. There are a few different ways to use:
    Code Block
    // 1
    jms{ //require static import of groovy.jms.JMS.jms
     // your jms code
    }
    
    // 2
    def jms = new JMS(){
     // your jms code
    }
    
    // and for further execution
    jms.run{
     // more jms code
    }
    
    
    // 3
    def jms = new JMS()
     jms.xxx ; // this is for using the Groovy Messaging Service API
     jms.close() //must be closed manually if JMS code are not executed in the JMS Contextâ™ 
    
  3. The base Category API are slightly modified and are refactored to the JMSCoreCategory. Two sets of new APIs: GroovyJMS API and Groovy Messaging Service API are provided. The latter are designed base on the Groovy Sql.

...