Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 59108 invoked from network); 3 Jan 2011 21:57:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Jan 2011 21:57:18 -0000 Received: (qmail 54813 invoked by uid 500); 3 Jan 2011 21:57:17 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 54767 invoked by uid 500); 3 Jan 2011 21:57: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 List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 54760 invoked by uid 99); 3 Jan 2011 21:57:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jan 2011 21:57:17 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of eljotpl@gmail.com designates 209.85.210.182 as permitted sender) Received: from [209.85.210.182] (HELO mail-iy0-f182.google.com) (209.85.210.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jan 2011 21:57:11 +0000 Received: by iyb26 with SMTP id 26so13003248iyb.13 for ; Mon, 03 Jan 2011 13:56:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:reply-to:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=08F2E1wIDfO8bBnUUVppEK6M2CHjQ44Gl1A5rV6iWdw=; b=RTNM/gwB9p7wfBNTzACf7MIwtByGpIBmYa1p6je0WsTKXpamSyeCtxCZxfW71NRTYk bFiRuA2n6o2EcxxzLZbwOoZty+qv/oTRGgJ+liEEJBQP/GeB+XOPjEiq8DA7GpYOSTeJ gNwe+ogqAbxJJeOzSbpiqJqxKKLJY8AHlbewk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=s1/Jv6LZCljtIGVBs0cbCWLfExYZXTx5aE8QQFrvcwoj7EeQhHdxsBS4ysYygeWUed 6vTQBFIa4w8EGQ/j6iO3nUyUX+4ZBvA0zTVHBGYBZZBmRrf0SY32QkAQ0yXnGu0BRONa n84BEx6z6groCkNEGmg2EDkNgVNZcUKkWq6bM= MIME-Version: 1.0 Received: by 10.231.11.139 with SMTP id t11mr10922026ibt.189.1294091810101; Mon, 03 Jan 2011 13:56:50 -0800 (PST) Sender: eljotpl@gmail.com Reply-To: jacek@laskowski.net.pl Received: by 10.231.35.199 with HTTP; Mon, 3 Jan 2011 13:56:50 -0800 (PST) In-Reply-To: <435623FE-8E17-4B53-AE49-D1F26887A6DE@yahoo.com> References: <8D64BA69-A163-4A78-9E7B-A5E4F12A5235@yahoo.com> <435623FE-8E17-4B53-AE49-D1F26887A6DE@yahoo.com> Date: Mon, 3 Jan 2011 22:56:50 +0100 X-Google-Sender-Auth: slAk8y0uM6htOjFuLfvL_CdsXrE Message-ID: Subject: Re: Where's javax.ejb.embeddable.EJBContainer's discovery protocol described? From: Jacek Laskowski To: dev@geronimo.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Jan 3, 2011 at 10:21 PM, David Jencks wrote: > Thats the java SE ServiceLocator which is what the ejb spec says to use. ... > hope this clarifies something :-) Quite a lot! Thanks for your time and patience. Sorry to say so, but I must admit that when you mentioned about the spec and servicelocator I searched the doc and found 22.3.3 Embeddable Container Bootstrapping: The Container Provider supplies the provider configuration file by creating a text file named javax.ejb.spi.EJBContainerProvider and placing it in the META-INF/servicesdirectory of one of its JAR files. The contents of the file should be the name of the embeddable container provider implementation class of the javax.ejb.spi.EJBContainerProvider interface. I meant to have read it, but...well...didn't and hence asked these questions. What a shame! Thanks again. It's clear now and am going to pursue more tests for my self-learning. Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://jaceklaskowski.pl