From geronimo-dev-return-2935-apmail-incubator-geronimo-dev-archive=incubator.apache.org@incubator.apache.org Tue Sep 02 11:12:03 2003 Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@www.apache.org Received: (qmail 42763 invoked from network); 2 Sep 2003 11:12:02 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 2 Sep 2003 11:12:02 -0000 Received: (qmail 19269 invoked by uid 500); 2 Sep 2003 11:11:47 -0000 Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 19121 invoked by uid 500); 2 Sep 2003 11:11:45 -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 19018 invoked from network); 2 Sep 2003 11:11:44 -0000 Received: from unknown (HELO smtp.abyssworld.de) (80.138.153.42) by daedalus.apache.org with SMTP; 2 Sep 2003 11:11:44 -0000 Received: by smtp.abyssworld.de (Postfix, from userid 426) id DB3481D47F; Tue, 2 Sep 2003 13:11:37 +0200 (CEST) Received: from daniel.stefan.haischt.name (unknown [192.168.120.47]) by smtp.abyssworld.de (Postfix) with ESMTP id 84A6E1D470 for ; Tue, 2 Sep 2003 13:11:36 +0200 (CEST) Message-ID: <3F547948.9060600@daniel.stefan.haischt.name> Date: Tue, 02 Sep 2003 13:04:40 +0200 From: "Daniel S. Haischt" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: geronimo-dev@incubator.apache.org Subject: Re: Who are working on the JMS integration References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Thies Edeling wrote: [...] > > > If the message broker is JMS compliant it implements the JMS API's. Or am > I mixing up the JMS API's with API's for integration ? > there are to different messaging components ... a) a JMS API compliant provider which abstracts the underlying MOM, for example IBM shipps a JMS provider that abstracts their MQSeries product. b) the framework/components that allows to integrate the JMS provider into a J2EE server system and delegates requests from/to the JMS provider. there are two method to accomplish this ... 1) create a proprietary integration framwork that tightly couples the JMS provider to the J2EE server infrastructer. this _might_ have the advantage that the integration part is optimized for that specific JMS provider, but on the other site this approach limits you to that specific JMS provider. 2) create a JCA resource adapter (*.rar) which will be loaded while starting the J2EE server and which will delegate requests to the JMS provider. the resource adapter is _kinda_ similar to a JDBC driver. this is the mor generic way and the way that i would prefer. final note: we don't need to care about part a), that's the resposibility of the JMS provider vendor (aka OpenJMS). regards daniel s. haischt --