Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
Reply-To: <tma@netspace.net.au>
From: "Tim Anderson" <tma@netspace.net.au>
To: <geronimo-dev@incubator.apache.org>
Subject: RE: [jms][patch] Integrating OpenJMS
Date: Sat, 16 Aug 2003 11:31:15 +1000
Message-ID: <AHEMLCHGJOKOCPPFEOIHIEOLGMAA.tma@netspace.net.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: 
 <20030815143047.18717.h010.c000.wm@mail.worden.org.criticalpath.net>
Importance: Normal

Go for it. Note that OpenJMS is still on version 1.0.2
of the JMS spec. I hadn't planned to upgrade to 1.1 until 
the OpenJMS 0.8 release, but I guess I can bring that forward.

-Tim

> -----Original Message-----
> From: brent@worden.org [mailto:brent@worden.org]
> Sent: Saturday, 16 August 2003 7:31 AM
> To: geronimo-dev@incubator.apache.org
> Subject: [jms][patch] Integrating OpenJMS
> 
> 
> If no one has started and no one objects, I was planning to begin
> integrating OpenJMS into Geronimo.
> 
> My plan of attack was going to include:
> 
> 1) Adding the JMS specification source files to specs/j2ee.  This is
> done as I've completed adding the ASF license to the JMS 1.1 source
> files and included an archive of the modified files.
> 
> 2) Creating a generic JMS provider SPI and adding it to the core
> module.  The interface would include the MBeans to manage the JMS
> components, the means to bind administered objects to the naming
> context, provided the JMS stats as per JSR77, etc.
> 
> 3) Creating a OpenJMS implementation for the JMS SPI.
> 
> If anyone has any thoughts, concerns, or guidance, feel free to share.
> 
> Brent Worden
> http://www.brent.worden.org/
>