Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 18333 invoked from network); 8 Apr 2004 07:12:31 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 8 Apr 2004 07:12:31 -0000 Received: (qmail 53194 invoked by uid 500); 8 Apr 2004 07:12:02 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 53079 invoked by uid 500); 8 Apr 2004 07:12:01 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 52975 invoked from network); 8 Apr 2004 07:12:00 -0000 Received: from unknown (HELO gateway.elsag.de) (134.98.65.18) by daedalus.apache.org with SMTP; 8 Apr 2004 07:12:00 -0000 Received: from vwall.elsag.de by gateway.elsag.de via smtpd (for daedalus.apache.org [208.185.179.12]) with SMTP; Thu, 8 Apr 2004 09:12:12 +0200 Received: from esmail by gateway.elsag.de via smtpd (for vwall.elsag.de [192.168.100.108]) with SMTP; Thu, 8 Apr 2004 09:12:11 +0200 Subject: RE: [configuration] Subsets and JNDIConfiguration MIME-Version: 1.0 Date: Thu, 8 Apr 2004 09:12:11 +0200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [configuration] Subsets and JNDIConfiguration Thread-Index: AcQdB6HnWkrSJL6USTquc6A/ZzMbkwAL7QIw From: =?iso-8859-1?Q?J=F6rg_Schaible?= To: "Jakarta Commons Developers List" 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 Henri Yandell wrote on Thursday, April 08, 2004 3:20 AM: > Spice JNDIKit more useful than Simple-JNDI? URL? Reasons? Spice JNDIKit comes with an InMemoryContext that is very comfortable for = tests. Additionally we had to comment out unit tests, since = context.listBindings("") does not work in Simple-JNDI. Also Spice JNDI = has NameParser support, that is not implemented at all in Simple-JNDI. > I'll happily stop developing Simple-JNDI if there's something > out there I can replace with it and let someone else develop > it :) Let's me start working on Simple-JMS. IMHO Spice JNDIKit could be a better foundation for PropertyContext etc. Regards, J=F6rg --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org