Everything uses JNDI. Running the entire testsuite is the best test. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message ----- From: "Jim Carlson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, February 08, 2003 4:13 AM Subject: [JBoss-dev] Re: JNP directory support? > Scott, > I'm now working on the DirContext support. In fact, I already have > getting/setting of attributes working (it's a pretty simple > Hashtable-backed implementation). > Meanwhile, I've been refactoring the existing jnp code a bit, which > may or may not endear me to the existing authors/users. Also, I've > noticed a few quirks in the jnp implementation which don't seem to match > the JNDI specification. Taking a look at some standard jnp client code > would help me understand what's going on (and help me avoid introducing > problems for existing users). Are there some places in the rest of the > JBoss code where JNP/JNDI is used extensively? I'm particularly > concerned about the way URLs are parsed/handled by the JNP interfaces. > Alternatively -- are there some unit tests that I can use on the JNP > server, other than the TestJNPSockets test (which is in the naming/ tree)? > > Thanks, > > Jim > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
