> runtime errors if JNDI is not available.
JNDI IS ALWAYS available.... ;-)
we need to make sure it is, so don't design around the assumption that it is
not.
In our grand "we are rewriting UNIX on the web", JNDI is the file system
that ALL the VMs see and you can lookup stuff in any directory and any
object can be retrieved. It is the BASIC structure that all our objects
see.
> So I guess you're right that there's another approach, but we'd
> have to be very conscious to make the JNDI/transaction code modular, to
agreed,
> return connections to the pool at the appropriate time (waiting for
> end() or not), and to minimize the extra overhead.
marc
>
> Aaron
>
>
