AHA! You got me on the right track. It turns out that the JCE provider is being loaded from the java.security file, so it's no doubt being loaded by one of the system classloaders and then caused me grief. I removed the automatic loading of the JCE provider and instead do a Security.addProvider() and it works fine. Mea culpa... Man, I wish these were easier to debug... David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
- Tomcat as a stand alone Zakaria .
- Classpath/loader problems internal to tomcat 3.2.... David Wall
- Re: Classpath/loader problems internal to tom... Craig R. McClanahan
- Re: Classpath/loader problems internal to... David Wall
- Re: Classpath/loader problems interna... David Wall
- Re: Classpath/loader problems in... David Wall
- Optimizing Tomcat Richard Seymour
- RE: Optimizing Tomcat Casey Lucas
- Re: Optimizing Tomcat William Brogden
- RE: Optimizing Tomcat Adam Fowler
- Classpath/loader problems fo... David Wall
- Re: Classpath/loader problem... Craig R. McClanahan
- Re: Classpath/loader problems interna... Craig R. McClanahan
- Re: Tomcat as a stand alone Dennis Daniels
