Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 29339 invoked by uid 500); 9 Aug 2003 18:58:09 -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 29325 invoked from network); 9 Aug 2003 18:58:09 -0000 Received: from ms-smtp-03.rdc-kc.rr.com (24.94.166.129) by daedalus.apache.org with SMTP; 9 Aug 2003 18:58:09 -0000 Received: from Monson-Haefel.com (CPE-24-163-199-223.mn.rr.com [24.163.199.223]) by ms-smtp-03.rdc-kc.rr.com (8.12.8p1/8.12.7) with ESMTP id h79IwBrv025489 for ; Sat, 9 Aug 2003 13:58:12 -0500 (CDT) Message-ID: <3F3544A6.D20C796E@Monson-Haefel.com> Date: Sat, 09 Aug 2003 13:59:50 -0500 From: Richard Monson-Haefel Reply-To: Richard@Monson-Haefel.com X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: geronimo-dev@incubator.apache.org Subject: Re: "Virtual Hosting" References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I don't think this is much of a problem. In fact, I thought OpenEJB's JNDI ENC Impl partitioned things very nicely by associating requests with deployment ids. That way each deployment had its own branch in the JNDI tree, and branches were isolated. Anyway, I don't think its a big deal to support this. In fact, I think its probably a natural outcome of development. Aaron Mulder wrote: > I'd like to suggest that Geronimo should support running > applications in a "sandbox". Which is to say, I'd like it to be able to > run several different apps, where each app can see only its own JNDI > entries, only its own DB pools, etc. That also means each app should be > able to be packaged with its own config files / DDs. I don't mind if the > server keeps an internal copy elsewhere, but I'd really like to be able to > just give an ear with all the configs it needs and have Geronimo run it in > a separate space from other apps. > > I guess this impinges in the JNDI discussion as well, in the sense > that a JNDI request from a remote client would need to identify the > application it's targeting, either via a suffix on the initial URL, or an > additional context parameter, or something along those lines. So two > different apps could each deploy something at "/Foo", and as long as the > client specified which app it wanted to connect to, it would get the right > one. This also lets different apps use different security realms, and > still secure JNDI. > > Aaron -- Richard Monson-Haefel Author of J2EE Web Services (Addison-Wesley 2003) Author of Enterprise JavaBeans, 3rd Edition (O'Reilly 2001) Co-Author of Java Message Service (O'Reilly 2000) http://www.Monson-Haefel.com