Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
From: "Noel J. Bergman" <noel@devtech.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Cc: "James-Dev Mailing List" <server-dev@james.apache.org>
Subject: RE: Tomcat Naming
Date: Fri, 8 Aug 2003 17:48:35 -0400
Message-ID: <NBBBJGEAGJAKLIDBKJOPGEDCDEAB.noel@devtech.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: 
 <Pine.LNX.4.44.0308081611521.16588-100000@acropolis.discursive.com>
Importance: Normal

Tim O'Brien asked:
> Tomcat ships with a naming component which is relatively easy to reuse.
> There has been some talk of moving this Jakarta Commons to encourage
> reuse.

> I know that many have expressed interest in doing something like this, but
> is there anyone out there with any strong views either way.

Well, I know that right now I am working on needing to integrate JNDI into
James, if that gives you a clue of how I feel.  And I think that someone
else IS doing some of it, but I don't see any evidence (i.e., CVS presence)
so far.

Mind you, I can't use Remy's clever approach for using assigning the initial
context, but I think we'll all be able to teach each other things.

Right now, I'm planning to have the container code in James set a
ThreadLocal when invoking a Matcher or Mailet, with the correct
initialcontext information available there for when the component goes to
instantiate an InitialContext.  The implementation, of course, will be
private to the container, not the contained.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org