Hi Alex, no, we use "com.sun.jndi.ldap.LdapCtxFactory" and it is hardcoded. We already have an Jira about that, see https://issues.apache.org/jira/browse/DIRSTUDIO-182
However, it works fine with Sun, IBM and JRockit JVMs, because they all come with this class. I don't know if they just re-license the libraries from Sun. I haven't tested with Harmony, but I guess it won't work (do they have a LDAP provider yet?). Some auto-detection depending on the JVM would be cool. Perhaps a simple property file that maps from java.vendor or java.vm.vendor to the factory class would be enough. Or we could have a list of well-known factory classes and use reflection to test which class exists. Regards, Stefan Alex Karasulu schrieb: > Hi studio team, > > I was wondering if you guys have a means to abstract the JNDI context > factory used in > connections depending on the JVM being used. I have a similar need to > get the JNDI > context factory name based on the JVM that the server is running on so I > thought I might > ask if you already have something in place. > > As you know the over the wire JNDI provider's InitialContextFactory > class is JVM specific. > Did you guys encapsulate this so studio uses the proper one when running > on different JVMs? > > Thanks, > Alex
