Hi Dave, > I have decompilied it before to make some sense of it. I now > there is a > class.forName and a newInstance but I don't think they use there own > classloader.
Uhm. > All of the classes are in the deploy directory not in the > jboss lib dir. > The -sevice.xml file that starts this is has them in a classpath def > pointing to the current directory. Where it is dieing it is simply > reading a file that has the x509 certificate info. Ok, can you do one more test ? Can you please print the classloader for your classes, via for example: com.candata.gateway.EncryptionService.class.getClassLoader() and for the lib classes, via for example: com.entrust.toolkit.User.class.getClassLoader() com.entrust.toolkit.credentials.Profile.class.getClassLoader() I think Class.forName may be the source of the problem, as bypasses a direct call to the classloader, going directly to the JVM class cache. Simon _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
