Draft Roadmap

The 0.1 release provides a set of JMS Category APIs for community review

develop a wiki page that provide examples of the GroovyJMS usage

0.2 - next release - end of 2008

Adopt general Groovy style and standard, e.g. JDK Logger

First revision to Groovy-style API

Provide API for all key JMS usages

In 0.1, the API support basic usage only. User has to use JMS API directly if they want to call certain JMS API that takes more configurable arguments. e.g. to send a Map message would require users to construct a JMS Message in v0.1

Clarify possibly Groovy messaging usage

Check if it is possible to enhance Groovy Category to provide a pre-execute and post-execute API. This makes a big difference to the GroovyJMS API Revised to use a Closure in Closure pattern, user code will be changed from use(JMS)
{ jmscode } to new JMS(){ jmscode }

Develop a wiki page with a table that list key JMS usage, current GroovyJMS API and proposed Groovy usage

Use Grape/@Grab to provide underlying JMS implementation, by default Apache ActiveMQ, so users may have an option to use JMS without any special works to download JMS implementation jar files. JMS Implementation configuration could be done in the GroovyJMS Builder.

Implement anannotationthat make a method bind to the GroovyJMS context transparently. so user needs not to use new JMS(){} and could directly use GroovyJMS resource and API the new jms{ } usage is very clean and it's not really necessary to use annotation