Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 6933 invoked by uid 500); 13 Aug 2003 03:36:19 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: geronimo-dev@incubator.apache.org Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 6882 invoked from network); 13 Aug 2003 03:36:18 -0000 Received: from ppp3.dyn145.pacific.net.au (HELO xchange.infocomp.com.au) (210.23.145.3) by daedalus.apache.org with SMTP; 13 Aug 2003 03:36:18 -0000 Received: by XCHANGE with Internet Mail Service (5.5.2653.19) id ; Wed, 13 Aug 2003 13:36:23 +1000 Message-ID: <61DA7719C45FD31185280008C733EF6E0307C7AB@XCHANGE> From: Adam Jenkins To: "'geronimo-dev@incubator.apache.org'" Subject: RE: [JMS] Geronimo Messaging Overview Date: Wed, 13 Aug 2003 13:36:23 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3614C.116B7690" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C3614C.116B7690 Content-Type: text/plain; charset="iso-8859-1" Good point raised. I just check out the Architecture descriptions in the wiki and found it diagramatically lacking. I am happy to doco up some of the concepts (microkernel etc) that newbies need in class/component diags, and do a reverse engineer of the current code base (clean it a bit)...that is of course, if these docs don't already exist somewhere (can someone enlighten me). Just let me know what format you want the docs in (zargo? xmi? png?). Thoughts? -----Original Message----- From: Keith Adler [mailto:keith@keithadler.com] Sent: Wednesday, 13 August 2003 1:27 PM To: geronimo-dev@incubator.apache.org Subject: Re: [JMS] Geronimo Messaging Overview Is there anyone looking to organize sub-deliverables where individuals like myself can contribute? I'm looking to make a contribution, but I don't want to sit around and be passive and hope something falls on my lap. Perhaps a lead or someone of that ilk could let me know. Thank you in advance. ----- Original Message ----- From: "Craig Miller" To: Sent: Tuesday, August 12, 2003 10:42 PM Subject: Re: [JMS] Geronimo Messaging Overview > Ed, > > What form are you looking for the initial OpenJMS contributions to come > in? I saw the earlier message from Tim A. that a good place to start would > be a JCA adapter for OpenJMS. Has anyone begun this work? > > Thanks, > > Craig > > ----- Original Message ----- > From: "Ed Curry" > To: > Sent: Tuesday, August 12, 2003 11:59 AM > Subject: [JMS] Geronimo Messaging Overview > > > > Just an overview of the the discussion on Messaging so far > > > > (I will place this on the wiki if there's no objections to it) > > > > > > > > Provisional Plan > > ------------------ > > > > MDBs > > ----- > > Geronimo should support MDBs with pluggable message transport protocols > (JMS, email, ws, etc) > > > > JMS Provider > > ------------- > > Short-Term > > Integrate OpenJMS has a lot of support as the desired JMS provider. > > > > Long-Term > > GeronimoMQ a JMS provider implemented using services from Geronimo such as > persistence, transactions, etc. > > > > > > TODO List > > ============- > > OpenJMS Integration > > Implement JCA support in OpenJMS > > > > > > > > GeronimoMQ Implementation Idea > > --------------------------------------------- > > Just an idea for the implementation of GeronimoMQ. We all know that > Geronimo will be the best J2EE server on the planet and i feel for any JMS > provider to the best it will need to reuse the services of geronimo I'm > not familiar with the architecture of OpenJMS but if it does not already > support pluggable services such as transactions and persistence it could be > refactored to support such a design. Once the geronimo services are ready > they would simple need to be plugged into OpenJMS and Vola! GeronimoMQ. ( > I'm sure it will not be this simple, but you get the idea) > > > > This approach would allow developers who wish to contribute to GeronimoMQ > to start straight away by contributing to OpenJMS. > > > > Just an idea for discussion. :-) > > > > Regards, > > Ed > > ------_=_NextPart_001_01C3614C.116B7690 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [JMS] Geronimo Messaging Overview

Good point raised.  I just check out the = Architecture descriptions in the wiki and found it diagramatically = lacking.  I am happy to doco up some of the concepts (microkernel = etc) that newbies need in class/component diags, and do a reverse = engineer of the current code base (clean it a bit)...that is of course, = if these docs don't already exist somewhere (can someone enlighten = me).  Just let me know what format you want the docs in (zargo? = xmi? png?).

Thoughts?

-----Original Message-----
From: Keith Adler [mailto:keith@keithadler.com]
Sent: Wednesday, 13 August 2003 1:27 PM
To: geronimo-dev@incubator.apache.org
Subject: Re: [JMS] Geronimo Messaging = Overview


Is there anyone looking to organize sub-deliverables = where individuals like
myself can contribute?  I'm looking to make a = contribution, but I don't want
to sit around and be passive and hope something = falls on my lap.  Perhaps a
lead or someone of that ilk could let me = know.

Thank you in advance.

----- Original Message -----
From: "Craig Miller" = <cmiller900@earthlink.net>
To: <geronimo-dev@incubator.apache.org>
Sent: Tuesday, August 12, 2003 10:42 PM
Subject: Re: [JMS] Geronimo Messaging = Overview


> Ed,
>
>     What form are you = looking for the initial OpenJMS contributions to
come
> in?  I saw the earlier message from Tim A. = that a good place to start
would
> be a JCA adapter for OpenJMS.  Has anyone = begun this work?
>
> Thanks,
>
> Craig
>
> ----- Original Message -----
> From: "Ed Curry" = <edcurry@eircom.net>
> To: = <geronimo-dev@incubator.apache.org>
> Sent: Tuesday, August 12, 2003 11:59 AM
> Subject: [JMS] Geronimo Messaging = Overview
>
>
> > Just an overview of the the discussion on = Messaging so far
> >
> > (I will place this on the wiki if there's = no objections to it)
> >
> > <Overview>
> >
> > Provisional Plan
> > ------------------
> >
> > MDBs
> > -----
> > Geronimo should support MDBs with = pluggable message transport protocols
> (JMS, email, ws, etc)
> >
> > JMS Provider
> > -------------
> > Short-Term
> > Integrate OpenJMS has a lot of support as = the desired JMS provider.
> >
> > Long-Term
> > GeronimoMQ a JMS provider implemented = using services from Geronimo such
as
> persistence, transactions, etc.
> >
> >
> > TODO List
> > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D-
> > OpenJMS Integration
> >   Implement JCA support in = OpenJMS
> >
> > </Overview>
> >
> > GeronimoMQ Implementation Idea
> > = ---------------------------------------------
> > Just an idea for the implementation of = GeronimoMQ. We all know that
> Geronimo will be the best J2EE server on the = planet and i feel for any JMS
> provider to the best it will need to reuse the = services of geronimo   I'm

> not familiar with the architecture of OpenJMS = but if it does not already
> support pluggable services such as transactions = and persistence it could
be
> refactored to support such a design.  Once = the geronimo services are ready
> they would simple need to be plugged into = OpenJMS and Vola! GeronimoMQ. (
> I'm sure it will not be this simple, but you = get the idea)
> >
> > This approach would allow developers who = wish to contribute to
GeronimoMQ
> to start straight away by contributing to = OpenJMS.
> >
> > Just an idea for discussion.  = :-)
> >
> > Regards,
> > Ed
>
>

------_=_NextPart_001_01C3614C.116B7690--