geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <>
Subject [JNDI] Commons Naming checking Was: JNDI Impl (fwd)
Date Tue, 12 Aug 2003 20:19:51 GMT

Okay, so I should have re-titled this.

A copy of the Tomcat JNDI is in the Commons-sandbox as Commons Naming.

The CVS is:

jakarta-commons-sandbox naming

and not jakarta-commons naming.  Bad habit.

---------- Forwarded message ----------
Date: Tue, 12 Aug 2003 16:15:41 -0400 (EDT)
From: Henri Yandell <>
Subject: Re: JNDI Impl

I've commited the Tomcat JNDI implementation into
jakarta-commons-sandbox/naming. I had played around a bit, pushing some
standard looking components into a jndi sub-package but I've backed that
out currently as unimportant.

The maven project.xml works for building under maven b10. There are a lot
of Sun dependencies though, so you have to hunt them down. I'll try to
hook some urls to them to make life a little easier.

I'm no shakes at JNDI, just interested, so for me my next step is to
understand fully what is going on in the Tomcat JNDI [I've got a good
grasp, but have yet to work out how to pass in some xml configurations
etc]. If others have better drives etc, I'm happy to act as the Commons
gopher and deal with websites, releases, passing on the Commons/ASF way

cvs checking out via:

cvs -d login
password: anoncvs

cvs -d checkout jakarta-commons/naming

Have at it,


On Fri, 8 Aug 2003, Henri Yandell wrote:

> On Fri, 8 Aug 2003, Richard Monson-Haefel wrote:
> > These are excellent issues, Aaron.
> >
> > Speaking only for myself, I envisioned a development track as follows:
> >
> > 1st. Develop, or otherwise obtain, a simple in memory JNDI ENC that can be used
> > across J2EE components. Something very basic, immutable, bootstrapped off a flat
> On this now. Commons JNDI. Resolving the dependencies so it will at least
> compile and removing things like the MBean part for the moment. It'll go
> in the Commons-sandbox sometime next week I imagine.
> Alternative is my simple-jndi package [which already fulfills two of your
> criteria, simple and jndi being in the title!] which might be of interest.
> I'm just not sure if it's too simple in concept for your plans.
> +1 to your general development plan.
> Hen

View raw message