Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 21725 invoked from network); 11 Jul 2004 01:58:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 11 Jul 2004 01:58:23 -0000 Received: (qmail 61951 invoked by uid 500); 11 Jul 2004 01:58:18 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 61867 invoked by uid 500); 11 Jul 2004 01:58:17 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@geronimo.apache.org Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 61854 invoked by uid 99); 11 Jul 2004 01:58:17 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received: from [211.29.132.168] (HELO mail017.syd.optusnet.com.au) (211.29.132.168) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sat, 10 Jul 2004 18:58:14 -0700 Received: from [192.168.0.2] (d211-29-167-17.dsl.nsw.optusnet.com.au [211.29.167.17] (may be forged)) (authenticated) by mail017.syd.optusnet.com.au (8.11.6p2/8.11.6) with ESMTP id i6B1w9M20041 for ; Sun, 11 Jul 2004 11:58:10 +1000 Message-ID: <40F09E89.7080708@optusnet.com.au> Date: Sun, 11 Jul 2004 11:57:29 +1000 From: Gianny Damour User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: ResourceAdapter.start() not getting called? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On 11/07/2004 5:24 AM, David Jencks wrote: > > Since it is unlikely that anyone will be running more than one > TransactionManager/XATerminator in a geronimo server, perhaps this > should be made a little clearer by specifying the WorkManager > directly in the ResourceAdapter config and constructing a > BootstrapContext per ResourceAdapter instance. Opinions? I agree. Perhaps that there is also something not so obvious - at least for me: a BootstrapContext must reference the same XATerminator used under the cover by the XAWork referenced by the WorkManager of this context. The current dependencies are something like that: TransactionManager <---- XAWork<---- WorkManager <---- BootstrapContext; ^ | | ------------------------------------------------------------------- So, is it possible to make it "clearer" by providing to the (Geronimo)WorkManager a TransactionManager(Proxy)? This latter still provides an XAWork view in order to recreate resource adpater transactions; one adds to the (Geronimo)WorkManager a getter for this XATerminator reference/attribute; and BootstrapContext only needs by now a simple reference to (Geronimo)WorkManager. This way, the dependencies could be more abvious - one more time, at least for me: TransactionManager <---- WorkManager <---- BootstrapContext. By the way, as I am talking about XAWork, I think that there are some concurrency issues: the begin and end methods should be synchronized otherwise, it is possible to run two Work concurrently having the same ExecutionContext. > > Also, perhaps we should adopt a naming convention for all these > gbeans such as > > geronimo.server:type=BootstrapContext,name=MyBootstrapContext Is it possible to have a distinct domain for the JCA services? I mean something like: geronimo.jca:type=BootstrapContext,name=MyBootstrapContext Moreover, one could perhaps use the naming conventions proposed by JSR-77. For instance, a WorkManager could be name: geronimo.jca:type=WorkManager,BootstrapContext=MyBootstrapContext Many thanks, Gianny