On Thu, 27 Feb 2003, Costin Manolache wrote:
> - A JNDI wrapper for VFS providers will allow people to write providers > using a simpler API ( and have them exposed as JNDI via the VFS->JNDI > wrapper ). +1. I looked into using VFS underneath my JNDI provider but ended up skipping it as I couldn't see if I could ask if an element in the FS was a container [ie directory] and because VFS didn't seem to support the classpath. > I think we do need a separate component to: > - simplify creation of generic JNDI drivers ( like config file abstraction, > etc). > - implement JNDI drivers for common config files > - eventually map to and from jdk1.4 prefs > - provide high-level JNDI tools - replication, deep copy, ant tasks, etc. > Those will operate on both VFS and any other kind of JDNI ( config, etc ). All sounds good. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
