GroovyJMS

Added by Mingfai Ma, last edited by Mingfai Ma on Feb 13, 2009  (view change)

Introduction

GroovyJMS provides set of Groovy-style APIs, enhanced JMS API with Groovy Categories, and a powerful JMSPool bean, that make it very easy to use JMS in Groovy application. It transparently handle connection and session lifecycle, and adds some thread-safe convenient methods to the JMS APIs.

Take a simple example:

jms{
 "loginService".send [user:'groovy', password:'jms']
 // or [user:'groovy', password:'jms'].sendTo "loginService"
}

And a complex one:

// create a JMS Thread Pool with 10 threads at max
def pool = new JMSPool(maximumPoolSize:10)
// subscribe to three destinations, each with 2 threads
pool.onMessage([fromQueue:['queue0','queue1'],fromTopic:'topic0',threads:2]){ m -> println m}

This module is in its early stage. The provided example are fully functional, but some relatively complex scenario may require directly JMS API usage

You may visit the v0.1 page or the latest v0.2 docs

Or check other information at:

Labels

messaging messaging Delete
jms jms Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (2)

 

  1. Oct 08, 2008

    James Strachan says:

    for concurrent consumption, pooling and support for declarative transactions you...

    for concurrent consumption, pooling and support for declarative transactions you might want to consider also integrating the spring-jms abstractions (particularly the JmsTemplate for sending or MessageListenerConsumer for consuming).

  2. Oct 09, 2008

    Mingfai Ma says:

    Personally, i do not think it's should use Spring JMS Template. Reasons are: F...

    Personally, i do not think it's should use Spring JMS Template. Reasons are:

    • From my past xp in a banking project that use Spring JMSTemplate and also messeging products like TibRV, I think JMSTemplate is really useful to make the life of Java developers easier. But in a Groovy project, it no longer provide such benefit, and IMHO, it's actually make things unnecessarily complex. At a high level, unlike Java, Groovy allows concise programming that make it less important to do things by configuration. And Groovy have many features that make the use of JMSTemplate quite unnecessary. e.g. it's easy to use a Closure as a listener and attached any function to any class with Category.
    • Groovy does not depend on Spring. It could be ok for Grails JMS Plugin to utilize Spring JMS features, but not GroovyJMS

    The above are just my opinion and if many people want any Spring JMS features and we are not able to provide in simple Groovy way, it's ok to utilize Spring. Please join the discussion in the groovy-dev mail list!