|
All I did install it in the extensions
directory and update the java.security file appropriately. I didn’t try
anything else after that. I simply started using jdk1.4 for this project for
the time being ;) If you’d like me to test otherwise,
please let me know. Laurence From: Granqvist, Hans
[mailto:[EMAIL PROTECTED] Laurence, okay, perhaps it makes no
difference. Do you get the same error if you load the provider as unbundled
(via explicit API call) as installed extension (using java.security)? Werner, the reason I asked is that I have been bitten a few
times by JCE providers that didn't initialize properly on the classpath. I
believe Sun's recommendation is to put providers inside lib/ext, and I thought
maybe Sun had optimized the loading in 1.5 and thereby broken some implicit
loading dependencies. Hans From: Laurence
Brockman [mailto: I put it in the lib/ext director previously when I
received the error so it doesn't seem to make a difference if it is in the
CLASSPATH or in the lib/ext directory. |
Title: RE: WSS4J and Kerberos signatures
- Re: WSS4J and Kerberos signatures Davanum Srinivas
- Re: WSS4J and Kerberos signatures Davanum Srinivas
- RE: WSS4J and Kerberos signatures Laurence Brockman
- Re: WSS4J and Kerberos signatures Davanum Srinivas
- RE: WSS4J and Kerberos signatures Laurence Brockman
- RE: WSS4J and Kerberos signatures Granqvist, Hans
- RE: WSS4J and Kerberos signatures Laurence Brockman
- RE: WSS4J and Kerberos signatures Laurence Brockman
- Re: WSS4J and Kerberos signatures Werner Dittmann
- RE: WSS4J and Kerberos signatures Granqvist, Hans
- RE: WSS4J and Kerberos signatures Laurence Brockman
- RE: WSS4J and Kerberos signatures Laurence Brockman
- Re: WSS4J and Kerberos signatures Ruchith Fernando
- Re: WSS4J and Kerberos signatures Alex K.
- Re: WSS4J and Kerberos signatures Enrique Rodriguez
- RE: WSS4J and Kerberos signatures Granqvist, Hans
